rewindex

CompaniesNew RelicIncidents

New Relic: E2M (Events-2-Metrics) authorization issues

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestspg.io (opens in new tab)

Affected components: Alerts : JPUI : JP - Alerts : JPAlert Notifications : Europe - APM : EuropeAPM : EuropeAlert Notifications : JP - APM : JPAPM : JPAlerts : USUI : US - Alerts : USAlert Notifications : US - APM : USAPM : USAlerts : EuropeUI : Europe - Alerts : Europe

Timeline of updates

  1. resolved

    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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by New Relic, started 2026-07-17 10:21 UTC, resolved after 0 min, 1 update(s).

Title
E2M (Events-2-Metrics) authorization issues
Vendor
New Relic
Date
URL
https://rewindex.com/company/new-relic/incidents/c1zg3xk8wcc6

New Relic profileRecent New Relic incidentsAll outages on July 17, 2026New Relic in July 2026MarkdownJSON