Supabase logo
MAJOR OUTAGE DETECTED

Supabase is currently
experiencing a major outage.

Pulsetic detects outages before the provider officially reports them. Monitoring since Feb 2026 · 71 incidents caught

Last checked: 6 min ago · 1 user report (24h) · Trusted by 30,000+ teams

Report an outage
  • MAJOR · MONITORING

    DNS record creation failures impacting project creation, restore, pause

    Started 1 hour ago · Jun 18, 2026 · 6:39 AM UTC

    We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes.


  • User Reports: Last 24 Hours

    1 report

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    1 report (24h)

    Reports by region (last 24h)

    North America 1 (100%)
  • Recent User Reports

    Live

    Updating in real-time

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Degraded performance 1
    Service outage 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

    Report an outage
  • Issue breakdown

    1 total vote

    Distribution of reported issues over the last 24 hours.

    Degraded performance 100%
    Service outage 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

Last 90 days

90-Day Health Summary

  • Total Incidents

    41

    Since Feb 2026

  • Major / Critical

    15

    15 high-impact incidents

  • Minor Incidents

    26

    Avg. 0.3 per day

  • Median Resolution

    1h 50m

    P95: 196h 36m

Supabase Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
DNS record creation failures impacting project creation, restore, pause
Jun 18, 2026 · 6:39 AM Ongoing
Major
Monitoring
Details →
Hardware failure in us-east
Jun 17, 2026 · 3:12 PM 1h 50m
Minor
Resolved
Details →
Degraded Management API performance affecting payments and Supabase Studio
Jun 17, 2026 · 12:31 PM 1h 39m
Major
Resolved
Details →
Project usage analytics API endpoints breakage
Jun 16, 2026 · 3:47 PM 1h 14m
Minor
Resolved
Details →
Degraded Log Explorer in the dashboard
Jun 16, 2026 · 11:26 AM 3h 42m
Minor
Resolved
Details →
Storage users in US-West-2 experiencing increased latency on storage requests
Jun 12, 2026 · 4:00 PM 8h 39m
Minor
Resolved
Details →
Higher connection failure rate for ap-northeast-1 and ap-northeast-2
Jun 10, 2026 · 12:00 AM < 1m
None
Resolved
Details →
DNS Resolution Failures for TLD .co users
Jun 8, 2026 · 3:39 AM 8d 4h 36m
None
Resolved
Details →
Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)
Jun 2, 2026 · 1:36 PM 1h 5m
Critical
Resolved
Details →
Branch creation degradation
May 21, 2026 · 4:46 PM 2h 39m
Minor
Resolved
Details →

How do they compare?

Alternatives to Supabase

Teams monitoring Supabase also watch

Other Monitored Services

Get alerted the moment Supabase goes down.

No credit card · free plan · 2-minute setup

Common questions

Frequently Asked Questions

  • Is Supabase down today?

    Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

  • How often does Supabase go down?

    Based on our 90-day data, we've detected 41 incidents, of which 15 were major or critical. The median resolution time is 1h 50m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.