SuperTokens Outage History
SuperTokens is up right nowPingoru has recorded 34 incidents for SuperTokens: 33 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 2 | 2 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 6 | 5 of 744 (1%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 510 (0%) |
Incidents, newest first
Minor August 27, 2026 One of our shared instances encountered a deadlock 15m
Started Aug 27, 2026, 03:30 PM UTC· resolved Aug 27, 2026, 03:45 PM UTC
- investigating Aug 27, 2026, 03:30 PM UTC
We are currently investigating this incident..
- resolved Aug 27, 2026, 03:45 PM UTC
This incident has been resolved. Initial investigations show that this deadlock type has been fixed in the latest version..
Minor August 17, 2026 One of our shared development instances started crashing 3h 29m
Started Aug 17, 2026, 02:10 AM UTC· resolved Aug 17, 2026, 05:39 AM UTC
- investigating Aug 17, 2026, 02:10 AM UTC
We are currently investigating this incident..
- identified Aug 17, 2026, 03:11 AM UTC
Identified and implemented a fix, which is now rolling out..
- resolved Aug 17, 2026, 05:39 AM UTC
This incident has been resolved..
Minor August 12, 2026 A user export script and a concurrent vacuum call caused DB overload on a single cluster 1h 35m
Started Aug 12, 2026, 01:30 PM UTC· resolved Aug 12, 2026, 03:05 PM UTC
- investigating Aug 12, 2026, 01:30 PM UTC
We are currently investigating this incident..
- resolved Aug 12, 2026, 03:05 PM UTC
This incident has been resolved..
Major May 8, 2026 A shared database stopped responding, causing an outage in associated instances 1h 40m
Started May 08, 2026, 12:20 AM UTC· resolved May 08, 2026, 02:00 AM UTC
- 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..
Minor March 9, 2026 Database overloading issues in some dev environments in us-east-1 46m
Started Mar 09, 2026, 07:49 PM UTC· resolved Mar 09, 2026, 08:35 PM UTC
- investigating Mar 09, 2026, 07:49 PM UTC
We are currently investigating this incident..
- monitoring Mar 09, 2026, 08:16 PM UTC
We implemented a fix and are currently monitoring the result..
- resolved Mar 09, 2026, 08:35 PM UTC
This incident has been resolved..
Minor March 9, 2026 Planned upgrade of the infrastructure provider (US) – Overall
Started Mar 09, 2026, 08:00 AM UTC· resolved Mar 09, 2026, 08:00 AM UTC
No vendor updates were posted for this incident.
Minor March 9, 2026 Planned upgrade of the infrastructure provider (EU) – Overall
Started Mar 09, 2026, 01:00 AM UTC· resolved Mar 09, 2026, 01:00 AM UTC
No vendor updates were posted for this incident.
Minor March 8, 2026 Planned upgrade of the infrastructure provider (AP) – Overall
Started Mar 08, 2026, 10:00 PM UTC· resolved Mar 08, 2026, 10:00 PM UTC
No vendor updates were posted for this incident.
Minor January 27, 2026 One of our instanced crashed and started automatic recovery 1h 41m
Started Jan 27, 2026, 09:38 AM UTC· resolved Jan 27, 2026, 11:20 AM UTC
- investigating Jan 27, 2026, 09:38 AM UTC
We are currently investigating this incident..
- identified Jan 27, 2026, 09:38 AM UTC
We are continuing to work on a fix for this incident..
- identified Jan 27, 2026, 10:39 AM UTC
We are continuing to work on a fix for this incident..
- resolved Jan 27, 2026, 11:20 AM UTC
This incident has been resolved..
Minor January 26, 2026 A single shared instance was having overloading issues 3m
Started Jan 26, 2026, 09:04 PM UTC· resolved Jan 26, 2026, 09:07 PM UTC
- monitoring Jan 26, 2026, 09:04 PM UTC
We implemented a fix and are currently monitoring the result..
- resolved Jan 26, 2026, 09:07 PM UTC
This incident has been resolved..
Minor December 20, 2025 Planned upgrade of the infrastructure provider (US), deploying security fixes – Overall
Started Dec 20, 2025, 08:00 AM UTC· resolved Dec 20, 2025, 08:00 AM UTC
No vendor updates were posted for this incident.
Minor December 20, 2025 Planned upgrade of the infrastructure provider (EU), deploying security fixes – Overall
Started Dec 20, 2025, 01:00 AM UTC· resolved Dec 20, 2025, 01:00 AM UTC
No vendor updates were posted for this incident.
Minor December 19, 2025 Planned upgrade of the infrastructure provider (AP), deploying security fixes – Overall
Started Dec 19, 2025, 08:00 PM UTC· resolved Dec 19, 2025, 08:00 PM UTC
No vendor updates were posted for this incident.
Minor November 9, 2025 Planned upgrade of the Website and SaaS Dashboard infrastructure – Overall
Started Nov 09, 2025, 11:00 AM UTC· resolved Nov 09, 2025, 11:00 AM UTC
No vendor updates were posted for this incident.
Minor November 8, 2025 Database overloading issues 1h 30m
Started Nov 08, 2025, 11:30 AM UTC· resolved Nov 08, 2025, 01:00 PM UTC
- investigating Nov 08, 2025, 11:30 AM UTC
We are currently investigating this incident..
- resolved Nov 08, 2025, 01:00 PM UTC
This incident has been resolved..
Minor November 4, 2025 Database overloading issue – Overall
Started Nov 04, 2025, 04:00 PM UTC· resolved Nov 04, 2025, 04:00 PM UTC
No vendor updates were posted for this incident.
Minor October 9, 2025 SMS delivery issues due to spam attack – Overall
Started Oct 09, 2025, 09:30 PM UTC· resolved Oct 09, 2025, 09:30 PM UTC
No vendor updates were posted for this incident.