- Detected by Pingoru
- Oct 02, 2026, 02:43 AM UTC
- Resolved
- Oct 02, 2026, 03:07 AM UTC
- Duration
- 24m
Affected: Ohio - Proxy (Ohio - Proxy)Las Vegas - Proxy (Las Vegas - Proxy)Seoul - Proxy (Seoul - Proxy)Tel Aviv - Proxy (Tel Aviv - Proxy)Montreal - Proxy (Montreal - Proxy)Mumbai - Proxy (Mumbai - Proxy)Osaka - Proxy (Osaka - Proxy)Hong Kong - Proxy (Hong Kong - Proxy)Tokyo - Proxy (Tokyo - Proxy)Zurich - Proxy (Zurich - Proxy)Oregon - Proxy (Oregon - Proxy)London - Proxy (London - Proxy)Taiwan - Proxy (Taiwan - Proxy)Frankfurt - Proxy (Frankfurt - Proxy)Singapore - Proxy (Singapore - Proxy)North Virginia - Proxy (North Virginia - Proxy)Paris - Proxy (Paris - Proxy)Iowa - Proxy (Iowa - Proxy)
Timeline · 2 updates
-
identified Oct 02, 2026, 02:43 AM UTC
An issue has been found and is currently in the process of rollback Traffic for tenants configured to bypass the global PEL was temporarily routed through standard policy processing instead of skipping it.
-
resolved Oct 02, 2026, 03:07 AM UTC
The rollback is complete and the incident has been resolved. Please contact Support if you have additional questions
Read the full incident report →
- Detected by Pingoru
- Sep 24, 2026, 01:29 AM UTC
- Resolved
- Sep 24, 2026, 02:11 AM UTC
- Duration
- 42m
Affected: Osaka - Web Isolation (Osaka - Web Isolation)Seoul - Web Isolation (Seoul - Web Isolation)
Timeline · 4 updates
-
investigating Sep 24, 2026, 01:29 AM UTC
An Issue has been found with browsing in Osaka and Seoul. Customers may experience degraded browsing in the region. Further information and status updates will be shared here as they become available.
-
investigating Sep 24, 2026, 01:48 AM UTC
We are actively investigating the browsing issues in Osaka and are working on mitigation plans. Further information will be shared as it becomes available.
-
investigating Sep 24, 2026, 02:02 AM UTC
We have implemented a fix and are actively monitoring to ensure seamless browsing.
-
resolved Sep 24, 2026, 02:11 AM UTC
This incident has been resolved. Please contact Support if you have additional questions
Read the full incident report →
- Detected by Pingoru
- Sep 16, 2026, 08:48 AM UTC
- Resolved
- Sep 16, 2026, 09:37 AM UTC
- Duration
- 49m
Affected: London - Proxy (London - Proxy)
Timeline · 3 updates
-
identified Sep 16, 2026, 08:48 AM UTC
An issue has been detected with browsing in London. Further information and status updates will be shared here as they become available
-
investigating Sep 16, 2026, 09:20 AM UTC
We are actively investigating the cause of the issue and are working on mitigation plans. Further information will be shared as it becomes available.
-
resolved Sep 16, 2026, 09:37 AM UTC
We have implemented a mitigation and are actively monitoring to ensure stability.
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 09:02 AM UTC
- Resolved
- Sep 15, 2026, 09:07 AM UTC
- Duration
- 4m
Affected: Global - Logging (Global - Logging)
Timeline · 2 updates
-
investigating Sep 15, 2026, 09:02 AM UTC
An issue has been detected with logging. Customers will have an issue trying to access the latest user activities logs. Further information and status updates will be shared here as they become available.
-
resolved Sep 15, 2026, 09:07 AM UTC
This incident has been resolved. Please contact Support if you have additional questions
Read the full incident report →
- Detected by Pingoru
- Sep 10, 2026, 08:32 AM UTC
- Resolved
- Sep 10, 2026, 09:00 AM UTC
- Duration
- 28m
Affected: Global - Logging (Global - Logging)
Timeline · 2 updates
-
identified Sep 10, 2026, 08:32 AM UTC
An issue has been detected with logging. Customers will have an issue trying to access the latest user activities logs. Further information and status updates will be shared here as they become available.
-
resolved Sep 10, 2026, 09:00 AM UTC
We have identified the issue and applied failover. This issue is now fixed.
Read the full incident report →
- Detected by Pingoru
- Sep 07, 2026, 01:27 PM UTC
- Resolved
- Sep 07, 2026, 01:36 PM UTC
- Duration
- 9m
Affected: Global - Email Flow (Global - Email Flow)
Timeline · 2 updates
-
investigating Sep 07, 2026, 01:27 PM UTC
An issue has been found and is currently under investigation. We are investigating reports of email being rejected with a 550 code when sending to Menlo. Further updates will be provided when they are available.
-
resolved Sep 07, 2026, 01:36 PM UTC
Mitigation has now been applied and we are no longer seeing issues. Our engineering team will continue to monitor.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 09:33 AM UTC
- Resolved
- Sep 04, 2026, 03:06 PM UTC
- Duration
- 5h 33m
Affected: Global - Email Flow (Global - Email Flow)
Timeline · 5 updates
-
investigating Sep 04, 2026, 09:33 AM UTC
An issue impacting Email is being investigated. Some customers may see emails rejected by upstream with a 451 error, resulting in delayed emails. Further information and status updates will be shared here as they become available.
-
investigating Sep 04, 2026, 09:53 AM UTC
Our engineering teams believe the root cause is the upstream provider not the Menlo service. There are reports of similar errors from multiple sources though no official confirmation yet. Our engineering teams continue to monitor the situation.
-
investigating Sep 04, 2026, 10:50 AM UTC
The root cause has been confirmed as the upstream provider not the Menlo service. Some customers will see email delays. Our engineering teams continue to monitor the situation.
-
investigating Sep 04, 2026, 12:51 PM UTC
The root cause has been confirmed as the upstream provider not the Menlo service. They have identified the issue and are working on a fix. Some customers will continue to see email delays until the issue is fully resolved. Our engineering teams continue to monitor the situation.
-
resolved Sep 04, 2026, 03:06 PM UTC
The upstream provider has implemented a fix and the issue is now resolved. Please contact support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 10:32 AM UTC
- Resolved
- Sep 03, 2026, 11:16 AM UTC
- Duration
- 43m
Affected: Frankfurt - Web Isolation (Frankfurt - Web Isolation)Frankfurt - Proxy (Frankfurt - Proxy)
Timeline · 2 updates
-
investigating Sep 03, 2026, 10:32 AM UTC
An issue has been found with browsing via the Frankfurt region. Customers may experience degraded performance. We are activley investigating and will update here when we have more information.
-
resolved Sep 03, 2026, 11:16 AM UTC
Mitigation has now been applied and browsing latency has returned to normal. We will continue monitoring for any further issues.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 01:14 AM UTC
- Resolved
- Sep 02, 2026, 02:17 AM UTC
- Duration
- 1h 3m
Affected: SG - Votiro (SG - Votiro)
Timeline · 3 updates
-
investigating Sep 02, 2026, 01:14 AM UTC
An issue impacting the CDR service is being investigated. Some customers may encounter challenges with file sanitization when connected via Menlo REST AP. Further information and status updates will be shared here as they become available.
-
investigating Sep 02, 2026, 01:40 AM UTC
We have identified the source of the issue and are working on a mitigation. Customers impacted can contact Customer Support for assistance with a workaround as required.
-
resolved Sep 02, 2026, 02:17 AM UTC
This incident has been resolved. Please contact Support if you have additional questions
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2026, 10:46 AM UTC
- Resolved
- Aug 28, 2026, 01:48 PM UTC
- Duration
- 3h 2m
Affected: Milan - Doc Isolation (Milan - Doc Isolation)Hong Kong - Doc Isolation (Hong Kong - Doc Isolation)Tel Aviv - Doc Isolation (Tel Aviv - Doc Isolation)Montreal - Doc Isolation (Montreal - Doc Isolation)Sydney - Doc Isolation (Sydney - Doc Isolation)Las Vegas - Doc Isolation (Las Vegas - Doc Isolation)Frankfurt - Doc Isolation (Frankfurt - Doc Isolation)Dammam - Doc Isolation (Dammam - Doc Isolation)Osaka - Doc Isolation (Osaka - Doc Isolation)Taiwan - Doc Isolation (Taiwan - Doc Isolation)Melbourne - Doc Isolation (Melbourne - Doc Isolation)Singapore - Doc Isolation (Singapore - Doc Isolation)London - Doc Isolation (London - Doc Isolation)North Virginia - Doc Isolation (North Virginia - Doc Isolation)Sao Paulo - Doc Isolation (Sao Paulo - Doc Isolation)Jakarta - Doc Isolation (Jakarta - Doc Isolation)Seoul - Doc Isolation (Seoul - Doc Isolation)Oregon - Doc Isolation (Oregon - Doc Isolation)Mumbai - Doc Isolation (Mumbai - Doc Isolation)Tokyo - Doc Isolation (Tokyo - Doc Isolation)Ohio - Doc Isolation (Ohio - Doc Isolation)Paris - Doc Isolation (Paris - Doc Isolation)Zurich - Doc Isolation (Zurich - Doc Isolation)Bahrain - Doc Isolation (Bahrain - Doc Isolation)North California - Doc Isolation (North California - Doc Isolation)Cape Town - Doc Isolation (Cape Town - Doc Isolation)South Carolina - Doc Isolation (South Carolina - Doc Isolation)Iowa - Doc Isolation (Iowa - Doc Isolation)UAE - Doc Isolation (UAE - Doc Isolation)CDR / Votiro (CDR / Votiro)
Timeline · 4 updates
-
investigating Aug 28, 2026, 10:46 AM UTC
An issue has been found impacting file downloads and is currently under investigation
-
investigating Aug 28, 2026, 11:14 AM UTC
We have identified the cause of the issue and are in the process of developing a fix. Further information will be shared as it becomes available.
-
investigating Aug 28, 2026, 12:07 PM UTC
We have identified the cause of the issue and have developed a fix which is currently undergoing validation. Upon successful validation, this will be deployed to all regions. Further information will be shared as it becomes available
-
resolved Aug 28, 2026, 01:48 PM UTC
We are pleased to announce that the fix has been successfully deployed to all regions. This incident has been resolved. Please contact Support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 05:08 PM UTC
- Resolved
- Aug 20, 2026, 07:22 PM UTC
- Duration
- 2h 14m
Affected: Oregon - Web Isolation (Oregon - Web Isolation)Iowa - Web Isolation (Iowa - Web Isolation)
Timeline · 4 updates
-
investigating Aug 20, 2026, 05:08 PM UTC
An issue has been found with services hosted out of the Iowa and Oregon GCP regions. Customers may experience issues using browser isolation. We are actively working on mitigation and will update here when we have more information.
-
investigating Aug 20, 2026, 05:22 PM UTC
We have mitigated the issue with GCP services and will continue to monitor for any potential customer impact.
-
investigating Aug 20, 2026, 06:36 PM UTC
On further investigation we discovered some customer impact for customers routed via Iowa. This impact was mitigated as of 18:04 UTC / 11:04 PDT. We are continuing to monitor the mitigations in place.
-
resolved Aug 20, 2026, 07:22 PM UTC
This incident has been resolved after an extended period of monitoring. Please contact Support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Aug 16, 2026, 10:40 AM UTC
- Resolved
- Aug 16, 2026, 04:58 PM UTC
- Duration
- 6h 18m
Affected: South Carolina - Doc Isolation (South Carolina - Doc Isolation)South Carolina - Proxy (South Carolina - Proxy)South Carolina - Web Isolation (South Carolina - Web Isolation)
Timeline · 3 updates
-
investigating Aug 16, 2026, 10:40 AM UTC
Menlo Operations has detected some intermittent disruption in the South Carolina region. While the network issue is under investigation, the region has been failed out. Traffic in the region is expected to divert to other US regions.
-
investigating Aug 16, 2026, 10:59 AM UTC
We can confirm that impact from this issue has been resolved by the applied mitigation. The situation is being monitored to ensure continued stability.
-
resolved Aug 16, 2026, 04:58 PM UTC
This incident has been resolved after a period of monitoring. Please contact Support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 08:00 AM UTC
- Resolved
- Aug 05, 2026, 08:48 AM UTC
- Duration
- 47m
Affected: Seoul - Web Isolation (Seoul - Web Isolation)Seoul - Proxy (Seoul - Proxy)
Timeline · 4 updates
-
identified Aug 05, 2026, 08:00 AM UTC
We are currently investigating an intermittent issue while browsing in Seoul
-
investigating Aug 05, 2026, 08:16 AM UTC
We are actively investigating the cause of the issue and are working on mitigation plans. Further information will be shared as it becomes available.
-
investigating Aug 05, 2026, 08:33 AM UTC
We have implemented a fix and are actively monitoring to ensure stability
-
resolved Aug 05, 2026, 08:48 AM UTC
This incident has been resolved. Please contact Support if you have additional questions
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2026, 09:08 AM UTC
- Resolved
- Aug 03, 2026, 09:39 AM UTC
- Duration
- 30m
Affected: Sao Paulo - Web Isolation (Sao Paulo - Web Isolation)
Timeline · 2 updates
-
identified Aug 03, 2026, 09:08 AM UTC
We are currently investigating browsing issue in South America region.
-
resolved Aug 03, 2026, 09:39 AM UTC
We identified and mitigated the issue. The South America region is functioning as normal.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 11:06 AM UTC
- Resolved
- Aug 03, 2026, 09:48 AM UTC
- Duration
- 2d 22h
Affected: Ohio - Proxy (Ohio - Proxy)Las Vegas - Proxy (Las Vegas - Proxy)Seoul - Proxy (Seoul - Proxy)Dammam - Proxy (Dammam - Proxy)Tel Aviv - Proxy (Tel Aviv - Proxy)Milan - Proxy (Milan - Proxy)Montreal - Proxy (Montreal - Proxy)Mumbai - Proxy (Mumbai - Proxy)Jakarta - Proxy (Jakarta - Proxy)North California - Proxy (North California - Proxy)Osaka - Proxy (Osaka - Proxy)Hong Kong - Proxy (Hong Kong - Proxy)Sao Paulo - Proxy (Sao Paulo - Proxy)Melbourne - Proxy (Melbourne - Proxy)Cape Town - Proxy (Cape Town - Proxy)Sydney - Proxy (Sydney - Proxy)Bahrain - Proxy (Bahrain - Proxy)Tokyo - Proxy (Tokyo - Proxy)Zurich - Proxy (Zurich - Proxy)Oregon - Proxy (Oregon - Proxy)London - Proxy (London - Proxy)Taiwan - Proxy (Taiwan - Proxy)Frankfurt - Proxy (Frankfurt - Proxy)Singapore - Proxy (Singapore - Proxy)North Virginia - Proxy (North Virginia - Proxy)Paris - Proxy (Paris - Proxy)Iowa - Proxy (Iowa - Proxy)South Carolina - Proxy (South Carolina - Proxy)UAE - Proxy (UAE - Proxy)
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 12:10 AM UTC
- Resolved
- Jul 23, 2026, 01:07 AM UTC
- Duration
- 57m
Affected: Jakarta - Web Isolation (Jakarta - Web Isolation)Tokyo - Web Isolation (Tokyo - Web Isolation)Hong Kong - Web Isolation (Hong Kong - Web Isolation)Ohio - Web Isolation (Ohio - Web Isolation)Las Vegas - Web Isolation (Las Vegas - Web Isolation)Osaka - Web Isolation (Osaka - Web Isolation)Taiwan - Web Isolation (Taiwan - Web Isolation)Seoul - Web Isolation (Seoul - Web Isolation)North Virginia - Web Isolation (North Virginia - Web Isolation)North California - Web Isolation (North California - Web Isolation)Ohio - Proxy (Ohio - Proxy)Las Vegas - Proxy (Las Vegas - Proxy)Seoul - Proxy (Seoul - Proxy)Jakarta - Proxy (Jakarta - Proxy)North California - Proxy (North California - Proxy)Osaka - Proxy (Osaka - Proxy)Hong Kong - Proxy (Hong Kong - Proxy)Tokyo - Proxy (Tokyo - Proxy)Taiwan - Proxy (Taiwan - Proxy)Singapore - Proxy (Singapore - Proxy)Iowa - Proxy (Iowa - Proxy)Iowa - Web Isolation (Iowa - Web Isolation)South Carolina - Proxy (South Carolina - Proxy)South Carolina - Web Isolation (South Carolina - Web Isolation)
Timeline · 4 updates
-
identified Jul 23, 2026, 12:10 AM UTC
An issue has been detected with browsing in the US - Las Vegas region. Further information and status updates will be shared here as they become available
-
investigating Jul 23, 2026, 12:34 AM UTC
We are actively investigating the cause of the browsing issue in US and APAC regions and are working on mitigation plans. Further information will be shared as it becomes available.
-
investigating Jul 23, 2026, 12:47 AM UTC
We have implemented a fix and are actively monitoring to ensure browsing is successful in all reported regions.
-
resolved Jul 23, 2026, 01:07 AM UTC
This incident has been resolved after a period of monitoring. Please contact Support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 05:09 AM UTC
- Resolved
- Jul 15, 2026, 09:06 AM UTC
- Duration
- 3h 56m
Affected: Melbourne - Web Isolation (Melbourne - Web Isolation)Frankfurt - Web Isolation (Frankfurt - Web Isolation)Hong Kong - Web Isolation (Hong Kong - Web Isolation)Milan - Web Isolation (Milan - Web Isolation)Osaka - Web Isolation (Osaka - Web Isolation)Seoul - Web Isolation (Seoul - Web Isolation)Sydney - Web Isolation (Sydney - Web Isolation)
Timeline · 4 updates
-
identified Jul 15, 2026, 05:09 AM UTC
Disruption to isolation browsing in Milan was detected. To mitigate the disruption, the region has been failed out until the issue is resolved.
-
investigating Jul 15, 2026, 05:23 AM UTC
Menlo is investigating an issue causing browsing disruption in Frankfurt, Hong Kong, Osaka, Seoul, Sydney, and Melbourne.
-
investigating Jul 15, 2026, 05:43 AM UTC
Menlo is working on mitigation for the detected issue. Several regions have returned to a working state.
-
resolved Jul 15, 2026, 09:06 AM UTC
The issue has been identified and remediated. The regions are now be fully functional
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 03:30 AM UTC
- Resolved
- Jul 15, 2026, 08:55 AM UTC
- Duration
- 5h 25m
Affected: Global - Admin Portal (Global - Admin Portal)
Timeline · 5 updates
-
identified Jul 15, 2026, 03:30 AM UTC
An issue has been detected with the Admin Portal service. Users may have issues accessing the Admin Portal to manage policies and tenancies. Further information and status updates will be shared here as they become available.
-
investigating Jul 15, 2026, 05:37 AM UTC
We are actively investigating the cause of the issue and are working on mitigation plans. Further information will be shared as it becomes available.
-
investigating Jul 15, 2026, 07:02 AM UTC
Updates to policies in the Admin portal are working now. Menlo is continuing to fix propagating the policies out to regions.
-
investigating Jul 15, 2026, 08:16 AM UTC
We are continuing to investigate issues with policy changes. There may be delays in applying new policy amendments.
-
resolved Jul 15, 2026, 08:55 AM UTC
We have identified the root cause and rolled out the remediation. All Admin services should now be operational
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2026, 02:52 PM UTC
- Resolved
- Jul 13, 2026, 03:35 PM UTC
- Duration
- 42m
Affected: Milan - Proxy (Milan - Proxy)Zurich - Proxy (Zurich - Proxy)London - Proxy (London - Proxy)Frankfurt - Proxy (Frankfurt - Proxy)Paris - Proxy (Paris - Proxy)
Timeline · 3 updates
-
investigating Jul 13, 2026, 02:52 PM UTC
We have received reports that customers in Europe are getting 403 errors when proxying traffic via Menlo Security. We are actively investigating the issue and are working on mitigation plans. Further information will be shared as it becomes available.
-
investigating Jul 13, 2026, 03:08 PM UTC
We have identified the cause of the issue and have developed a mitigation, which is currently being rolled out to impacted regions. Further information will be shared as it becomes available
-
resolved Jul 13, 2026, 03:35 PM UTC
This incident has been resolved. Please contact Support if you have additional questions
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 03:45 PM UTC
- Resolved
- Jul 10, 2026, 04:23 PM UTC
- Duration
- 38m
Affected: Melbourne - Web Isolation (Melbourne - Web Isolation)Frankfurt - Web Isolation (Frankfurt - Web Isolation)Mumbai - Web Isolation (Mumbai - Web Isolation)Jakarta - Web Isolation (Jakarta - Web Isolation)Tokyo - Web Isolation (Tokyo - Web Isolation)Montreal - Web Isolation (Montreal - Web Isolation)Hong Kong - Web Isolation (Hong Kong - Web Isolation)Ohio - Web Isolation (Ohio - Web Isolation)Zurich - Web Isolation (Zurich - Web Isolation)Milan - Web Isolation (Milan - Web Isolation)Oregon - Web Isolation (Oregon - Web Isolation)Dammam - Web Isolation (Dammam - Web Isolation)London - Web Isolation (London - Web Isolation)Paris - Web Isolation (Paris - Web Isolation)Sao Paulo - Web Isolation (Sao Paulo - Web Isolation)Las Vegas - Web Isolation (Las Vegas - Web Isolation)Osaka - Web Isolation (Osaka - Web Isolation)Tel Aviv - Web Isolation (Tel Aviv - Web Isolation)Singapore - Web Isolation (Singapore - Web Isolation)Taiwan - Web Isolation (Taiwan - Web Isolation)Seoul - Web Isolation (Seoul - Web Isolation)North Virginia - Web Isolation (North Virginia - Web Isolation)Sydney - Web Isolation (Sydney - Web Isolation)Bahrain - Web Isolation (Bahrain - Web Isolation)Cape Town - Web Isolation (Cape Town - Web Isolation)Iowa - Web Isolation (Iowa - Web Isolation)UAE - Web Isolation (UAE - Web Isolation)
Timeline · 3 updates
-
investigating Jul 10, 2026, 03:45 PM UTC
We are investigating an issue with rendering a subset of webpages in all regions. We are investigating further. Status updates will be shared here as they become available
-
investigating Jul 10, 2026, 03:54 PM UTC
Operations team is applying a mitigation to address the rendering of the subset of webpages. Further update will be provided as it becomes available.
-
resolved Jul 10, 2026, 04:23 PM UTC
We are pleased to announce that the mitigation has been successfully deployed and all webpages are being rendered successfully This incident has been resolved. Please contact Support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 07:00 AM UTC
- Resolved
- Jul 08, 2026, 02:32 AM UTC
- Duration
- 19h 32m
Affected: Hong Kong - Doc Isolation (Hong Kong - Doc Isolation)
Timeline · 2 updates
-
investigating Jul 07, 2026, 07:00 AM UTC
Menlo Operations is aware of a degradation in the file download and related services. We are actively invetigating the situation.
-
resolved Jul 08, 2026, 02:32 AM UTC
We are pleased to announce that the mitigation has been successfully deployed in HongKong. This incident has been resolved. Please contact Support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 01:16 PM UTC
- Resolved
- Jun 15, 2026, 01:30 PM UTC
- Duration
- 13m
Affected: North Virginia - Proxy (North Virginia - Proxy)
Timeline · 2 updates
-
investigating Jun 15, 2026, 01:16 PM UTC
An issue has been found and is currently under investigation. Customers browsing via the North Virginia region may have experienced degraded performance when browsing via this region. As of 13:10 UTC we have identified and applied mitigation for the issue, and are now continuing to...
-
resolved Jun 15, 2026, 01:30 PM UTC
This incident has been resolved after an extended period of monitoring. Please contact Support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 02:46 AM UTC
- Resolved
- Jun 09, 2026, 03:50 AM UTC
- Duration
- 1h 4m
Affected: Taiwan - Web Isolation (Taiwan - Web Isolation)
Timeline · 2 updates
-
investigating Jun 09, 2026, 02:46 AM UTC
We are investigating page loading errors with the Web Isolation service in Taiwan.
-
resolved Jun 09, 2026, 03:50 AM UTC
We are pleased to announce that the mitigation has been successfully deployed to Web Isolation service in Taiwan region. This incident has been resolved. Please contact Support if you have additional questions.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 03:35 AM UTC
- Resolved
- Jun 09, 2026, 05:26 PM UTC
- Duration
- 5d 13h
Affected: Hong Kong - Web Isolation (Hong Kong - Web Isolation)
Timeline · 3 updates
-
investigating Jun 04, 2026, 03:35 AM UTC
Menlo Operations is aware of reported slowness in the Hong Kong region. We are actively working with our service provider to investigate.
-
investigating Jun 04, 2026, 03:40 AM UTC
Operations has identified a zone experiencing functional issues and has removed the capacity from that zone. Although this does not solve the service degradation fully, it will allow users to reach healthy systems while investigation continues.
-
resolved Jun 09, 2026, 05:26 PM UTC
As this issue is mitigated for Menlo customers we are closing the incident out.
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 12:40 AM UTC
- Resolved
- May 26, 2026, 02:17 AM UTC
- Duration
- 1h 37m
Affected: Tokyo - Web Isolation (Tokyo - Web Isolation)Tokyo - Doc Isolation (Tokyo - Doc Isolation)Tokyo - Proxy (Tokyo - Proxy)
Timeline · 2 updates
-
investigating May 26, 2026, 12:40 AM UTC
Some customers have reported an unstable internet access route through the Menlo Tokyo region, resulting in pages occasionally failing to load completely.
-
resolved May 26, 2026, 02:17 AM UTC
The REDGE team has confirmed that the incident was fully resolved at 00:30 UTC
Read the full incident report →