ATTOM API Outages and Service Disruptions: What to Do

Last updated: September 1, 2026

If you are experiencing errors such as 502 Bad Gateway, 504 Gateway Time-out, connection timeouts, high latency, or a complete inability to reach the ATTOM API (e.g., EAI_AGAIN DNS errors), this article explains the most common causes and what you can expect.

Common Causes of API Disruptions

ATTOM API service disruptions can occur for several reasons, including:

  • Upstream cloud provider outages – ATTOM's infrastructure runs on Microsoft Azure. When Azure experiences a global or regional outage, it can impact ATTOM API availability. These incidents are outside of ATTOM's direct control, and services are restored automatically once Microsoft's systems stabilize. You can monitor Azure's status at azure.status.microsoft.

  • Unexpected traffic surges – An unusual spike in API requests can place heavy load on backend databases, causing slowdowns or temporary outages. ATTOM's database administration team monitors for these events and works to restore normal operation promptly.

  • Internal releases or deployments – Occasionally, a newly deployed release may introduce instability. In such cases, ATTOM's team will roll back the release and work on a fix.

  • Temporary service instability – Shorter disruptions may occur and resolve on their own within minutes to hours.

What to Do During an Outage

  1. Wait and retry. Many disruptions are temporary. Try your requests again after a few minutes.

  2. Check Azure status. If the disruption appears widespread, check Azure's status page to see if there is an active cloud incident affecting services.

  3. Contact ATTOM Support. If the issue persists, reach out to the ATTOM support team at datacustomercare@attomdata.com. When contacting support, please include:

    • The full API endpoint URL(s) you are calling

    • The last 4 digits of your API key

    • The exact error message or HTTP status code you are receiving

    • Approximate timestamps of when the issue started

    • Any request IDs (e.g., x-azure-ref headers) if available

What to Expect from ATTOM During an Outage

When a service disruption is confirmed, ATTOM's team will:

  • Investigate the root cause and engage the appropriate engineering teams.

  • Provide updates as more information becomes available.

  • Notify you once services have been restored.

If the disruption is caused by an upstream provider such as Microsoft Azure, ATTOM will monitor the provider's progress and services will come back online automatically once the upstream issue is resolved.

After the Outage Is Resolved

Once ATTOM confirms that services have been restored, please retry your API calls. If you continue to experience elevated latency or errors after the outage is declared resolved, contact support at datacustomercare@attomdata.com with specific details (endpoints, timestamps, and request IDs) so the team can investigate further.