Menlo Security incident

An Issue has been found with some sites when using the "Allow" mode

Minor Resolved View vendor source →

Menlo Security experienced a minor incident on July 31, 2026 affecting Ohio - Proxy (Ohio - Proxy) and Las Vegas - Proxy (Las Vegas - Proxy) and 1 more component, lasting 2d 22h. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2026, 11:06 AM UTC
Resolved
Aug 03, 2026, 09:48 AM UTC
Duration
2d 22h
Detected by Pingoru
Jul 31, 2026, 11:06 AM UTC

Affected components

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)

Update timeline

  1. investigating Jul 31, 2026, 11:06 AM UTC

    An issue has been found and is currently under investigation. Users may experience some degraded functionality on specific sites whilst using the "Allow" mode. We will update with further information, once we have investigated further.

  2. investigating Jul 31, 2026, 11: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.

  3. investigating Jul 31, 2026, 01:17 PM UTC

    We have found a mitigation and are currently validating it

  4. investigating Jul 31, 2026, 02:34 PM UTC

    We continue to test our mitigation solution. Further information will be provided once this has been validated

  5. investigating Jul 31, 2026, 03:47 PM UTC

    We have validated a fix and are preparing the plan to roll out to all regions. We are aware of additional impact to Australia and are focusing on quick resolution there

  6. investigating Jul 31, 2026, 04:48 PM UTC

    We have validated a fix and are preparing the plan to roll out to all regions. The additional impact to Australia has now been resolved

  7. investigating Jul 31, 2026, 07:47 PM UTC

    Work continues to validate a patch for this issue. Once the patch has been validated we will update with our roll out schedule.

  8. investigating Aug 01, 2026, 10:25 PM UTC

    A fix has been created which is expected to resolve the issue for all customers. It is being deployed worldwide. We will update once deployment completes in all regions.

  9. investigating Aug 02, 2026, 04:44 AM UTC

    Patching has completed. We are continuing to monitor all systems.

  10. resolved Aug 03, 2026, 09:48 AM UTC

    The monitoring confirmed we have fully resolved the issue. User should no longer experience any issue.