Skip to content

Outage tracker / New Relic

Is New Relic down?

I'm having a problem

Vendor reports no incidentWhat New Relic reports

New Relic reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:52 UTC.

New Relic's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of New Relic pass from all 10 regions we check.

As of Nov 5, 2026, 3:07 PM UTC, RealUptime's checks of New Relic passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:07 PM UTC
US-East838 msChecks passing
US-West780 msChecks passing
Europe745 msChecks passing
Asia-Pacific1292 msChecks passing
US-Central348 msChecks passing
Canada1091 msChecks passing
UK403 msChecks passing
Southeast Asia748 msChecks passing
Australia2138 msChecks passing
South America1362 msChecks passing
their status pagetheir claim, not our reading

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

from New Relic's own status page, checked Nov 5, 2026, 1:22 PM UTC
New Relic's own status page shows no incident, and our checks of New Relic pass right now.

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

  • APM : EuropeOperational
  • APM : JPOperational
  • APM : USOperational
  • APM Agent : EuropeOperational
  • APM Agent : JPOperational
  • APM Agent : USOperational
  • Alerts : EuropeOperational
  • Alerts : JPOperational
  • Alerts : 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
  • Logs : EuropeOperational
  • Logs : JPOperational
  • Logs : USOperational
  • Trace API : EuropeOperational
  • Trace API : JPOperational
  • Trace API : USOperational
  • isNewUserOperational
  • 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.2sp95 · 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-10-07 UTC: p95 509ms2026-10-08 UTC: p95 582ms2026-10-09 UTC: p95 571ms2026-10-10 UTC: p95 501ms2026-10-11 UTC: p95 604ms2026-10-12 UTC: p95 539ms2026-10-13 UTC: p95 541ms2026-10-14 UTC: p95 441ms2026-10-15 UTC: p95 485ms2026-10-16 UTC: p95 513ms2026-10-17 UTC: p95 912ms2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-West
1.3sp95 · 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-10-07 UTC: p95 480ms2026-10-08 UTC: p95 466ms2026-10-09 UTC: p95 482ms2026-10-10 UTC: p95 428ms2026-10-11 UTC: p95 463ms2026-10-12 UTC: p95 506ms2026-10-13 UTC: p95 506ms2026-10-14 UTC: p95 567ms2026-10-15 UTC: p95 482ms2026-10-16 UTC: p95 556ms2026-10-17 UTC: p95 866ms2026-10-18 UTC: p95 971ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 942ms2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Europe
1.1sp95 · 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-10-07 UTC: p95 748ms2026-10-08 UTC: p95 782ms2026-10-09 UTC: p95 651ms2026-10-10 UTC: p95 628ms2026-10-11 UTC: p95 609ms2026-10-12 UTC: p95 737ms2026-10-13 UTC: p95 554ms2026-10-14 UTC: p95 571ms2026-10-15 UTC: p95 649ms2026-10-16 UTC: p95 558ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 940ms2026-10-21 UTC: p95 804ms2026-10-22 UTC: p95 797ms2026-10-23 UTC: p95 728ms2026-10-24 UTC: p95 716ms2026-10-25 UTC: p95 720ms2026-10-26 UTC: p95 847ms2026-10-27 UTC: p95 952ms2026-10-28 UTC: p95 846ms2026-10-29 UTC: p95 971ms2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 917ms2026-11-01 UTC: p95 903ms2026-11-02 UTC: p95 927ms2026-11-03 UTC: p95 901ms2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Asia-Pacific
2.3sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
US-Central
866msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 593ms2026-10-08 UTC: p95 633ms2026-10-09 UTC: p95 493ms2026-10-10 UTC: p95 492ms2026-10-11 UTC: p95 603ms2026-10-12 UTC: p95 553ms2026-10-13 UTC: p95 646ms2026-10-14 UTC: p95 688ms2026-10-15 UTC: p95 562ms2026-10-16 UTC: p95 652ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 882ms2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 949ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 663ms2026-10-29 UTC: p95 466ms2026-10-30 UTC: p95 381ms2026-10-31 UTC: p95 412ms2026-11-01 UTC: p95 409ms2026-11-02 UTC: p95 340ms2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 866ms
Oct 7Oct 21Nov 5
Canada
1.4sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 638ms2026-10-08 UTC: p95 683ms2026-10-09 UTC: p95 723ms2026-10-10 UTC: p95 612ms2026-10-11 UTC: p95 672ms2026-10-12 UTC: p95 739ms2026-10-13 UTC: p95 704ms2026-10-14 UTC: p95 849ms2026-10-15 UTC: p95 773ms2026-10-16 UTC: p95 742ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 939ms2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 960ms2026-10-25 UTC: p95 909ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 954ms2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
UK
516msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 494ms2026-10-08 UTC: p95 512ms2026-10-09 UTC: p95 581ms2026-10-10 UTC: p95 525ms2026-10-11 UTC: p95 549ms2026-10-12 UTC: p95 533ms2026-10-13 UTC: p95 482ms2026-10-14 UTC: p95 457ms2026-10-15 UTC: p95 401ms2026-10-16 UTC: p95 436ms2026-10-17 UTC: p95 624ms2026-10-18 UTC: p95 771ms2026-10-19 UTC: p95 860ms2026-10-20 UTC: p95 857ms2026-10-21 UTC: p95 694ms2026-10-22 UTC: p95 812ms2026-10-23 UTC: p95 800ms2026-10-24 UTC: p95 778ms2026-10-25 UTC: p95 772ms2026-10-26 UTC: p95 826ms2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 942ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 865ms2026-10-31 UTC: p95 652ms2026-11-01 UTC: p95 756ms2026-11-02 UTC: p95 748ms2026-11-03 UTC: p95 609ms2026-11-04 UTC: p95 722ms2026-11-05 UTC: p95 516ms
Oct 7Oct 21Nov 5
Southeast Asia
1.7sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.2s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 3.1s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Australia
3.1sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 2.8s2026-10-18 UTC: p95 2.9s2026-10-19 UTC: p95 3.0s2026-10-20 UTC: p95 2.8s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.8s2026-10-26 UTC: p95 3.0s2026-10-27 UTC: p95 2.9s2026-10-28 UTC: p95 2.6s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 3.8s2026-11-05 UTC: p95 3.1s
Oct 7Oct 21Nov 5
South America
1.3sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 857ms2026-10-08 UTC: p95 758ms2026-10-09 UTC: p95 637ms2026-10-10 UTC: p95 914ms2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.6s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 6.9s2026-10-24 UTC: p95 2.2s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5

Check your own site while you wait on New Relic

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Browser agentUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • EU regionUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • NerdGraphUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sign inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when New Relic reports an incident on its status page, and again when it reports it resolved.

Get an email when New Relic reports an incident

Email me when New Relic reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is New Relic's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 838msstatus code: 401checked: Nov 5, 2026, 3:04 PM 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
      Checks passinglatency: 780msstatus code: 401checked: Nov 5, 2026, 3:00 PM 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.
    • US-Central
      Checks passinglatency: 348msstatus code: 401checked: Nov 5, 2026, 3:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach New Relic normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1091msstatus code: 401checked: Nov 5, 2026, 2:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach New Relic normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1362msstatus code: 401checked: Nov 5, 2026, 2:54 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach New Relic normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 745msstatus code: 401checked: Nov 5, 2026, 3:07 PM 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.
    • UK
      Checks passinglatency: 403msstatus code: 401checked: Nov 5, 2026, 3:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach New Relic normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1292msstatus code: 401checked: Nov 5, 2026, 3:03 PM 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.
    • Southeast Asia
      Checks passinglatency: 748msstatus code: 401checked: Nov 5, 2026, 2:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach New Relic normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2138msstatus code: 401checked: Nov 5, 2026, 2:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach New Relic normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

Data and Alerts Irregularities for US Region, 1mdeclared on their status page2026-11-04
Data Irregularities in US Region, 23mdeclared on their status page2026-11-02
Synthetics Ping Monitor Processing Delays in Multiple Regions, 1h 46mdeclared on their status page2026-11-02
Next-Gen Entity Platform Issues, 7mdeclared on their status page2026-10-28
Data Irregularities for US region, 2h 36mdeclared on their status page2026-09-25
New Relic UI errors, 1mdeclared on their status page2026-09-25
New Relic UI errors, 1mdeclared on their status page2026-09-25
New Relic UI errors, 1h 10mdeclared on their status page2026-09-25

check 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 check readings and New Relic's own claim at the time, side by side.

Full check history for New Relic: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

New Relic uptime by RealUptime's checksLive, from this page's own readings.
[![New Relic uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is New Relic down?", https://realuptime.io/outages/new-relic. The readings change with every check, so give the date you read them.

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
secondary
https://api.newrelic.com/graphql
secondary
https://api.eu.newrelic.com/graphql
secondary
https://login.newrelic.com/
secondary
https://js-agent.newrelic.com/nr-loader-spa-current.min.js

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.newrelic.com

RealUptime is not affiliated with New Relic; the name identifies what we checked, and nothing here speaks for New Relic's own team. We send a single web request to New Relic from 10 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.