Is SuperTokens down?

Last checked 5m ago
Current status
SuperTokens is up

No incidents right now.

Official status page: https://supertokens.instatus.com · Polled every 5 minutes · 14 components tracked

SuperTokens is operational right now. Last checked 5m ago; the most recent incident resolved 24d ago.

Real-time SuperTokens status, recent outages, and incident history — pulled directly from SuperTokens's official status page at https://supertokens.instatus.com every 5 minutes. Pingoru tracks 14 SuperTokens services and has captured 8 incidents in the last 90 days (99.52% uptime). Get email, Slack, Discord, or webhook alerts the moment SuperTokens reports a new incident — free for 5 monitors, no credit card.

Users who monitor SuperTokens also follow these Authentication services: Clerk Magensa WorkOS Login.gov Okta FGA Accredible RRPproxy Proxyrack BoldSign MetaMap View all 6,000+ providers
SuperTokens uptime 99.52% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 21, 2026, 07:00 AM UTC · Resolved May 21, 2026, 07:00 AM UTC
    Timeline · 1 update
    • resolved · May 21, 2026, 07:00 AM UTC

      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.

    Latest: 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 duri…

  2. Resolved
    Started May 18, 2026, 07:30 AM UTC · Resolved May 18, 2026, 07:30 AM UTC
    Timeline · 1 update
    • resolved · May 18, 2026, 07:30 AM UTC

      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

    Latest: 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 maint…

  3. Resolved
    Started May 16, 2026, 11:00 PM UTC · Resolved May 16, 2026, 11:00 PM UTC
    Timeline · 1 update
    • resolved · May 16, 2026, 11:00 PM UTC

      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.

    Latest: 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 tim…

  4. Resolved
    Started May 08, 2026, 12:20 AM UTC · Resolved May 08, 2026, 12:20 AM UTC
    Timeline · 1 update
    • resolved · May 08, 2026, 12:42 AM UTC

      Type: Incident Affected Components: Production environment May 8, 00:42:42 GMT+0 - Investigating - We are currently investigating this incident.

    Latest: Type: Incident Affected Components: Production environment May 8, 00:42:42 GMT+0 - Investigating - We are currently investigating this incident.

  5. Resolved 1h 40m
    Started May 08, 2026, 12:20 AM UTC · Resolved May 08, 2026, 02:00 AM UTC
    Production environment
    Timeline · 5 updates
    • 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.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 5 incidents View full outage history →