Live / MongoDB Cloud / Incident
MongoDB Cloud: Trigger processing may be delayed globally
MongoDB Cloud · mongodb.comMajor incidentResolved2026-10-01 20:54 UTC
Public — what happened
Summary
MongoDB Cloud reported a major incident in which some users of its Atlas Triggers feature saw delays in the processing of unordered triggers, a problem the company said began around 15:00 UTC on October 1, 2026. Later updates added that some triggers were not running at all or could not be seen in the Atlas interface. By 19:59 UTC the company said triggers were firing again and it was checking the ones affected, including delayed events, and the incident was marked resolved at 20:54. MongoDB Cloud did not name a cause in its updates.
Timeline
- Started — 2026-10-01 15:41 UTC
- Investigating — 2026-10-01 15:41 UTC (3 updates)
- Monitoring — 2026-10-01 19:59 UTC
- Resolved — 2026-10-01 20:54 UTC · 5h 13m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach MongoDB Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for MongoDB Cloud: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the MongoDB Cloud report →
More from MongoDB Cloud
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.