# Trigger processing may be delayed globally

- Provider: [MongoDB Atlas](https://down.guide/mongodb-atlas)
- Level: confirmed
- Impact: Partial outage
- lasted 5h 13m
- started 2026-10-01 15:41 UTC
- MongoDB Atlas App Services and Device Sync
- id: DWN-72d5f78a41
- Official page: https://stspg.io/bdghxhyf3hbd

## Updates from MongoDB Atlas
### 2026-10-01 15:41 UTC: investigating
As of approximately 15:00 UTC, some users of MongoDB Atlas Triggers may experience delayed unordered trigger processing. We are investigating and working to restore normal processing.

### 2026-10-01 18:21 UTC: investigating
We are continuing to investigate this issue.

### 2026-10-01 19:51 UTC: investigating
Some users may find that their Atlas Triggers are not firing or are not visible in the Atlas UI. We are investigating both symptoms and working to restore trigger processing. We will provide another update as we learn more.

### 2026-10-01 19:59 UTC: monitoring
Atlas Triggers are firing again, and trigger processing is operational. We are monitoring the service and verifying the status of triggers affected during the incident, including any delayed events. We will provide a further update once verification is complete.

### 2026-10-01 20:54 UTC: resolved
This incident has been resolved.

From the builder: does your app depend on MongoDB Atlas? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=mongodb-atlas) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention MongoDB Atlas.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-72d5f78a41), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.