← Live dashboard

Atlas UI and API Periodic Unavailability

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Aug 18, 2026, 02:10 PM · Resolved Aug 18, 2026, 03:17 PM

This incident has been resolved. Following the incident, we identified an issue that caused some internal Atlas jobs not to start as scheduled, resulting in delays to certain changes. The issue was related to this incident "Atlas UI and API Periodic Unavailability" which has been remediated. Customer clusters and their data were not affected; the impact was limited to the timing of control-plane operations. This jobs issue has been resolved as well.

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with MongoDB Atlas now? Check the current status

Affected services

MongoDB Cloud

Updates (4)

  1. Aug 18, 2026, 03:17 PM
    Atlas UI and API Periodic Unavailability

    This incident has been resolved. Following the incident, we identified an issue that caused some internal Atlas jobs not to start as scheduled, resulting in delays to certain changes. The issue was related to this incident "Atlas UI and API Periodic Unavailability" which has been remediated. Customer clusters and their data were not affected; the impact was limited to the timing of control-plane operations. This jobs issue has been resolved as well.

    MongoDB Atlas ↗
  2. Aug 18, 2026, 03:04 PM
    Atlas UI and API Periodic Unavailability

    We have disabled the workload and are monitoring the situation

    MongoDB Atlas ↗
  3. Aug 18, 2026, 02:57 PM
    Atlas UI and API Periodic Unavailability

    We have identified a new workload that was putting more load than expected on the backing system. We are working on disabling it. Customer clusters remain unaffected.

    MongoDB Atlas ↗
  4. Aug 18, 2026, 02:10 PM
    Atlas UI and API Periodic Unavailability

    We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.

    MongoDB Atlas ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow MongoDB Atlas's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.