Skip to content

Incident detail

Issue connecting to Atlas Data Federation and Online Archive

Resolved incidentMajor3 affected services

Timeline window

to

Get alerted the next time MongoDB Atlas breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are investigating report of issues connecting and authenticating to Atlas Data Federation and Online Archive instances.

  2. Investigating

    We are continuing to investigate this issue.

  3. Identified

    We have identified an issue causing the following symptoms:

    • Atlas Data Explorer connections and queries failing
    • Atlas Data Federation and Online Archive queries failing
    • Atlas Stream Processing being interrupted
    • MongoDB Charts data being delayed

    Affected users will see the above symptoms, often with timeout or host not found errors.

    Underlying cluster health is unaffected, including Atlas search queries.

  4. Identified

    We have identified an issue causing the following symptoms:

    • Atlas Data Explorer connections and queries failing
    • Atlas Data Federation and Online Archive queries failing, as well as the creation of new Data Federation or Online Archive instances
    • Atlas Stream Processing being interrupted
    • MongoDB Charts data being delayed

    Affected users will see the above symptoms, often with timeout or host not found errors.

    Underlying cluster health is unaffected, including Atlas search queries.

    Additionally, Vercel users may not be able to get directly to Atlas from within Vercel. As a workaround, users are encouraged to login directly to Atlas at cloud.mongodb.com

  5. Monitoring

    A fix has been implemented and we are monitoring the results.

  6. Resolved

    Issue is resolved, and affected components are confirmed to be operational again.

Keep exploring

More from MongoDB Atlas

Neighboring incidents on MongoDB Atlas's timeline and the rest of their record on OutageDeck.