Menlo Security incident

Web Isolation Issue in Incognito/Private Browsing

Minor Resolved View vendor source →

Menlo Security experienced a minor incident on March 5, 2026 affecting Melbourne - Web Isolation (Melbourne - Web Isolation) and Frankfurt - Web Isolation (Frankfurt - Web Isolation) and 1 more component, lasting 1d 10h. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2026, 11:10 AM UTC
Resolved
Mar 06, 2026, 09:56 PM UTC
Duration
1d 10h
Detected by Pingoru
Mar 05, 2026, 11:10 AM UTC

Affected components

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)

Update timeline

  1. identified Mar 05, 2026, 11:10 AM UTC

    An issue has been detected with web isolation that may affect a subset of customers. Further information and status updates will be shared here as they become available

  2. investigating Mar 05, 2026, 12:10 PM 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.

  3. investigating Mar 05, 2026, 01:58 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 web isolation services. Further information will be shared as it becomes available

  4. investigating Mar 05, 2026, 03:49 PM UTC

    We have identified the cause of the issue and have developed a fix, which is currently still undergoing validation. Upon successful validation, this will be deployed to web isolation services. Further information will be shared as it becomes available

  5. investigating Mar 05, 2026, 05:56 PM UTC

    We have identified the root cause and prepared a fix. The update is currently in the validation stage, and once testing is complete, it will be rolled out to all regions. We will provide further updates as progress continues

  6. investigating Mar 05, 2026, 07:32 PM UTC

    We have identified the cause of the issue and developed a fix, which is currently undergoing validation. Once validation is complete, we will deploy the fix to the affected regions. This is a temporary issue impacting Web Isolation specifically when using Incognito/Private browsing windows....

  7. investigating Mar 05, 2026, 09:41 PM UTC

    The fix has been validated and confirmed effective. Deployment to the affected regions is in progress. Next update: once deployment is complete.

  8. investigating Mar 06, 2026, 12:32 AM UTC

    Impact has been resolved for Web Isolation in the Singapore and Seoul regions. We are continuing deployment to the remaining affected regions and will provide updates as rollout progresses.

  9. investigating Mar 06, 2026, 09:40 AM UTC

    Impact has been resolved for Web Isolation in the Singapore, Seoul, Ohio, Montreal, Sao Paulo, North Virginia, Iowa, South Carolina, North California, Las Vegas and Oregon regions. We are continuing deployment to the remaining affected regions and will provide updates as rollout progresses.

  10. investigating Mar 06, 2026, 02:50 PM UTC

    Impact has been resolved for Web Isolation in the Singapore, Seoul, Ohio, Montreal, Sao Paulo, North Virginia, Iowa, South Carolina, North California, Las Vegas, Oregon, Melbourne, Jakarta, Sydney, Taiwan, Mumbai and Hong Kong regions. We are continuing deployment to the remaining affected...

  11. investigating Mar 06, 2026, 05:47 PM UTC

    Impact has been resolved for Web Isolation in the Singapore, Seoul, Ohio, Montreal, Sao Paulo, North Virginia, Iowa, South Carolina, North California, Las Vegas, Oregon, Melbourne, Jakarta, Sydney, Taiwan, Mumbai, Hong Kong, Tokyo and Osaka regions. We are continuing deployment to the remaining...

  12. resolved Mar 06, 2026, 09:56 PM UTC

    This incident has been resolved. Please contact Support if you have additional questions