Skip to content

Outage tracker / New Relic

Is New Relic down?

Short linkrlup.io/down/new-relic

I'm having a problem

Operationalchecked 1 minute ago

We reached New Relic from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 10 days we have measured New Relic (since Aug 22, 2026).

our independent probeslive · checked Sep 1, 2026, 4:09 AM UTC
US-East925 msOperational
US-West315 msOperational
Europe560 msOperational
Asia-Pacific829 msOperational
their status pagetheir claim, not our reading

New Relic reports: All systems operational (“All Systems Operational”)

from New Relic's own status page, checked Sep 1, 2026, 3:55 AM UTC
Our probes and New Relic's own status page agree: both show New Relic as reachable right now.

New Relic's own component breakdown, as they publish it

  • Alerts : EuropeOperational
  • Alerts : JPOperational
  • Alerts : USOperational
  • APM : EuropeOperational
  • APM : JPOperational
  • APM : USOperational
  • APM Agent : EuropeOperational
  • APM Agent : JPOperational
  • APM Agent : USOperational
  • APM : EuropeOperational
  • APM : JPOperational
  • APM : USOperational
  • Browser : EuropeOperational
  • Browser : JPOperational
  • Browser : USOperational
  • Browser Agent : EuropeOperational
  • Browser Agent : JPOperational
  • Browser Agent : USOperational
  • Auto-Telemetry with Pixie : EuropeOperational
  • Auto-Telemetry with Pixie : JPOperational
  • Auto-Telemetry with Pixie : USOperational
  • Event API : EuropeOperational
  • Event API : JPOperational
  • Event API : USOperational
  • Infrastructure : EuropeOperational
  • Infrastructure : JPOperational
  • Infrastructure : USOperational
  • AWS Lambda Integration : EuropeOperational
  • AWS Lambda Integration : JPOperational
  • AWS Lambda Integration : USOperational
  • Incident Intelligence API : EuropeOperational
  • Incident Intelligence API : JPOperational
  • Incident Intelligence API : USOperational
  • Logs : EuropeOperational
  • Logs : JPOperational
  • Logs : USOperational
  • Browser : EuropeOperational
  • Browser : JPOperational
  • Browser : USOperational
  • Infrastructure Agent : EuropeOperational
  • Infrastructure Agent : JPOperational
  • Infrastructure Agent : USOperational
  • Mobile : EuropeOperational
  • Mobile : JPOperational
  • Mobile : USOperational
  • Dashboards : EuropeOperational
  • Dashboards : JPOperational
  • Dashboards : USOperational
  • Log API : EuropeOperational
  • Log API : JPOperational
  • Log API : USOperational
  • NRQL : EuropeOperational
  • NRQL : JPOperational
  • NRQL : USOperational
  • Incident Intelligence : EuropeOperational
  • Incident Intelligence : JPOperational
  • Incident Intelligence : USOperational
  • Metric API : EuropeOperational
  • Metric API : JPOperational
  • Metric API : USOperational
  • Serverless : EuropeOperational
  • Serverless : JPOperational
  • Serverless : USOperational
  • Infrastructure : EuropeOperational
  • Infrastructure : JPOperational
  • Infrastructure : USOperational
  • Mobile Agent : EuropeOperational
  • Mobile Agent : JPOperational
  • Mobile Agent : USOperational
  • Synthetics : EuropeOperational
  • Synthetics : JPOperational
  • Synthetics : USOperational
  • Infrastructure Integrations : EuropeOperational
  • Infrastructure Integrations : JPOperational
  • Infrastructure Integrations : USOperational
  • OTLP API : EuropeOperational
  • OTLP API : JPOperational
  • OTLP API : USOperational
  • isNewUserOperational
  • Logs : EuropeOperational
  • Logs : JPOperational
  • Logs : USOperational
  • Trace API : EuropeOperational
  • Trace API : JPOperational
  • Trace API : USOperational
  • Lookout : EuropeOperational
  • Lookout : JPOperational
  • Lookout : USOperational
  • Synthetics : EuropeOperational
  • Synthetics : JPOperational
  • Synthetics : USOperational
  • Mobile : EuropeOperational
  • Mobile : JPOperational
  • Mobile : USOperational
  • Open Instrumentation : EuropeOperational
  • Open Instrumentation : JPOperational
  • Open Instrumentation : USOperational
  • Proactive Detection : EuropeOperational
  • Proactive Detection : JPOperational
  • Proactive Detection : USOperational

These are New Relic's components, named and scored by New Relic. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is New Relic's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

New Relic response time, by region

US-East
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 882ms2026-08-23 UTC: p95 1.5s2026-08-24 UTC: p95 1.6s2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.3s2026-08-28 UTC: p95 1.0s2026-08-29 UTC: p95 926ms2026-08-30 UTC: p95 897ms2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.4s
Aug 3Aug 17Sep 1
US-West
515msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 402ms2026-08-23 UTC: p95 395ms2026-08-24 UTC: p95 488ms2026-08-25 UTC: p95 524ms2026-08-26 UTC: p95 439ms2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 704ms2026-08-29 UTC: p95 846ms2026-08-30 UTC: p95 787ms2026-08-31 UTC: p95 741ms2026-09-01 UTC: p95 515ms
Aug 3Aug 17Sep 1
Europe
756msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 548ms2026-08-23 UTC: p95 967ms2026-08-24 UTC: p95 696ms2026-08-25 UTC: p95 694ms2026-08-26 UTC: p95 727ms2026-08-27 UTC: p95 684ms2026-08-28 UTC: p95 689ms2026-08-29 UTC: p95 718ms2026-08-30 UTC: p95 967ms2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 756ms
Aug 3Aug 17Sep 1
Asia-Pacific
915msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 736ms2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.4s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.3s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 1.1s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.4s2026-09-01 UTC: p95 915ms
Aug 3Aug 17Sep 1

Is it New Relic, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not New Relic -- it cannot diagnose New Relic's own systems.

What we measured, function by function

New Relic answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 925msstatus code: 401checked: Sep 1, 2026, 4:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach New Relic normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 315msstatus code: 401checked: Sep 1, 2026, 4:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach New Relic normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 560msstatus code: 401checked: Sep 1, 2026, 4:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach New Relic normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 829msstatus code: 401checked: Sep 1, 2026, 4:07 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach New Relic normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionNew Relic is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionNew Relic is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionNew Relic is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionNew Relic is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionNew Relic is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionNew Relic is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using New Relic, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for New Relic yet, which is not evidence that nothing is wrong.

Recent outages

Issues loading Alerts and Activity page, 17mdeclared on their status page2026-08-03
E2M (Events-2-Metrics) authorization issues, 1mdeclared on their status page2026-07-17
Delay of Entity Relationship Data, 1mdeclared on their status page2026-07-06
Alerts and Data Irregularities - US and EU region, 1mdeclared on their status page2026-05-18
UI and Data Irregularities - US Region, 1h 38mdeclared on their status page2026-05-15
Issue when querying live edge data in the US region, 2h 28mdeclared on their status page2026-04-13
Synthetics Manager, 10h 55mdeclared on their status page2026-04-09
NrComputeUsage is 0 for ScannedEvents, 5h 10mdeclared on their status page2026-03-24

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring New Relic since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for New Relic covering any window you pick, with our measurements and New Relic's own claim at the time, side by side.

Full availability history for New Relic: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching New Relic, and again when they can reach it again. That is our own measurement from ten regions, not New Relic's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

New Relic uptime measured by RealUptimeLive, from this page's own readings.
[![New Relic uptime measured by RealUptime](https://realuptime.io/outages/new-relic/badge.svg?days=30)](https://realuptime.io/outages/new-relic)
<a href="https://realuptime.io/outages/new-relic"><img src="https://realuptime.io/outages/new-relic/badge.svg?days=30" alt="New Relic uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What New Relic's SLA implies, from our measurement

At or above your target

We measured none of downtime for New Relic over the 244h 11m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 14 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from New Relic's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.newrelic.com/v2/applications.json
secondary
https://newrelic.com/
secondary
https://status.newrelic.com/api/v2/status.json
RealUptime is not affiliated with New Relic; the name identifies what we measured, and nothing here speaks for New Relic's own team. We send a single web request to New Relic from 4 regions on our own schedule and time the response. We do not see inside New Relic's systems, do not use an account or real transaction, and are not the same signal New Relic's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for New Relic is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. New Relic operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 22, 2026 (10 of 14 days so far, 14535 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

AkamaiAmplitudeAnthropicAuth0AWS (Amazon Web Services)