Skip to main content
down.guideby Sazabi
Providers
Is Supabase down? · Data and storage

Supabase is up

OperationalNo known problems: Supabase's status page says operational

99.95% uptime, since Aug 11Last incident Checked Official status pageHistory

Reports count in aggregate against normal levels; one alone never makes a claim.

Now

Open incidents

What Supabase has posted and not resolved.

Supabase has no open incidents.

90 days

Daily history

Worst impact each day, from the provider's own incidents.

  1. 2026-08-09: no data
  2. 2026-08-10: no data
  3. 2026-08-11: 1 incident, worst degraded
  4. 2026-08-12: no incidents
  5. 2026-08-13: no incidents
  6. 2026-08-14: 2 incidents, worst degraded
  7. 2026-08-15: 1 incident, worst degraded
  8. 2026-08-16: 1 incident, worst degraded
  9. 2026-08-17: 2 incidents, worst degraded
  10. 2026-08-18: 1 incident, worst degraded
  11. 2026-08-19: 2 incidents, worst degraded
  12. 2026-08-20: 1 incident, worst degraded
  13. 2026-08-21: 2 incidents, worst degraded
  14. 2026-08-22: 1 incident, worst degraded
  15. 2026-08-23: 1 incident, worst degraded
  16. 2026-08-24: 5 incidents, worst degraded
  17. 2026-08-25: 1 incident, worst degraded
  18. 2026-08-26: 2 incidents, worst degraded
  19. 2026-08-27: 3 incidents, worst degraded
  20. 2026-08-28: 3 incidents, worst degraded
  21. 2026-08-29: 2 incidents, worst degraded
  22. 2026-08-30: 2 incidents, worst degraded
  23. 2026-08-31: 3 incidents, worst degraded
  24. 2026-09-01: 2 incidents, worst major outage
  25. 2026-09-02: 1 incident, worst degraded
  26. 2026-09-03: 1 incident, worst degraded
  27. 2026-09-04: 2 incidents, worst degraded
  28. 2026-09-05: 1 incident, worst degraded
  29. 2026-09-06: 1 incident, worst degraded
  30. 2026-09-07: 1 incident, worst degraded
  31. 2026-09-08: 1 incident, worst degraded
  32. 2026-09-09: 2 incidents, worst degraded
  33. 2026-09-10: 2 incidents, worst degraded
  34. 2026-09-11: 2 incidents, worst degraded
  35. 2026-09-12: 1 incident, worst degraded
  36. 2026-09-13: 1 incident, worst degraded
  37. 2026-09-14: 1 incident, worst degraded
  38. 2026-09-15: 1 incident, worst degraded
  39. 2026-09-16: 4 incidents, worst partial outage
  40. 2026-09-17: 1 incident, worst degraded
  41. 2026-09-18: 1 incident, worst degraded
  42. 2026-09-19: 2 incidents, worst degraded
  43. 2026-09-20: 1 incident, worst degraded
  44. 2026-09-21: 1 incident, worst degraded
  45. 2026-09-22: 2 incidents, worst degraded
  46. 2026-09-23: 4 incidents, worst degraded
  47. 2026-09-24: 4 incidents, worst major outage
  48. 2026-09-25: 1 incident, worst degraded
  49. 2026-09-26: 1 incident, worst degraded
  50. 2026-09-27: 1 incident, worst degraded
  51. 2026-09-28: 2 incidents, worst degraded
  52. 2026-09-29: 1 incident, worst degraded
  53. 2026-09-30: no incidents
  54. 2026-10-01: no incidents
  55. 2026-10-02: no incidents
  56. 2026-10-03: no incidents
  57. 2026-10-04: no incidents
  58. 2026-10-05: no incidents
  59. 2026-10-06: 2 incidents, worst degraded
  60. 2026-10-07: no incidents
  61. 2026-10-08: no incidents
  62. 2026-10-09: no incidents
  63. 2026-10-10: no incidents
  64. 2026-10-11: no incidents
  65. 2026-10-12: 3 incidents, worst degraded
  66. 2026-10-13: 3 incidents, worst degraded
  67. 2026-10-14: 1 incident, worst degraded
  68. 2026-10-15: no incidents
  69. 2026-10-16: no incidents
  70. 2026-10-17: 1 incident, worst degraded
  71. 2026-10-18: no incidents
  72. 2026-10-19: 1 incident, worst degraded
  73. 2026-10-20: 1 incident, worst degraded
  74. 2026-10-21: 2 incidents, worst partial outage
  75. 2026-10-22: 3 incidents, worst partial outage
  76. 2026-10-23: 1 incident, worst degraded
  77. 2026-10-24: 1 incident, worst degraded
  78. 2026-10-25: 1 incident, worst degraded
  79. 2026-10-26: 1 incident, worst degraded
  80. 2026-10-27: no incidents
  81. 2026-10-28: 1 incident, worst degraded
  82. 2026-10-29: no incidents
  83. 2026-10-30: 1 incident, worst degraded
  84. 2026-10-31: 1 incident, worst degraded
  85. 2026-11-01: no incidents
  86. 2026-11-02: 1 incident, worst degraded
  87. 2026-11-03: 1 incident, worst degraded
  88. 2026-11-04: 2 incidents, worst degraded
  89. 2026-11-05: 2 incidents, worst degraded
  90. 2026-11-06: no incidents
90 days agoToday
Reliability

Last 90 days in numbers

From the provider's own posts, including history read from its archive.

Uptime
99.95%since Aug 11
Incidents
56on 68 days
Median duration
2h
Longest
46d 16h
Postmortem rate
50%partial and major outages
Reports

People reporting problems

Hourly counts, last 24 hours.

No reports in the last 24 hours.

Follow Supabase incidents

Following several providers? Check your stack to get one feed for all of them.

https://down.guide/feed?provider=supabase
Open feed

In Slack, install the RSS app and run /feed subscribe https://down.guide/feed?provider=supabase in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.

https://down.guide/feed?provider=supabase&format=atom
Open feed

The same entries as Atom, for readers that prefer it.

https://down.guide/feed?provider=supabase&format=json
Open feed

The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.

History

Recent incidents

The last 90 days.

All history
  1. SupabaseDegraded
    Intermittent 502/503 errors for pg_net calls to Edge Functions
    lasted 42map-southeast-1
  2. SupabaseDegraded
    Storage issues in us-east-1 and eu-central-1
    lasted 16h 18meu, eu-central-1, us, us-east-1
  3. SupabaseDegraded
    Intermittent errors on Supavisor Shared Pooler in us-east-2
    lasted 29mus, us-east-2
  4. SupabaseDegraded
    Management API Postgres config updates overwriting previous updates
    lasted 2h 8m
  5. SupabaseDegraded
    Storage uploads failing in us-east-1
    lasted 1h 14mus, us-east-1
  6. SupabaseDegraded
    PG15 -> PG17 Upgrade Failures
    lasted 1h 8m
  7. SupabaseDegraded
    Logs degraded in multiple regions
    lasted 51m
  8. SupabaseDegraded
    Delayed Log Delivery from 14:10 - 15:30 UTC
    lasted 53m
  9. SupabaseDegraded
    Log Drain Issues
    lasted 47m
  10. SupabaseDegraded
    Elevated Mgmt API Error Rates in Multiple Regions
    lasted 3d 17h
  11. SupabasePartial outage
    Elevated Mgmt API Error Rates in Multiple Regions
    lasted 2h 13m
  12. SupabasePartial outage
    Project lifecycle operation errors in the EU region
    lasted 12h 3meu
  13. SupabaseDegraded
    Intermittent connection errors via the connection pooler in us-east-1
    lasted 0mus, us-east-1
  14. SupabasePartial outage
    Project lifecycle operations such as project creation, pausing, and restoration, in all regions
    lasted 1h 16m
  15. SupabaseDegraded
    Projects stuck in restarting state
    lasted 7h 41mus, us-east-2

Compare Supabase's reliability with MongoDB Atlas, Elastic Cloud or PostHog.

Supabase status: questions

Is Supabase down right now?

No known problems: Supabase's status page says operational (checked 2026-11-06 17:58 UTC from Supabase's official status page).

What is Supabase's uptime?

99.95% since 2026-08-11, from the incidents Supabase posted on its own status page. A major outage counts in full and a partial outage as 30% of its time, per component.

When was Supabase's last outage?

Intermittent 502/503 errors for pg_net calls to Edge Functions, starting 2026-11-05 23:12 UTC and lasting 42m: https://down.guide/supabase/DWN-fb784df3d1

How do I get alerts when Supabase goes down?

Subscribe to https://down.guide/feed?provider=supabase (RSS; add format=atom or format=json). In Slack, install the RSS app and run /feed subscribe with that URL; in Discord, give it to a feed bot such as MonitoRSS. No account needed.

Where does down.guide get Supabase's status?

From Supabase's official status page, https://status.supabase.com, read every minute. Supabase's words are quoted verbatim and linked.