MongoDB vs Supabase SLA
Promised uptime per service, credits, support and what the status pages showed, side by side.
Change vendors (up to four; 2 picked)
VendorHighest SLAWith an SLAFastest support
Promise vs reality, last year
Service99%99.9%99.99%99.999%100%
Downtime vs allowed 
Supabase Platform (Postgres, Auth, Data APIs, Storage, Pooler, Realtime, Functions, Management API, Branching, Studio, Logging)Supabase99.9% / 99.589%36 h downof 8.8 h allowed
MongoDB Atlas (database clusters)MongoDB99.995% / 99.989%60 min downof 26 min allowed
Promised in the SLAObserved on the vendor's status pagePartial historyShortfall
Best SLA by category
| Category | MongoDB | Supabase |
|---|
| Databases | 99.995%MongoDB Atlas (database clusters) | 99.9%Supabase Platform (Postgres, Auth, Data APIs, Storage, Pooler, Realtime, Functions, Management API, Branching, Studio, Logging) |
|---|
Support: fastest first response
Vendor and planFastestTargets
- MongoDB Basic (free)n/aNo published response targets.
- MongoDB Developer8 hSeverity Level 1: 8 hours · Severity Level 2: 10 hours · Severity Level 3: 12 hours · Severity Level 4: 24 hours
- MongoDB Pro2 hSeverity Level 1: 2 hours · Severity Level 2: 4 hours · Severity Level 3: 8 hours · Severity Level 4: 24 hours
- MongoDB Enterprise30 minSeverity Level 1: 30 minutes · Severity Level 2: 2 hours · Severity Level 3: 4 hours · Severity Level 4: 24 hours
- MongoDB Platinum15 minSeverity Level 1: 15 minutes · Severity Level 2: 1 hour · Severity Level 3: 4 hours · Severity Level 4: 24 hours
- Supabase Team1 d1. Urgent: 24 hours, 24/7 x 365 · 2. High: 1 business day, Mon-Fri · 3. Normal: 1 business day, Mon-Fri · 4. Low: 2 business days, Mon-Fri
- Supabase Enterprise Standard1 h1. Urgent: 1 hour, 24/7 x 365 · 2. High: 2 business hours, Mon-Fri · 3. Normal: 1 business day, Mon-Fri · 4. Low: 2 business days, Mon-Fri
- Supabase Priority Plus1 h1. Urgent: 1 hour, 24/7 x 365 · 2. High: 2 hours, 24/7 x 365 · 3. Normal: 12 hours, 24/7 x 365 · 4. Low: 24 hours, 24/7 x 365
Uptimeby Glyph