E2M (Events-2-Metrics) authorization issues

What to do

• Check whether you use New Relic APM : US, APM : Europe, Alerts : US, Alerts : Europe and 2 more 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 0m it lasted.

  Anything that failed between 2026-07-17 10:21 UTC and 2026-07-17 10:21 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 1

1. resolvedJul 17, 2026, 10:21 AM UTC

   Between 15:00 UTC on July 14th and 10:00 UTC on July 17th, we experienced an issue where some customers experienced authorization issues when attempting to create, read or update E2M (Events-2-Metrics) rules in the US, EU and JP regions. This was due to a recent change we have made to our authorization endpoints. These endpoints now require S2S authentication which has caused requests to our E2M (Events-2-Metrics) to fail. Our teams have rolled back these changes until a permanent fix can be put in place. The issue is now resolved, and the impacted services have returned to normal service.

   provider

Corrections

None so far.

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