MongoDB Cloud: Trigger processing may be delayed in AWS ap-southeast-2

MongoDB Cloud · mongodb.comImpact: minorinvestigating2026-10-01 15:41 UTC

Public — what happened

Summary

As of approximately 15:00 UTC, some users of MongoDB Atlas Triggers in AWS ap-southeast-2 may experience delayed unordered trigger processing. We are investigating and working to restore normal processing.

Timeline

Started — 2026-10-01 15:41 UTC
Last update — 2026-10-01 15:41 UTC
Ongoing at last check.

Source of record: provider status page. Mirrored as reported; times in UTC.

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 see

Customers 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 →

Related: MongoDB Cloud status & history. SquidGrid is not affiliated with MongoDB Cloud.