Over after 32 min10 Nov

Check failures in the Amsterdam group

104 services stopped answering in 1 monitoring group for 32 min, from 20:23 to 20:54.

Failing, minute by minute

1040
20:2320:54

Monitoring-group history

  1. Amsterdam20:23

What the status pages said

What it took down

Services

Timeline

  1. 20:23It began: Amsterdam
  2. 20:54It was over
  3. 21:00Twilio's status page admitted it
  4. 21:00Epic Games's status page admitted it
  5. 21:03MongoDB Atlas's status page admitted it
  6. 21:03OVHcloud's status page admitted it
  7. 21:03Akamai Cloud (Linode)'s status page admitted it
  8. 21:03Scaleway's status page admitted it
  9. 21:03Cloudflare's status page admitted it
  10. 21:03Fastly's status page admitted it
  11. 21:03Akamai's status page admitted it
  12. 21:03bunny.net's status page admitted it
  13. 21:03Notion's status page admitted it
  14. 21:03Zoom's status page admitted it
  15. 21:22Sentry's status page admitted it
Check failures in the Amsterdam group, 10 Nov · SkyCISA