Skip to main content
Vendor reliability

Vendor record

Datadog

Vendor reports Operational

Checked

Front door check counts and Datadog’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Datadog endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.datadoghq.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Datadog product, region or your app worked.

How we count front door checks

Datadog says

Incident posts from Datadog’s status page, with its titles, impact levels and times. They say what Datadog chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

31

incidents Datadog posted, last 180 days

Median recorded duration: 1h 9m. From 31 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Delayed RUM sessions

    Not specified

    Started, per Datadog

    Closed in our record(2h 28m)

    Datadog’s post
  • Delayed Events

    Minor

    Started, per Datadog

    Closed in our record(57m)

    Datadog’s post
  • Users are unable to acknowledge, escalate, or resolve On-Call Pages

    Minor

    Started, per Datadog

    Closed in our record(28m)

    Datadog’s post
  • Delayed Monitors Notifications

    Minor

    Started, per Datadog

    Closed in our record(55m)

    Datadog’s post
  • Delayed events triggered by emails

    Minor

    Started, per Datadog

    Closed in our record(1h 37m)

    Datadog’s post
15 older records
  • Delayed CICD Optimization, Code Coverage, Code Security, and DORA data

    Minor

    Started, per Datadog

    Closed in our record(5h 49m)

    Datadog’s post
  • Delayed DBM Monitor Evaluation

    Minor

    Started, per Datadog

    Closed in our record(27m)

    Datadog’s post
  • Delayed Processes data

    Minor

    Started, per Datadog

    Closed in our record(48m)

    Datadog’s post
  • Delayed Evaluation of Service Check monitors

    Minor

    Started, per Datadog

    Closed in our record(46m)

    Datadog’s post
  • Real user monitoring, distribution and custom processes metrics delayed

    Minor

    Started, per Datadog

    Closed in our record(1h 53m)

    Datadog’s post
  • Synthetics Test Runs Delayed

    Major

    Started, per Datadog

    Closed in our record(49m)

    Datadog’s post
  • Latency with Pages and Monitor state changes

    Minor

    Started, per Datadog

    Closed in our record(1h 11m)

    Datadog’s post
  • Delayed data streams data

    Major

    Started, per Datadog

    Closed in our record(1h 51m)

    Datadog’s post
  • Errors Pulling Container Images

    Critical

    Started, per Datadog

    Closed in our record(1h 9m)

    Datadog’s post
  • Elevated Error Rates

    Not specified

    Started, per Datadog

    Closed in our record(2h 8m)

    Datadog’s post
  • Delayed data processing and errors in multiple products

    Major

    Started, per Datadog

    Closed in our record(2h 53m)

    Datadog’s post
  • Delayed Monitors Notifications

    Major

    Started, per Datadog

    Closed in our record(45m)

    Datadog’s post
  • Delayed APM Trace Metrics

    Not specified

    Started, per Datadog

    Closed in our record(6m)

    Datadog’s post
  • Delayed CI Visibility data

    Minor

    Started, per Datadog

    Closed in our record(17m)

    Datadog’s post
  • Metrics Queries

    Major

    Started, per Datadog

    Closed in our record(1h 17m)

    Datadog’s post

Your code, your dependencies

See which of your code paths call Datadog

Connect GitHub or GitLab to find where your public or private repository uses Datadog. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Datadog status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · DatadogStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/datadog?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Datadog status badge"></iframe>

Frequently Asked Questions

Is Datadog currently down?

Datadog's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Datadog last have an outage?

The most recent closed incident record began 14 days ago and spans 2h 28m. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Datadog?

No. CheckUpstream checks Datadog’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Datadog in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Datadog?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.