outages.live
Live

New Relic

New Relic is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

5

Days with an incident

3

Median duration

7 min

Longest incident

5 h 32 min

Components

106

Alert Notifications : US

APM : US Operational
90 days ago1 day with an incidentToday
Browser : US Operational
90 days ago1 day with an incidentToday
Infrastructure : US Operational
90 days ago1 day with an incidentToday
Logs : US Operational
90 days ago1 day with an incidentToday
Mobile : US Operational
90 days ago1 day with an incidentToday
NRQL : US Operational
90 days ago1 day with an incidentToday
Serverless : US Operational
90 days ago1 day with an incidentToday
Synthetics : US Operational
90 days ago1 day with an incidentToday

Alert Notifications : Europe

APM : Europe Operational
90 days agoNo incidentsToday
Browser : Europe Operational
90 days agoNo incidentsToday
Infrastructure : Europe Operational
90 days agoNo incidentsToday
Logs : Europe Operational
90 days agoNo incidentsToday
Mobile : Europe Operational
90 days agoNo incidentsToday
NRQL : Europe Operational
90 days agoNo incidentsToday
Serverless : Europe Operational
90 days agoNo incidentsToday
Synthetics : Europe Operational
90 days agoNo incidentsToday

Data Ingest : US

APM Agent : US Operational
90 days ago1 day with an incidentToday
Browser Agent : US Operational
90 days ago1 day with an incidentToday
Event API : US Operational
90 days ago1 day with an incidentToday
Incident Intelligence API : US Operational
90 days ago1 day with an incidentToday
Infrastructure Agent : US Operational
90 days ago1 day with an incidentToday
Log API : US Operational
90 days ago1 day with an incidentToday
Metric API : US Operational
90 days ago1 day with an incidentToday
Mobile Agent : US Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 28, 2026

Duration7 min09:35 to 09:42Next-Gen Entity Platform IssuesPartial outage

Between 08:35 and 09:42 UTC on October 28th, we experienced an issue in the JP region affecting the Next Gen Entity Platform (NGEP) where some customers may have been unable to view or manage entities. The issue is now resolved and the service is operating normally.

Sep 25, 2026

Duration2 h 36 min19:57 to 22:33Data Irregularities for US regionPartial outage

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 and impacted services have returned to normal operations.

Duration1 min03:56 to 03:56New Relic UI errorsNotice

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 have returned to normal operations.

Sep 16, 2026

Duration5 h 32 min10:08 to 15:40Salesforce Service DisruptionNotice

All in-app services have returned to normal operations. Please reach out to New Relic support for assistance with any issues.

Duration1 min00:14 to 00:14Data Irregularities for EU RegionNotice

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 may not be recoverable.

Follow New Relic

Your coding agent knows when New Relic is down, and tells you when a failure is theirs, not yours. You can also get New Relic incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "newrelic" and tell me if New Relic has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=newrelic
Slack
/feed subscribe https://outages.live/feed.xml?providers=newrelic

Go from tracking outages to fixing production issues with Polylane.

Try Polylane