Skip to main content
New Relic

Distributed Tracing Errors for US and EU Regions

Degraded Lasted 1h 2m · started · New Relic's page

Level
confirmed
Worst impact
Degraded
Regions
eu, us

What to do

  • Check whether you use New Relic in eu, us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 2m it lasted.

    Anything that failed between 2026-02-05 16:20 UTC and 2026-02-05 17:22 UTC may need a replay.
  • Subscribe to New Relic's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=new-relic works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from New Relic 3

  1. investigating

    We are currently investigating an issue causing errors with Distributed Tracing

    provider

  2. monitoring

    Our Team has now issued a fix and are monitoring the issue.

    provider

  3. resolved

    Between 15:15 UTC and 16:30 UTC some customers may have experienced an issue with Distributed Tracing.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-5e9431f28f

Is New Relic still down?

No, this incident was resolved 2026-02-05 17:22 UTC. For New Relic's live state, see https://down.guide/new-relic.

How long did it last?

1h 2m, from 2026-02-05 16:20 UTC to 2026-02-05 17:22 UTC, by the times New Relic posted.

What was affected?

New Relic named in eu, us.

What caused it?

New Relic hasn't published a root cause. If it does, it shows here.

Where does this come from?

New Relic's official status page, https://status.newrelic.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.