Past Incidents

Update 17:27 UTC We are currently experiencing a service disruption impacting the Menlo Security Isolation.

Users browsing via Bounce cluster 57 (Taiwan) may experience slow browsing and/or timeouts. The Menlo Security Operations team has identified the cause and are working with our service provider in this region to resolve the issue.

Update 12:20 UTC TechOps Engineers have confirmed nodes in the bounce cluster 57 (Taiwan) have now recovered.

10:46 UTC We are currently experiencing a service disruption impacting the Menlo Security Isolation.

Users browsing via Bounce cluster 57 (Taiwan) may experience slow browsing and/or timeouts.

The Menlo Security Operations team has identified the cause and are working with our service provider in this region to resolve the issue.

1935 UTC Web browsing via our Taiwan egress cluster is back to normal. Menlo Security Operations will continue to monitor for the next few hours.

0412 UTC 2022-10-14 Menlo Security Operations has completed an extended observation period and and not seen a reoccurrence of slow web browsing or timeout through the Taiwan egress cluster. Incident is resolved.

Update 20:41 UTC Operations has restore the service.

Update 18:52 UTC Operations are working to restore the service. No customer is impacted at the moment.

Update 17:51 UTC Operations continue to work with the provider to restore the service. No customer is impacted at the moment.

Update 17:27 UTC Operations continue to work with the provider to restore the service.

Update 16:57 UTC Operations continue to work with the provider to restore the service. All affected users are rolled back.

Update 12:37 UTC Operations continue to work with the provider to restore the service.

We are currently experiencing a service disruption impacting the Menlo Security Isolation.

Users in the us-west-1 (N. California) , ap-northeast-2 (Seoul), ap-southeast-2 (Sydney) and ap-northeast-1 (Tokyo) with CloudHSM configured may be experiencing failures while connecting to TLS secured web sites.

The Menlo Security Operations team has identified the root cause and currently working on a solution.

We will send an additional update in 20 minutes.