Previous incidents
Checkout is down
Resolved Oct 28, 2022 at 3:42pm UTC
Checkout recovered.
1 previous update
Checkout is down
Resolved Oct 19, 2022 at 11:32pm UTC
Checkout recovered.
1 previous update
Authentication Backend is down
Resolved Oct 18, 2022 at 8:30pm UTC
The root cause has been fixed. This is now resolved.
2 previous updates
Temporary issue with our cloud provider
Resolved Oct 17, 2022 at 7:28pm UTC
Everything is back to normal
6 previous updates
Some services are down
Resolved Oct 11, 2022 at 3:10pm UTC
The maintenance is now complete and everything should be working as expected
2 previous updates
Ingests Unavailable
Resolved Oct 6, 2022 at 10:50pm UTC
We have identified the issue and implemented a fix. Further fixes to harden our services will continue to roll out.
1 previous update
API Unavailable in North America
Resolved Oct 6, 2022 at 10:09pm UTC
API availablity in North America and surrounding areas was comprimised for a period of time. This should now be resolved and we are looking at ways of failing over to other regions automatically in the event of errors in one region.
Checkout is down
Resolved Sep 27, 2022 at 1:28pm UTC
Checkout recovered.
1 previous update
Twitch streaming down
Resolved Sep 21, 2022 at 8:34pm UTC
This issue is now resolved
2 previous updates
Authentication Backend is down
Resolved Aug 15, 2022 at 5:48am UTC
Authentication Backend recovered.
1 previous update
Authentication Backend is down
Resolved Aug 14, 2022 at 3:32pm UTC
Authentication Backend recovered.
1 previous update
API, Authentication Frontend, Checkout, and 1 other service are down
Resolved Aug 13, 2022 at 5:57am UTC
Authentication Frontend recovered.
5 previous updates
API is down
Resolved Aug 12, 2022 at 3:13pm UTC
API recovered.
1 previous update
Some services are down
Resolved Aug 5, 2022 at 12:21am UTC
The concurrency limit has now been increased, and misconfigured autoscaling settings which would have caused the limit to scale up the service in response to reaching the limit, is now correctly configured. This incident is now resolved.
2 previous updates