SuperTokens had 20 outages in the last 2 years totaling 1h 40m of downtime — averaging 0.8 incidents per month.
There were 20 SuperTokens outages since October 9, 2025 totaling 1h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.
Type: Maintenance Duration: 2 hours Affected Components: Development environment, Production environment Sep 5, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 5, 09:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 2, 09:29:17 GMT+0 - Identified - We are planning for a scheduled maintenance during that time.
Type: Maintenance Duration: 2 hours Affected Components: Development environment, Production environment Sep 5, 00:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 5, 02:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 2, 09:28:30 GMT+0 - Identified - We are planning for a scheduled maintenance during that time.
Type: Maintenance Duration: 2 hours Affected Components: Development environment, Production environment Sep 4, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 4, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 2, 09:27:22 GMT+0 - Identified - We are planning for a scheduled maintenance during that time.
Type: Incident Duration: 15 minutes Affected Components: Production environment Aug 27, 15:30:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 27, 15:45:00 GMT+0 - Resolved - This incident has been resolved. Initial investigations show that this deadlock type has been fixed in the latest version.
Type: Incident Duration: 3 hours and 30 minutes Affected Components: Development environment Aug 17, 02:10:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 17, 03:11:00 GMT+0 - Identified - Identified and implemented a fix, which is now rolling out. Aug 17, 05:39:58 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 35 minutes Affected Components: Production environment Aug 12, 13:30:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 12, 15:05:00 GMT+0 - Resolved - This incident has been resolved.
Type: Maintenance Duration: 1 hour and 22 minutes Affected Components: Production environment May 21, 07:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. May 21, 07:00:01 GMT+0 - Identified - Maintenance is now in progress May 21, 08:22:30 GMT+0 - Completed - Maintenance has completed successfully.
Type: Maintenance Duration: 2 hours Affected Components: Development environment, Production environment May 18, 07:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. May 18, 07:30:01 GMT+0 - Identified - Maintenance is now in progress May 18, 09:30:00 GMT+0 - Completed - Maintenance has completed successfully
Type: Maintenance Duration: 16 minutes Affected Components: Production environment May 16, 23:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. May 16, 23:00:01 GMT+0 - Identified - Maintenance is now in progress May 16, 23:15:52 GMT+0 - Completed - Maintenance has completed successfully.
We are currently investigating this incident.
Rebooting db instance
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.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
Type: Incident Duration: 47 minutes Affected Components: Development environment Mar 9, 19:49:12 GMT+0 - Investigating - We are currently investigating this incident. Mar 9, 20:16:06 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 9, 20:35:46 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 42 minutes Affected Components: Production environment Jan 27, 09:38:45 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jan 27, 10:39:04 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jan 27, 11:20:27 GMT+0 - Resolved - This incident has been resolved. Jan 27, 09:38:34 GMT+0 - Investigating - We are currently investigating this incident.
Type: Incident Duration: 4 minutes Affected Components: Production environment Jan 26, 21:04:14 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 26, 21:07:47 GMT+0 - Resolved - This incident has been resolved.
Type: Maintenance Duration: 2 hours Affected Components: Development environment, Production environment Dec 20, 08:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Dec 20, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 20, 10:00:00 GMT+0 - Completed - Maintenance has completed successfully
Type: Maintenance Duration: 2 hours Affected Components: Development environment, Production environment Dec 20, 01:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Dec 20, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 20, 03:00:00 GMT+0 - Completed - Maintenance has completed successfully
Type: Maintenance Duration: 2 hours Affected Components: Development environment, Production environment Dec 19, 20:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Dec 19, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 19, 22:00:00 GMT+0 - Completed - Maintenance has completed successfully
Type: Maintenance Duration: 1 hour Affected Components: Website Nov 9, 11:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Nov 9, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 9, 12:00:00 GMT+0 - Completed - Maintenance has completed successfully
Type: Incident Duration: 1 hour and 30 minutes Affected Components: Production environment Nov 8, 11:30:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 8, 13:00:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 38 minutes Affected Components: Production environment Nov 4, 16:00:10 GMT+0 - Investigating - We are currently investigating this incident. Nov 4, 16:57:10 GMT+0 - Investigating - We are currently investigating this incident. Nov 4, 17:38:33 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 19 minutes Affected Components: Email and SMS Service Oct 9, 21:30:36 GMT+0 - Investigating - We are currently investigating this incident. Oct 9, 21:50:00 GMT+0 - Resolved - This incident has been resolved.