Skip to main content

Clerk 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: Clerk and Supabase
Last 30 daysClerkSupabase
Front door reachableOut of checks with a clear answer
  • 2,256 of 2,256

    checks to api.clerk.com

  • 735 of 735

    checks to 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.

Clerk · check scope

  • api.clerk.comapi · No vendor region

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

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

    First check in this window
    Latest clear answer
View Clerk record

Supabase · check scope

  • api.supabase.comapi · No vendor region

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

    1,523 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: Clerk and Supabase
Last 30 daysClerkSupabase
Incidents recorded

2

18

Recorded incident durationMedian

Too few dated records

2 valid durations

1h 42m

17 valid durations

Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded, as are records posted with one time for start and resolution. 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.

Clerk says

  • Elevated error rates for authentication requests

    Started
    Closed in record
    Source incident
  • SMS Delivery Issues

    Started
    Closed in record
    Source incident

Supabase says

  • Gateway availability disruption

    Started
    Closed in record
    Source incident
  • Edge Function Issues in ap-northeast-1

    Started
    Closed in record
    Source incident
  • ‘Project not specified’ errors reported for users in ap-northeast-2

    Started
    Closed in record
    Source incident

Check the terms for your plan

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

Clerk

No public terms recorded here.

Review Clerk SLA guide

Supabase

1 public term record.

Product not specified

Review Supabase SLA guide