SuperTokens incident
A shared database stopped responding, causing an outage in associated instances
Major Vendor's status page →
Resolved after 1 hour 40 minutes, on May 8, 2026.
We implemented a fix and are currently monitoring the result..
Other major vendors with incidents that started within 30 minutes of this one
Amazon Web Services Outage Amazon Elastic Compute Cloud — N. Virginia: [RESOLVED] Increased Error Rate and LatencyUpdate timeline
- investigating May 08, 2026, 12:20 AM UTC
We are currently investigating this incident..
- identified May 08, 2026, 12:47 AM UTC
Rebooting db instance.
- identified May 08, 2026, 01:29 AM UTC
We are experiencing a database outage caused by an AWS infrastructure incident in us-east-1b (thermal event / power loss affecting use1-az4). We are monitoring recovery and moving the db instance to a different AZ..
- monitoring May 08, 2026, 01:50 AM UTC
We implemented a fix and are currently monitoring the result..
- resolved May 08, 2026, 02:00 AM UTC
This incident has been resolved..
Your product runs on more than SuperTokens
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services