Rewindex

CompaniesMongoDB AtlasIncidents

MongoDB Atlas: MongoDB Atlas: Clusters hosted in Microsoft Azure may have experienced networking issues

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

Azure outage, Jan 25, 2023 · 14 vendors, 14 incidents

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

“…MongoDB Atlas: Clusters hosted in Microsoft Azure may have experienced networking issues Starting approximately 07:05 UTC on 25 January 2023 and running to approximately 09:45 that same day, Microsoft…”

Swipe sideways to see the whole diagram.

Azureown incident not archivedWithin an hour1 vendor, 1 blamed AzureMongoDB Atlas1 to 4 hours later3 vendors, 2 blamed AzureGrafana Cloud, Retool, InfluxData (InfluxDB Cloud)MongoDB Atlas (this incident)posted +0 min
Azureown incident not archivedWithin an hour1 vendor, 1 blamed AzureMongoDB Atlas1 to 4 hours later3 vendors, 2 blamed AzureGrafana Cloud, Retool,InfluxData (InfluxDB Cloud)MongoDB 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<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>1 vendor, 1 blamed Azure<br/>MongoDB Atlas"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>3 vendors, 2 blamed Azure<br/>Grafana Cloud, Retool, InfluxData (InfluxDB Cloud)"]:::blames
  root --> h4
  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

    Starting approximately 07:05 UTC on 25 January 2023 and running to approximately 09:45 that same day, Microsoft Azure experienced issues with networking connectivity. MongoDB Atlas clusters hosted in Azure may have seen increased network latency or timeouts. For more information, check https://status.azure.com/en-us/status/history/ (Tracking ID VSG1-B90)

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

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