PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if MongoDB Atlas is down?

PulseWatch evaluates user reports and replay-approved automated evidence for MongoDB Atlas. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported MongoDB Atlas issues today?

As of Oct 4, 2026 00:24 UTC, 0 users had reported issues with MongoDB Atlas in the previous 24 hours.

How can I report a MongoDB Atlas outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Cloud Infrastructure

Is MongoDB Atlas down right now?

UnknownOfficial status last polled Oct 4, 2026 00:20 UTCwww.mongodb.com/atlas Official status page

Managed MongoDB database service

Are you on the MongoDB Atlas team and see something inaccurate? Report it to us. We respond within one business day.

Is MongoDB Atlas down right now?

Vendor-reported issue. MongoDB Atlas: MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1 Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Oct 4, 2026 00:24 UTC

UnknownVendor-reported issue

MongoDB Atlas: vendor reports an issue

As of Oct 4, 2026 00:24 UTC

MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1 Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

Oct 1, 2026 21:40 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for MongoDB Atlas.

Incident days

No recorded incident

194h 12m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for MongoDB Atlas. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

194h 12m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

MongoDB Atlas: vendor-reported major incident on October 1 (tracked 1h 44m)

Oct 1, 07:56 PM → Oct 1, 09:40 PM · 1h 44m · high

MongoDB Atlas reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 1h 44m, from Thu, 01 Oct 2026 19:56:12 GMT to Thu, 01 Oct 2026 21:40:56 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration

1h 44m

tracked by PulseWatch

Impact

During the 1 hour and 44 minute high-severity incident, MongoDB Atlas services experienced disruption. This event was identified through automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-reported features, regions, or issue types can be detailed.

Incident timeline

Oct 1, 07:56 PM
The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it
Oct 1, 07:56 PM
Status updated: possible issue
Oct 1, 09:40 PM
PulseWatch closed the incident

Official updates

Oct 1, 07:56 PM
MongoDB Atlas reported the incident on its status page.
View official source

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: MongoDB Atlas is unknown, so there is no incident history to measure and no uptime figure is shown.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

MongoDB Atlas: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch MongoDB Atlas or have an alert rule on it can be alerted, labelled vendor-reported.

10/1/2026, 7:56:12 PM · 1h 44m

07:56 PM09:40 PM

Detection10/1/2026, 7:56:12 PM · 2d ago

Detected — high severity

ResolvedHigh

9/16/2026, 9:15:50 AM · 6d 7h

09:15 AM04:46 PM

Detection9/16/2026, 9:15:50 AM · 17d ago

Detected — high severity

ResolvedMedium