CompaniesMongoDB AtlasIncidents
MongoDB Atlas: Atlas Serverless Outage in AWS Singapore (ap-southeast-1)
Timeline of updates
- resolved
Starting at 2025-01-15T01:02:00 UTC some Atlas Serverless instances in AWS Singapore region (ap-southeast-1) experienced downtime. The issue was due to unexpected memory exhaustion of the system that caused outage for a subset of the Atlas infrastructure in that region. A small number of serverless instances running on those infrastructure would have experienced downtime. Our engineers were alerted and the system was restored to health around 2025-01-15T01:44:00 UTC.
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).
Cite this
Status incident (vendor impact label: minor) posted by MongoDB Atlas, started 2025-01-15 01:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Atlas Serverless Outage in AWS Singapore (ap-southeast-1)
- Vendor
- MongoDB Atlas
- Date
- URL
- https://rewindex.com/company/mongodb-atlas/incidents/mtd4st60s35b
MongoDB Atlas profileRecent MongoDB Atlas incidentsAll outages on January 15, 2025MongoDB Atlas in January 2025MarkdownJSON