Is MongoDB down?

Last checked 6m ago
Current status
MongoDB is having a partial outage

Active incident: Impaired Cluster Operations – AWS me-central-1 (United Arab…

Get alerts when MongoDB breaks →

Free · no credit card

Official status page: http://status.cloud.mongodb.com · Polled every 5 minutes · 9 components tracked

Real-time MongoDB status, recent outages, and incident history — pulled directly from MongoDB's official status page at http://status.cloud.mongodb.com every 5 minutes. Pingoru tracks 9 MongoDB services and has captured 23 incidents in the last 90 days (94.07% uptime). Get email, Slack, Discord, or webhook alerts the moment MongoDB reports a new incident — free for 5 monitors, no credit card.

Users who monitor MongoDB also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
MongoDB uptime 94.07% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Increase in Billing for Backup Usage
    Resolved 3h 33m
    Started Apr 27, 2026, 05:16 PM UTC · Resolved Apr 27, 2026, 08:50 PM UTC
    MongoDB Cloud
    2 updates · show timeline
    • identified · Apr 27, 2026, 05:16 PM UTC

      We have identified a bug affecting some Atlas customers that resulted in higher-than-expected backup charges on invoices for the billing date of April 24, 2026. This is a billing-only issue; your backup configuration, cluster health, and data are unaffected. We are actively working to correct all affected invoices. Any overcharges will be automatically refunded — no action is required on your end. Please contact MongoDB Support with any questions. We will post another update by April 24 at 22:00 UTC.

    • resolved · Apr 27, 2026, 08:50 PM UTC

      We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us.

    Latest: We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us…

See the full MongoDB outage history

22 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 5 incidents
  • Increase in Billing for Backup Usage Resolved
    Started Apr 27, 2026, 05:16 PM UTC · Resolved Apr 27, 2026, 08:50 PM UTC · 3h 33m
  • MongoDB Atlas BI Connector: Connections and queries fail Resolved
    Started Apr 17, 2026, 05:03 PM UTC · Resolved Apr 21, 2026, 01:45 PM UTC · 3d 20h
  • Atlas Charts users unable to login Resolved
    Started Apr 01, 2026, 12:55 PM UTC · Resolved Apr 01, 2026, 12:55 PM UTC · —
  • Delays in cluster creation and adding new cluster nodes in Azure East US 2 region Resolved
    Started Mar 30, 2026, 09:47 PM UTC · Resolved Mar 30, 2026, 11:10 PM UTC · 1h 22m
  • MongoDB Atlas for Government: SSO login failures for some users Resolved
    Started Mar 19, 2026, 12:24 AM UTC · Resolved Mar 31, 2026, 09:19 PM UTC · 12d 20h

See MongoDB in your Pingoru dashboard

Monitor MongoDB alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add MongoDB to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every MongoDB incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just MongoDB or see every provider at once.

Maintenance calendar

Scheduled MongoDB maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every MongoDB status change, one inbox

Pingoru watches MongoDB's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

MongoDB reports on 9 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route MongoDB alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming MongoDB maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy MongoDB services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching MongoDB from the same account, with per-user notification preferences for any monitor.

Get notified on MongoDB status changes

Pingoru watches MongoDB's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring MongoDB free

Monitor MongoDB along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add MongoDB and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track MongoDB uptime & incident history

See 90 days of MongoDB uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See MongoDB uptime history

Frequently asked questions

What is MongoDB's uptime?
Over the last 90 days, MongoDB reported 94.07% uptime on its official status page. That figure is calculated from the public incident timeline at http://status.cloud.mongodb.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see MongoDB's uptime history rolling forward in real time.
Has MongoDB had outages in 2026?
Yes — MongoDB has had 22 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last MongoDB outage?
The most recent MongoDB incident was "Increase in Billing for Backup Usage", which started on April 27, 2026 and was resolved on April 27, 2026. Pingoru captured this directly from http://status.cloud.mongodb.com. See the full incident card above for affected components and the update timeline.
How often does MongoDB have outages?
Based on the last 90 days, MongoDB averages 7.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is MongoDB's status page?
MongoDB's official status page is http://status.cloud.mongodb.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is MongoDB down right now?
MongoDB is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment MongoDB reports a change. Current status is based on 9 tracked services.
How does Pingoru know if MongoDB is down?
We read http://status.cloud.mongodb.com directly, using MongoDB's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when MongoDB has an outage?
Create a free Pingoru account and add MongoDB as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
MongoDB's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real MongoDB incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real MongoDB issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official MongoDB status?
We use MongoDB's own status page at http://status.cloud.mongodb.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Partial Outage" mean?
MongoDB has a partial outage — one or more components are down, but the rest of the service is operational.

Stop finding out from your users.

We watch MongoDB's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor MongoDB free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →