Skip to content

Outage tracker

New Relic: the full evidence record

The last 24 hours in detail, 46 days of measured availability, a 12-month summary, our own incident log, New Relic's declared record, and how the two compare.

← Back to New Relic's live status

We started measuring New Relic on August 22, 2026, which is 46 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me the next time we see New Relic go down

Measured by our own probes from ten regions, not New Relic's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what New Relic's own status page declared. Below it, any public chatter we saw about New Relic and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what New Relic's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about New Relic in the last 24 hours, which is not evidence that nothing is wrong.
New Relic's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is New Relic's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention New Relic next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%6273
US-West99.98%6267
Europe100.00%6195
Asia-Pacific99.98%5954
US-Central100.00%2391
Canada100.00%2392
UK100.00%2391
Southeast Asia100.00%2359
Australia100.00%2355
South America100.00%2382

Monthly summary

Tracking New Relic since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min
Oct 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for New Relic: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and New Relic's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for New Relic in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: New Relic's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for New Relic since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

New Relic's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Data Irregularities for US regionPartial outage
Sep 25, 2026, 7:57 PM UTC to Sep 25, 2026, 10:33 PM UTC (2h 36m)resolved
their latest update (Sep 25, 2026, 10:33 PM UTC): Between 19:24 UTC and 22:04 UTC, a subset of customers in the US region may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing or suppressed alert notifications for related data. We have investigated and resolved this service interruption…
New Relic UI errorsAll systems operational
Sep 25, 2026, 3:56 AM UTC to Sep 25, 2026, 3:56 AM UTC (0 min)resolved
their latest update (Sep 25, 2026, 3:56 AM UTC): Between 01:10 UTC and 03:33 UTC on September 25th, some customers in the US, EU, and JP regions may have experienced intermittent UI errors while navigating the New Relic UI. Data ingest and alert notifications were not impacted. We have resolved this issue and impacted services …
New Relic UI errorsAll systems operational
Sep 25, 2026, 3:55 AM UTC to Sep 25, 2026, 3:55 AM UTC (0 min)resolved
their latest update (Sep 25, 2026, 3:55 AM UTC): Between 01:10 UTC and 03:33 UTC on September 25th, some customers in the US, EU, and JP regions may have experienced intermittent UI errors while navigating the New Relic UI. Data ingest and alert notifications were not impacted. We have resolved this issue and impacted services …
New Relic UI errorsAll systems operational
Sep 25, 2026, 2:34 AM UTC to Sep 25, 2026, 3:44 AM UTC (1h 10m)resolved
their latest update (Sep 25, 2026, 3:44 AM UTC): Between 01:10 UTC and 03:35 UTC on September 25th, some customers in the US EU and JP region may have experienced some intermittent UI navigation errors. We have investigated and resolved this service interruption and impacted services have returned to normal operations.
Potential Service InterruptionOngoing, all systems operational
Sep 25, 2026, 2:23 AM UTC, open for 10d 19h so farinvestigating
their latest update (Sep 25, 2026, 2:23 AM UTC): We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.
Test Incident - Public Status Page -ImpactIQPartial outage
Sep 22, 2026, 8:55 AM UTC to Sep 22, 2026, 8:55 AM UTC (1 min)resolved
their latest update (Sep 22, 2026, 8:55 AM UTC): Test message -resolved
Salesforce Service DisruptionAll systems operational
Sep 16, 2026, 10:08 AM UTC to Sep 16, 2026, 3:40 PM UTC (5h 32m)resolved
their latest update (Sep 16, 2026, 3:40 PM UTC): All in-app services have returned to normal operations. Please reach out to New Relic support for assistance with any issues.
Data Irregularities for EU RegionAll systems operational
Sep 16, 2026, 12:14 AM UTC to Sep 16, 2026, 12:14 AM UTC (0 min)resolved
their latest update (Sep 16, 2026, 12:14 AM UTC): Between 23:06 UTC and 23:16 UTC, some customers in the EU region may have experienced errors when sending metric timeslice data to New Relic, issues in viewing metric timeslice data in real time, and delayed or missing alert notifications related to real time data. Impacted data …
Issues loading Alerts and Activity pageMinor incident
Aug 3, 2026, 9:58 AM UTC to Aug 3, 2026, 10:15 AM UTC (17 min)resolved
their latest update (Aug 3, 2026, 10:15 AM UTC): Between 08:13 and 9:30 UTC on August 3rd, customers in the EU and US regions may have experienced an issue when trying to load the Alerts and Issues page in the New Relic UI. The issue is now resolved, and the impacted services have returned to normal service. Please close and re…
E2M (Events-2-Metrics) authorization issuesAll systems operational
Jul 17, 2026, 10:21 AM UTC to Jul 17, 2026, 10:21 AM UTC (0 min)resolved
their latest update (Jul 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 ma…

Showing the 10 most recent of 58 incidents New Relic has declared in the history we hold.

These entries are New Relic's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How New Relic's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording New Relic's own status page on August 22, 2026, 44 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for New Relic since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

New Relic decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If New Relic believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.