Is New Relic down right now?

Live status of newrelic.com, checked every 5 minutes.

New Relic is up

Last checked: 22 Oct 2026, 20:13 UTC

Answered in 42 ms

Short answer: No. New Relic is up. Our last check of newrelic.com was on 22 Oct 2026, 20:13 UTC. It answered in 42 ms with HTTP status 200.

New Relic uptime and response time

Uptime today
100%
Uptime, 7 days
100%
Uptime, 30 days
100%
Average response
57 ms
30 days agoToday

Based on 2,871 checks of newrelic.com since 12 Oct 2026. Each bar is one day: green means every check got an answer, amber means some failed, red means most failed, grey means no checks that day.

Recent New Relic problems we saw

None. Every check of newrelic.com since 12 Oct 2026 got an answer.

A failed check means our server got no answer or a server error. It does not show which part of New Relic broke.

New Relic's own status page

New Relic is a monitoring and incident tool. It reports incidents itself, and that report says which part is affected. Check it next to the result above.

status.newrelic.com

Up here but not working for you?

Work down this list. Stop at the first step that fixes it.

  1. Reload the page with the cache skipped: Ctrl + F5 on Windows, Cmd + Shift + R on a Mac.
  2. Open newrelic.com in a private window. If it works there, an extension or a stored cookie is the cause.
  3. Try another network, for example your phone with wifi turned off. If it works, the fault is in your connection or your provider.
  4. Look up the address with our DNS lookup. If it finds records but your computer does not, restart your router or switch DNS server.
  5. Check if only one part is broken (sign-in, payments, uploads). New Relic's status page lists each part.
  6. Wait 10 minutes and try again. Short faults often clear before anyone announces them.

For your own site, the full method is in our website down checklist.

How this check works

  • Every 5 minutes our server sends one request to https://newrelic.com and waits up to 8 seconds.
  • Any answer below HTTP status 500 counts as up. No answer, or a status of 500 or above, counts as failed.
  • A failed check is tried once more after 3 seconds before it is recorded.
  • We check from one location. A fault that only affects another region will not show here.
  • We check one address. New Relic can have a broken feature while this address still answers.

Questions about New Relic status

Is New Relic down right now?+
No. New Relic is up. Our last check of newrelic.com was on 22 Oct 2026, 20:13 UTC. It answered in 42 ms with HTTP status 200.
How often do you check New Relic?+
Every 5 minutes, with one request to https://newrelic.com from our server. A check that fails is tried once more after 3 seconds before it counts as failed. Opening this page also runs one fresh check.
New Relic is up here but it does not work for me. Why?+
Our check only proves that newrelic.com answers a request from our server. The fault can still be on your side (your connection, your DNS, your browser, an ad blocker), in your region only, or in one part of New Relic such as sign-in or payments while the front page still loads.
Where does New Relic announce outages?+
On its own status page: https://status.newrelic.com. That page is written by New Relic and says which part is affected. Ours is an outside check of one address, so the two can disagree for a few minutes at the start of an incident.
What counts as down on this page?+
No answer within 8 seconds, a failed connection, or an HTTP status of 500 or above. Any other answer counts as up, including redirects and a 403, because it shows the server is running.
Can I get this kind of check for my own website?+
Yes. PULSX checks your own site every 60 seconds and sends an alert by email, Slack, Discord, webhook or phone push when it stops answering. It is free for 20 monitors, with no card.

This page watches New Relic. Who watches your site?

PULSX checks your own website, API, cron jobs and SSL certificate every 60 seconds and tells you the minute something fails. Free for 20 monitors, with no card.