Is SuperTokens down?
Last checked 1m agoNo active incidents. All 14 components operational.
SuperTokens is operational right now. Last checked 1m ago; the most recent incident resolved 62d ago.
Real-time SuperTokens status, recent outages, and incident history: pulled directly from SuperTokens's official status page at supertokens.instatus.com every 5 minutes. Pingoru tracks 14 SuperTokens services and has captured 3 incidents in the last 90 days (99.98% uptime). Get email, Slack, Discord, or webhook alerts the moment SuperTokens reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Production environment
Timeline · 4 updates
- investigating · Aug 27, 2026, 03:30 PM UTC
We are currently investigating this incident.
- 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.
- 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..
Latest: This incident has been resolved. Initial investigations show that this deadlock type has been fixed in the latest version..
-
- Development environment
Timeline · 6 updates
- investigating · Aug 17, 2026, 02:10 AM UTC
We are currently investigating this incident.
- 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.
- 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..
- resolved · Aug 17, 2026, 05:39 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Production environment
Timeline · 4 updates
- investigating · Aug 12, 2026, 01:30 PM UTC
We are currently investigating this incident.
- 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.
- resolved · Aug 12, 2026, 03:05 PM UTC
This incident has been resolved..
Latest: This incident has been resolved..
-
Incident record
Since April 2026 · Instatus · 14 components checked every 5 minutesThe longest incident in the last year, One of our shared development instances started crashing on August 17, 2026, ran for 3 hours. 22 maintenance windows announced in the same period.
Most affected components, last 12 months
- Production environment3
- Development environment1
Latest incidents
- One of our shared instances encountered a deadlock
We are currently investigating this incident.
- One of our shared development instances started crashing
We are currently investigating this incident.
- A user export script and a concurrent vacuum call caused DB overload on a single cluster
We are currently investigating this incident.
- Started Aug 27, 2026, 03:30 PM UTC · Resolved Aug 27, 2026, 03:45 PM UTC · 15m
- Started Aug 17, 2026, 02:10 AM UTC · Resolved Aug 17, 2026, 05:39 AM UTC · 3h 29m
- Started Aug 12, 2026, 01:30 PM UTC · Resolved Aug 12, 2026, 03:05 PM UTC · 1h 35m