SuperTokens Outage History

SuperTokens is up right now

SuperTokens had 17 outages in the last 2 years totaling 11h 1m of downtime — averaging 0.7 incidents per month.

There were 17 SuperTokens outages since October 9, 2025 totaling 11h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://supertokens.instatus.com

Minor August 27, 2026

One of our shared instances encountered a deadlock

Detected by Pingoru
Aug 27, 2026, 03:30 PM UTC
Resolved
Aug 27, 2026, 03:45 PM UTC
Duration
15m
Timeline · 2 updates
  1. investigating Aug 27, 2026, 03:30 PM UTC

    We are currently investigating this incident..

  2. 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..

Read the full incident report →

Minor August 17, 2026

One of our shared development instances started crashing

Detected by Pingoru
Aug 17, 2026, 02:10 AM UTC
Resolved
Aug 17, 2026, 05:39 AM UTC
Duration
3h 29m
Timeline · 3 updates
  1. investigating Aug 17, 2026, 02:10 AM UTC

    We are currently investigating this incident..

  2. identified Aug 17, 2026, 03:11 AM UTC

    Identified and implemented a fix, which is now rolling out..

  3. resolved Aug 17, 2026, 05:39 AM UTC

    This incident has been resolved..

Read the full incident report →

Major May 8, 2026

A shared database stopped responding, causing an outage in associated instances

Detected by Pingoru
May 08, 2026, 12:20 AM UTC
Resolved
May 08, 2026, 02:00 AM UTC
Duration
1h 40m
Timeline · 5 updates
  1. investigating May 08, 2026, 12:20 AM UTC

    We are currently investigating this incident..

  2. identified May 08, 2026, 12:47 AM UTC

    Rebooting db instance.

  3. 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..

  4. monitoring May 08, 2026, 01:50 AM UTC

    We implemented a fix and are currently monitoring the result..

  5. resolved May 08, 2026, 02:00 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 9, 2026

Database overloading issues in some dev environments in us-east-1

Detected by Pingoru
Mar 09, 2026, 07:49 PM UTC
Resolved
Mar 09, 2026, 08:35 PM UTC
Duration
46m
Timeline · 3 updates
  1. investigating Mar 09, 2026, 07:49 PM UTC

    We are currently investigating this incident..

  2. monitoring Mar 09, 2026, 08:16 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Mar 09, 2026, 08:35 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor January 27, 2026

One of our instanced crashed and started automatic recovery

Detected by Pingoru
Jan 27, 2026, 09:38 AM UTC
Resolved
Jan 27, 2026, 11:20 AM UTC
Duration
1h 41m
Timeline · 4 updates
  1. investigating Jan 27, 2026, 09:38 AM UTC

    We are currently investigating this incident..

  2. identified Jan 27, 2026, 09:38 AM UTC

    We are continuing to work on a fix for this incident..

  3. identified Jan 27, 2026, 10:39 AM UTC

    We are continuing to work on a fix for this incident..

  4. resolved Jan 27, 2026, 11:20 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor November 8, 2025

Database overloading issues

Detected by Pingoru
Nov 08, 2025, 11:30 AM UTC
Resolved
Nov 08, 2025, 01:00 PM UTC
Duration
1h 30m
Timeline · 2 updates
  1. investigating Nov 08, 2025, 11:30 AM UTC

    We are currently investigating this incident..

  2. resolved Nov 08, 2025, 01:00 PM UTC

    This incident has been resolved..

Read the full incident report →