Is MongoDB Atlas down or is it my connection?

To distinguish Atlas downtime from a local connection issue: (1) Check status.mongodb.com for your region, (2) Try connecting from a different network or using the Atlas Data Explorer in the UI, (3) Run 'mongosh your-connection-string --eval db.adminCommand({ping: 1})' — a timeout suggests a network/firewall issue, while a connection error suggesting the host is down may indicate Atlas issues. (4) Search 'MongoDB Atlas down' on X for real-time reports.

Does MongoDB Atlas downtime affect self-hosted MongoDB?

No. Self-hosted MongoDB (running on your own servers or VMs) is completely independent of MongoDB Atlas. Atlas incidents only affect Atlas-hosted clusters. If you run MongoDB on your own infrastructure, your availability depends on your own setup, not MongoDB's cloud status.

What does MongoDB Atlas status "degraded" mean?

Degraded Atlas status means the service is available but experiencing performance issues — slower query execution, higher latency, or occasional connection drops. Your application can still read and write data, but operations may take longer than usual. Monitor your application's error rates and timeouts during degraded status periods.

MongoDB / Cloud Database

MongoDB Status: How to Check If MongoDB Atlas Is Down (2026)

Q: Where is the official MongoDB Atlas status page?

MongoDB Atlas's official status page is at status.mongodb.com. It shows real-time status for Atlas clusters, the Atlas API, Atlas Search, Data Federation, App Services (Realm), and the Atlas UI — broken down by region (AWS, GCP, Azure). For independent monitoring, use apistatuscheck.com.

Q: How do I get alerts when MongoDB Atlas goes down?

Subscribe to alerts at status.mongodb.com (email/SMS/webhook), set up Atlas Alerts in your Atlas project settings, or use a third-party monitoring tool like Better Stack or API Status Check. Atlas also supports PagerDuty integration for incident escalations.

Updated June 2026 · 8 min read · API Status Check

Quick Answer

Check MongoDB Atlas status at status.mongodb.com (official). Atlas status is region-specific — expand your cloud provider (AWS/GCP/Azure) and region to see your cluster's actual status.

Staff Pick

📡 Monitor your APIs — know when they go down before your users do

Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.

Start Free →

Affiliate link — we may earn a commission at no extra cost to you

The Official MongoDB Status Page

MongoDB maintains its official status page at status.mongodb.com. The page covers all MongoDB cloud services, organized by region and cloud provider:

Atlas Clusters (AWS / GCP / Azure): The managed MongoDB clusters hosting your databases — the core service most apps depend on

Atlas API: REST APIs for cluster management, user administration, and automation (used by Terraform providers and CI/CD pipelines)

Atlas UI / Atlas Administration Console: The web dashboard for managing clusters, collections, indexes, and users

Atlas Search: Full-text search powered by Apache Lucene — Atlas Search outages don't always coincide with cluster outages

Atlas Data Federation: Query data across S3, Atlas clusters, and other sources via federated queries

App Services (formerly Realm): Serverless functions, triggers, GraphQL API, and device sync for Atlas

Atlas Charts: Data visualization and dashboards built on Atlas data

Critical: Atlas Status Is Region-Specific

MongoDB Atlas runs across AWS, Google Cloud, and Azure in dozens of regions. An outage in AWS us-east-1 doesn't affect Azure eu-west-2. On status.mongodb.com, always expand the specific cloud provider and region where your cluster runs to see accurate status for your workload.

What Each MongoDB Atlas Status Means

Operational: All Atlas services in this region working normally. If your app still can't connect, the issue is likely in your connection string, network/firewall rules (IP access list), or application-side connection pooling.

Degraded Performance: Atlas is running but slower than normal. Queries may take longer, write operations may be queued, and connection setup may be delayed. Your application should handle this gracefully with appropriate timeouts and retry logic.

Partial Outage: A subset of Atlas services or a specific region is impacted. Check whether it's cluster data operations, the API, or the UI that's affected. Often only one component fails while others remain operational.

Major Outage: Core Atlas database service is unavailable. Applications cannot read or write data. Atlas has automatic failover for replica sets, so cluster-level outages typically trigger failover to a secondary node within 30-60 seconds.

Under Maintenance: Planned maintenance window. Atlas notifies cluster owners in advance for major maintenance. Minor maintenance (like software patches) happens automatically with minimal impact to replica set clusters.

📡

Recommended

Monitor your MongoDB Atlas cluster uptime

Better Stack monitors your Atlas cluster's availability every 30 seconds and alerts your engineering team before users see database errors. Free tier included.

Try Better Stack Free →

MongoDB Atlas vs. Self-Hosted MongoDB: Key Differences

The cause of your MongoDB issue depends critically on whether you're using Atlas (managed cloud) or self-hosted:

MongoDB Atlas (Managed Cloud)

What it is: MongoDB's fully-managed cloud database. Your app connects via a connection string to Atlas-hosted clusters. MongoDB manages all infrastructure, replication, and backups.

Signs of issues: Connection timeouts, MongoNetworkError, MongoServerSelectionError with timeout, writes failing with WriteConcernError.

Workaround: Check status.mongodb.com for your region. Atlas clusters automatically failover to secondaries — brief connection disruption (30-60s) is expected during failover. Implement retry logic in your application.

Self-Hosted MongoDB (On-Premises / Cloud VMs)

What it is: MongoDB running on your own servers, VMs, or Kubernetes. You manage the infrastructure. Not affected by Atlas outages.

Signs of issues: mongod process crashed, disk full, replica set election in progress, network partition between nodes.

Workaround: Check mongod process status, disk space, replica set status with rs.status(), and system logs. Not an Atlas issue — check your own infrastructure.

MongoDB Realm / App Services

What it is: Serverless backend built on Atlas — functions, triggers, GraphQL, device sync. Depends on Atlas cluster availability plus its own service layer.

Signs of issues: Functions not triggering, sync not working, GraphQL errors. Check App Services status separately from cluster status on status.mongodb.com.

Workaround: App Services can fail independently of your Atlas cluster. Check the App Services section specifically on status.mongodb.com.

5 Ways to Check MongoDB Atlas Status Right Now

Official MongoDB Status Page

Visit status.mongodb.com and expand your cloud provider/region to see cluster-specific status. Subscribe to notifications.

status.mongodb.com →

Test Your Atlas Cluster Directly

Run a ping command against your Atlas cluster. A timeout indicates network/firewall issues; a server error indicates Atlas-side problems.

mongosh 'mongodb+srv://cluster0.xxxxx.mongodb.net/' --eval 'db.adminCommand({ping: 1})'

Atlas UI Health Check

Try accessing your Atlas cluster's Data Explorer in the Atlas UI (cloud.mongodb.com). If data loads in the UI but your app can't connect, it's a network/connection string issue, not Atlas.

Atlas Cloud UI →

X/Twitter Search

Search 'MongoDB Atlas down' or 'MongoDB down' on X. Developers report database connection issues in real time.

Search X for 'MongoDB Atlas down' →

Atlas Alerts in Your Project

Configure Atlas Alerts in your Atlas project settings to receive automatic notifications when cluster metrics (connections, latency, replica set elections) hit thresholds.

Atlas Alerts documentation →

Common MongoDB Atlas Errors During Outages

These are the errors developers see when Atlas is experiencing issues:

MongoNetworkError: connection timed outCan't reach your Atlas cluster. Could be Atlas-side or your IP not on the access list. Check status.mongodb.com and verify your IP access list in Atlas → Network Access.

MongoServerSelectionError: Timed out after 30000msThe driver can't select a primary server. During Atlas incidents, this appears when replica set elections are in progress. Usually resolves in 30-60s as Atlas completes failover.

MongoServerError: not primaryYour connection hit a secondary node that can't accept writes. This happens during primary election events — implement retryWrites:true in your connection string to handle this automatically.

Atlas cluster shows "Idle" but queries failThe cluster may be in a degraded state not yet reflected on status.mongodb.com. Check your Atlas cluster metrics (CPU, disk I/O, connections) in the Atlas UI for anomalies.

WriteConcernError: waiting for replication timed outReplication between Atlas nodes is lagging. Indicates network issues between replica set members or high write load. May occur during degraded Atlas network conditions.

Atlas UI shows "Cluster under maintenance"MongoDB is performing automated maintenance on your cluster. Replica set clusters typically maintain availability during maintenance via rolling restarts. M0 (free tier) clusters may have brief outages.

MongoDB Atlas Reliability & SLA

99.995%

Uptime SLA

For dedicated M10+ clusters with replica sets — roughly 26 minutes of downtime per year

30-60s

Automatic failover

Atlas automatically elects a new primary when the current primary is unavailable

Free (M0)

No SLA on free tier

M0 free clusters have no uptime guarantee and may have higher incident rates

Atlas M0 (free tier) clusters are the most vulnerable to downtime — they share infrastructure and have no SLA. For production workloads, use M10 or higher. Atlas replica set clusters (3 nodes) provide automatic failover and are the standard for production availability. Also see: Neon status guide and Supabase status guide for alternative managed database options.

📡

Recommended

Monitor your MongoDB Atlas cluster 24/7

Better Stack independently monitors your Atlas connection endpoints every 30 seconds and pages your on-call engineer when the database goes down. Free tier included.

Try Better Stack Free →

What to Do When MongoDB Atlas Is Down

Immediate Steps

Check status.mongodb.com — expand your cloud provider and region
Verify your IP access list in Atlas → Network Access (a common false alarm)
Check if retryWrites and retryReads are enabled in your connection string
Notify your engineering team — database outages cascade to all dependent services
Enable read-only fallback from a replica or secondary if you have read scaling configured

Long-Term Resilience

Use M10+ clusters with replica sets for automatic failover (avoid M0 in production)
Enable retryWrites=true&retryReads=true in all connection strings
Configure Atlas Alerts for cluster health, connections, and replication lag
Use multi-region clusters for critical applications requiring geo-redundancy
Implement a read-through cache (Redis) for high-traffic reads to survive brief database degradation

Frequently Asked Questions

Where is the official MongoDB Atlas status page?

MongoDB's official status page is at status.mongodb.com. It shows real-time status for Atlas clusters, the Atlas API, Atlas Search, App Services, and the Atlas UI — organized by cloud provider (AWS, GCP, Azure) and region. Always expand your specific cloud provider/region to see status relevant to your cluster.

Why does my app show connection errors but MongoDB status shows operational?

Common causes: (1) Your IP isn't on the Atlas IP access list — check Atlas → Network Access. (2) You're hitting connection limits on your cluster tier. (3) The outage just started and the status page hasn't been updated yet. (4) Your connection string has wrong credentials or parameters. Try connecting via Atlas Data Explorer to isolate app-side vs Atlas-side issues.

How does MongoDB Atlas handle downtime automatically?

Atlas replica set clusters (M10+) automatically failover when the primary node becomes unavailable. The driver detects the primary is gone and the replica set elects a new primary, typically within 30-60 seconds. During this window, write operations will fail. With retryWrites=true, the MongoDB driver will automatically retry eligible write operations after failover.

Does MongoDB Atlas have an SLA for free tier clusters?

No. M0 (free tier) clusters have no uptime SLA and run on shared infrastructure. For any production workload, upgrade to M10 or higher, which provides the 99.995% uptime SLA, dedicated resources, and automatic failover. M0 is for development and testing only.

How do I get alerts when MongoDB Atlas goes down?

Subscribe to status updates at status.mongodb.com, configure Atlas Alerts in your project settings for cluster health metrics, and use third-party monitoring (Better Stack, API Status Check) for independent endpoint monitoring. Atlas also integrates with PagerDuty, Slack, and Microsoft Teams for incident notifications.

Alert Pro

14-day free trial

Stop checking — get alerted instantly

Next time MongoDB Atlas goes down, you'll know in under 60 seconds — not when your users start complaining.

Email alerts for MongoDB Atlas + 9 more APIs
$0 due today for trial
Cancel anytime — $9/mo after trial

Start Free Trial →Compare all plans →

Also recommended:

Better Stack — all-in-one monitoring 1Password — secure your API keys