Skip to main content

Is New Relic Down?

No — New Relic is up

Reachable from all 8 checked regions

Average response time: 48ms

Last checked · checks run every 6 hours

Official status page: https://status.newrelic.com

New Relic uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
133ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 26 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

26-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: 100.00% uptime, 8 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 31 checks
Aug 2: 100.00% uptime, 39 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 32 checks
Aug 5: 100.00% uptime, 40 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 24 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 40 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 31 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 35 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad
34ms
DNS 0ms TCP 2ms TLS 9ms TTFB 19ms
jnb
213ms
DNS 0ms TCP 23ms TLS 49ms TTFB 107ms
lax
25ms
DNS 0ms TCP 2ms TLS 5ms TTFB 14ms
lhr
26ms
DNS 0ms TCP 1ms TLS 5ms TTFB 13ms
nrt
27ms
DNS 0ms TCP 2ms TLS 5ms TTFB 17ms
ord
43ms
DNS 0ms TCP 2ms TLS 6ms TTFB 17ms
sin
19ms
DNS 1ms TCP 1ms TLS 4ms TTFB 12ms
sjc
23ms
DNS 0ms TCP 1ms TLS 4ms TTFB 11ms
syd
13ms
DNS 0ms TCP 0ms TLS 3ms TTFB 5ms

What New Relic does

New Relic is an observability platform collecting application traces, infrastructure metrics, logs and browser and mobile telemetry into one place, with alerting on top. Engineering teams install agents across their stack and run on-call from the alerts it raises, which makes it the tool they reach for first when something else breaks.

What an outage looks like

Charts stop at a point and dashboards show a gap rather than an error, so the platform looks healthy while data is missing. Queries and the UI may be slow or fail to load entirely. The consequential symptom is silence: alert notifications stop being delivered, so incidents in your own systems run unannounced and the first sign of trouble arrives from a customer rather than from a page.

What to do about it

Check status.newrelic.com, which reports the US, Europe and JP regions separately and splits data ingest, alert notifications and the UI into distinct components, so a UI incident does not mean alerting has stopped. Agents buffer and retry, so short gaps often backfill. While alert notifications are degraded, watch critical systems another way rather than trusting an empty incident list.

Is it down for everyone, or just you?

If this page says New Relic is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Datadog
Datadog
Sentry
Sentry
G
Grafana Cloud
PagerDuty
PagerDuty

New Relic outage FAQ

Will I still be paged if New Relic is down?
Not necessarily. Alert notifications are listed as their own set of components, separate from both data ingest and the interface, and when they are degraded a condition that should page someone may never reach you. Treat it as a monitoring gap rather than a quiet period, and keep eyes on anything critical until the status page reports notifications healthy again.
Is telemetry lost during a New Relic outage?
Short interruptions usually backfill. New Relic agents buffer data locally and retry, so a brief ingest problem often resolves with the missing window filling in once the connection recovers. Longer incidents exceed what the agent can hold and that data is dropped, which is why a gap that has not filled within a few minutes of recovery is unlikely to appear later.
Is New Relic down or has my agent stopped reporting?
Check whether the relevant ingest component is flagged, since a missing service looks the same from the dashboard either way. If APM Agent and Infrastructure Agent are operational for your region, the problem is more likely a stopped agent, an expired licence key or a host that is genuinely offline. Confirm the agent process is running before assuming an outage.
Does a New Relic outage affect all regions?
Often not. New Relic operates the US, Europe and JP regions separately and reports them individually, so an incident in one may leave accounts in another entirely unaffected. Check the region your account is hosted in first, because reading the wrong one leads teams to either dismiss a real outage or investigate a problem that was never theirs.
Can I see historical data while New Relic ingest is degraded?
Usually yes, provided the UI is healthy. Ingest and the interface are separate components, so dashboards and queries over data already stored keep working while new telemetry fails to arrive. That combination is deceptive during an incident: the charts look normal until you notice the most recent minutes are missing, so check the right-hand edge before drawing conclusions.

How we measure this

  • We request New Relic's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where New Relic publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when New Relic goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required