Datadog service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Live Domain Check
Run a live reachability check for datadoghq.com. Compare the regional responses with the problem you see in Datadog.
Find Datadog help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Datadog has site-specific monitoring services; a datadoghq.com marketing response does not verify your selected Datadog site or incoming telemetry.
The checker above requests datadoghq.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Datadog action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
The linked default dashboard is labelled US1; choose the status information for your Datadog site.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
The linked default dashboard is labelled US1; choose the status information for your Datadog site.
Open Datadog help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Datadog site, affected product, agent/version, time range and intake/request error without API keys.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Datadog.
These are troubleshooting comparisons, not claims that Datadog is currently experiencing a particular incident.
Check the site/region in your dashboard URL and compare the corresponding status page.
For missing metrics or logs, inspect one agent/intake response and distinguish ingestion delay from a dashboard query failure.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Datadog seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open datadoghq.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Datadog issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Datadog support.
Run the datadoghq.com check and compare its original timestamps and responses with your actual error. Datadog has site-specific monitoring services; a datadoghq.com marketing response does not verify your selected Datadog site or incoming telemetry.
Use the official help/reporting resource linked above. The linked default dashboard is labelled US1; choose the status information for your Datadog site.
Check the site/region in your dashboard URL and compare the corresponding status page. For missing metrics or logs, inspect one agent/intake response and distinguish ingestion delay from a dashboard query failure.
Datadog site, affected product, agent/version, time range and intake/request error without API keys.