Expedited Security driftsforstyrrelser

1. 17. september 2026 kl. 10.31 UTCinvestigating

   Vi ser et forhøjet niveau af fejl, når du læser eller opdaterer WAF indstillinger, herunder IP-tilladelse og blokere lister, gennem både den Udbetalte WAF API og Management Dashboard. Anmodninger kan mislykkes, eller der kan forekomme tomme lister. Trafikbeskyttelse berøres ikke. Alle websteder forbliver online og fortsat være beskyttet og serveret normalt.

2. 17. september 2026 kl. 12.08 UTCinvestigating

   Vores ingeniørteam fortsætter med at undersøge og arbejder på at genoprette fuld indstillinger management funktionalitet. Trafikbeskyttelse er ikke påvirket, og alle websteder er online og tjener normalt.

3. 17. september 2026 kl. 12.53 UTCinvestigating

   Vi fortsætter med at arbejde på at genoprette indstillinger management. Trafikbeskyttelse er ikke påvirket, og alle websteder er online og tjener normalt.

4. 17. september 2026 kl. 13.44 UTCinvestigating

   Arbejdet fortsætter med at genoprette fuld indstillinger management funktionalitet. Trafikbeskyttelse er upåvirket, og alle websteder forbliver online og tjener normalt.

5. 17. september 2026 kl. 14.15 UTCinvestigating

   Vores team arbejder stadig aktivt på dette spørgsmål og genskaber indstillingerne management. Trafikbeskyttelse er ikke påvirket, og alle websteder er online og tjener normalt.

6. 17. september 2026 kl. 14.25 UTCresolved

   Indstillinger management funktionalitet er blevet fuldt restaureret. Læsning og opdatering af WAF-indstillinger, herunder IP-tillader og blokere lister, fungerer normalt igen gennem både API og Management Dashboard. Trafikbeskyttelse var upåvirket af denne hændelse, og alle websteder forblev online. Hvis du lavede IP-listeændringer mellem 16 september, 6: 30 PM UTC og 17 september, 2: 30 PM UTC, skal du kontrollere, at de blev anvendt og re- indsende eventuelle, der ikke var. Vi undskylder ulejligheden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 5. februar 2024 kl. 22.38 UTCidentified

   We've identified an issue with network interconnect services in our EU and Southeast US regions, preventing requests from being completed. Requests to sites outside of those regions are unaffected.

2. 5. februar 2024 kl. 22.50 UTCresolved

   We are continuing to monitor the affected networks for further issues, but all operations have been restored.

1. 6. september 2022 kl. 13.42 UTCidentified

   We detected an account desync issue that is preventing access to the WAF Management Dashboard for some Expedited WAF users. The cause of the issue has been determined, and engineers are working on resolving it.

2. 6. september 2022 kl. 16.12 UTCresolved

   This incident has been resolved. We apologize for any disruption this may have caused. If you're continuing to see errors please contact [email protected]

1. 24. august 2022 kl. 00.53 UTCinvestigating

   Heroku is experiencing issues with their upstream DNS provider. As the WAF and CDN target Heroku DNS domains as their origins, our Edge Network can't connect to Heroku. If connections into Heroku are unable to be made, a HTTP status code of 502 is returned along with a brief HTML error page describing the issue. As Heroku resolves their upstream DNS issues sites will immediately come back online with no further intervention needed. For the most recent updates, please follow Heroku's Status Page at: https://status.heroku.com/

2. 24. august 2022 kl. 12.16 UTCinvestigating

   Heroku's issues with their upstream DNS provider have been resolved. Please continue to follow https://status.heroku.com for further updates from them.

3. 24. august 2022 kl. 12.16 UTCresolved

   This incident has been resolved.

1. 10. juli 2022 kl. 01.22 UTCinvestigating

   A small number of accounts are experiencing timeout errors after SSO from their Heroku applications. We have traced the cause to an edge case in how accounts are provisioned and are actively working on a solution.

2. 10. juli 2022 kl. 01.22 UTCinvestigating

   We are continuing to investigate this issue.

3. 11. juli 2022 kl. 21.05 UTCinvestigating

   We have identified the source of the issue causing some accounts to error after logging in via SSO linking from their Heroku dashboards. Throughout this outage, the external WAF interface has continued to protect all sites.

4. 11. juli 2022 kl. 23.54 UTCresolved

   This incident has been resolved. To check if you can access your WAF dashboard correctly now, click on the Expedited WAF or Expedited CDN add-on in your Heroku Application's resources tab. If you have any further issues please report them to support@expeditedsecurity We apologize for the inconvenience that this has caused and are taking steps to modify the underlying procedures and checks that led to the dashboard control plane becoming out of sync with the larger Edge Network.

1. 8. juni 2021 kl. 21.28 UTCresolved

   Some clients began experiencing extended latency resulting in reaching origin servers as a result of an upstream bandwidth provider outage. Network services are monitoring the situation as traffic is moved to alternate providers.

1. 9. februar 2021 kl. 17.23 UTCmonitoring

   Heroku is currently experiencing issues with their Platform API. This is preventing the creation of new WAF instances as we are dependent upon API responses to configure the WAF. WAFs in the process of being provisioned are also delayed as a result. Existing WAF clients are unaffected.

2. 9. februar 2021 kl. 20.37 UTCresolved

   Heroku has resolved their issues with the Platform API and all issues are resolved.

1. 31. januar 2021 kl. 15.29 UTCinvestigating

   We're currently investigating a delay in the provisioning of new WAF instances. This does not affect the normal throughput of traffic for existing WAF clients.

2. 31. januar 2021 kl. 15.32 UTCinvestigating

   We have identified the issue and provisioning times have returned to normal limits.

3. 31. januar 2021 kl. 15.33 UTCresolved

   This incident has been resolved.

1. 18. januar 2021 kl. 13.29 UTCresolved

   A Webfont icon library used in the dashboard was failing to load due to network issues. Upon replacement, with a locally cached version, the issues resolved and the dashboard is loading normally.

1. 8. januar 2021 kl. 20.32 UTCresolved

   We have received reports that a mobile ISP in Thailand has misconfigured their network routing. This has resulted in traffic timing out before it hits our Edge network. We have reported the issue but are unable to directly change their routing to fix the error.

2. 8. januar 2021 kl. 20.33 UTCpostmortem

   After approximately 6 hours the network errors were resolved and connections stopped timing out.