Rewindex

CompaniesMongoDB AtlasIncidents

MongoDB Atlas: Microsoft Azure Incident: Degraded performance for Atlas Device Sync

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.mongodb.com (opens in new tab)
Part of an outage event

Azure central us outage, Jul 18, 2024 · 9 vendors, 9 incidents

MongoDB Atlas’s incident blames Azure as the cause. (hop 1, posted +0 min vs the first vendor naming Azure)

“…Microsoft Azure Incident: Degraded performance for Atlas Device Sync An Azure outage impacted Sync users, causing very delayed syncing during the outage and the system auto-recovered once the outage w…”

Swipe sideways to see the whole diagram.

Azure central usown incident not archivedWithin an hour5 vendors, 1 blamed AzureMongoDB Atlas, Confluent, GitHub, GitHub Copilot +1Later1 vendorContentstackMongoDB Atlas (this incident)posted +0 min
Azure central usown incident not archivedWithin an hour5 vendors, 1 blamed AzureMongoDB Atlas, Confluent,GitHub, GitHub Copilot +1Later1 vendorContentstackMongoDB Atlas (this incident)posted +0 min
MongoDB Atlas is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Azure central us<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 1 blamed Azure<br/>MongoDB Atlas, Confluent, GitHub, GitHub Copilot +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor<br/>Contentstack"]:::names
  root --> later
  me["MongoDB Atlas (this incident)<br/>posted +0 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    An Azure outage impacted Sync users, causing very delayed syncing during the outage and the system auto-recovered once the outage was resolved. Updates from Azure can be tracked at https://azure.status.microsoft/en-us/status and in the Service Health Dashboard in your Microsoft Azure Portal.

From MongoDB Atlas’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.mongodb.com (opens in new tab).

MongoDB Atlas profileRecent MongoDB Atlas incidentsMarkdownJSON