MongoDB Atlas Status · History · Incident #143579

RESOLVED

Trigger processing may be delayed globally

Major · Started Oct 1, 2026 · 3:41 PM

  • Duration

    5h 12m

  • Severity

    Major

  • Detection lead

    —

  • User reports

    —

Summary

Trigger processing may be delayed globally

This incident has been resolved.


  • Started

    Oct 1, 2026 · 3:41 PM

  • Resolved

    Oct 1, 2026 · 8:54 PM

  • Duration

    5h 12m

  • Severity

    Major

Event timeline

How this incident unfolded

  • ◐

    Investigating

    Oct 1 · 3:41 PM MongoDB Atlas

    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.

  • ◐

    Investigating

    Oct 1 · 6:21 PM MongoDB Atlas

    We are continuing to investigate this issue.

  • ◐

    Investigating

    Oct 1 · 7:51 PM MongoDB Atlas

    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.

  • ◉

    Monitoring

    Oct 1 · 7:59 PM MongoDB Atlas

    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.

  • ✓

    Resolved

    Oct 1 · 8:54 PM MongoDB Atlas

    This incident has been resolved.

Get an email when MongoDB Atlas opens, updates or resolves an incident.

Add it as a dependency monitor. The Free plan includes one.