Skip to main content

Auth0 vs Supabase

Front door check counts, what each vendor’s status page recorded and SLA terms for these vendors.

30-day window ending

Front door checks

Every 15 minutes we send a request to a documented endpoint for each vendor from a single CheckUpstream location and count the answers. A reachable front door does not confirm that a customer action worked.

Front door check counts: Auth0 and Supabase
Last 30 daysAuth0Supabase
Front door reachableOut of checks with a clear answer
  • 2,879 of 2,879

    checks to login.auth0.com

  • No clear answer in 24 hours

    from api.supabase.com

Checks 15 minutes apart cannot see disruptions shorter than that. Each vendor is checked at its own endpoints, so the counts cover different things.

Auth0 · check scope

  • login.auth0.comapi · No vendor region

    Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    First check in this window
    Latest clear answer
View Auth0 record

Supabase · check scope

  • api.supabase.comapi · No vendor region

    No clear answer in 24 hours. The counts below are from before this check went quiet.

    Front door reachable in 2,073 of 2,073 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    806 more checks gave no clear answer and are not counted.

    First check in this window
    Latest clear answer
View Supabase record

What each vendor’s status page says

Recorded starts in the same 30-day window, excluding maintenance. Vendors report incidents differently; fewer posts don’t prove better reliability.

Recorded incidents: Auth0 and Supabase
Last 30 daysAuth0Supabase
Incidents recorded

3

16

Recorded incident durationMedian

Too few dated records

3 valid durations

1h 51m

13 valid durations

Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not mean an outage is ongoing.

Auth0 says

  • Elevated Errors on US-4 Public Cloud

    Started
    Closed in record
    Source incident
  • We have detected an issue.

    Started
    Closed in record
    Source incident
  • Elevated Errors on US-5 Public Cloud

    Started
    Closed in record
    Source incident

Supabase says

  • Realtime latency

    Started
    Closure
    Not recorded
  • Edge Function Degradation

    Started
    Closure
    Not recorded
  • Log ingestion impaired

    Started
    Closure
    Not recorded

Check the terms for your plan

An SLA applies to specific products and plans. Credit eligibility also depends on exclusions, evidence and filing deadlines.

Auth0

1 public term record.

Product not specified

Review Auth0 SLA guide

Supabase

1 public term record.

Product not specified

Review Supabase SLA guide