Is Datadog down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, app.datadoghq.com is responding normally to HostTracker's monitoring network, and has been up for 21d 7h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

It can be an intake delay rather than a full outage. Datadog occasionally experiences delays in processing incoming telemetry, which makes dashboards look sparse or empty because the data simply hasn't arrived and been rendered yet, not because monitoring has stopped working entirely. This is a distinct pattern from the platform being unreachable outright, and it typically clears once the backlog processes, though checking the specific regional site's status is worth doing if it persists.

Datadog operates several genuinely separate regional sites rather than one shared global platform, so a status check or incident report for one site tells you nothing about another. An account hosted on EU1 can be fully degraded while US1 runs perfectly normally, and vice versa - the sites don't share the underlying infrastructure that would make one incident affect both. Confirming which site an account actually lives on is the first step before concluding anything about the platform as a whole.

This is a real limitation worth planning around: a team that relies entirely on Datadog to know when something is wrong has no signal at all when Datadog itself is the thing that's degraded, since the dashboards that would normally show a problem are exactly what's failing quietly in the background. An independent check of Datadog's own reachability, run from outside its infrastructure entirely, is the only way to get a signal in that specific scenario - checking the tool that watches everything else needs a watcher of its own.

It can be a monitor evaluation delay, which is a narrower issue than data not arriving at all. Datadog's monitors evaluate incoming data on their own schedule, and a backlog in that evaluation step pushes back when an alert condition is actually detected and fired, even though the raw data itself arrived on time. The gap between an issue starting and an alert firing is the symptom to watch for here, distinct from missing data entirely.