Loading status…
New Relic status · Observability · checked (7s ago)
Also searched as New Relic One, New Relic APM.
No — New Relic is not down. All New Relic systems are reported operational.
According to New Relic's official status page, New Relic was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, New Relic's feed reported no outage in 100.00% of our checks.
Everything above is read from New Relic's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported New Relic in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
New Relic is an observability platform — APM, infrastructure monitoring, logs, browser and synthetic monitoring, all queried through NRQL. Like every monitoring vendor, its outages are felt as blindness rather than breakage: your systems keep running, you just cannot see them.
The status page separates data ingestion from querying and alerting, and separates the US and EU data centres. That regional split is essential — a EU-region account is unaffected by most US incidents and vice versa. Alerting is the component worth watching, because an alerting outage means notifications silently do not arrive.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where New Relic's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days New Relic was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 7s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of New Relic's status endpoint.
New Relic has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what New Relic posted itself — not every problem users hit.
resolved · Sep 16, 10:08 AM (3d ago)
resolved · Sep 16, 12:14 AM (4d ago)
resolved · Aug 3, 09:58 AM (47d ago)
resolved · Jul 17, 10:21 AM (64d ago)
resolved · Jul 6, 08:23 AM (75d ago)
resolved · May 18, 04:25 PM (124d ago)
resolved · May 15, 12:06 AM (128d ago)
resolved · Apr 13, 12:44 PM (159d ago)
resolved · Apr 9, 09:51 AM (163d ago)
resolved · Mar 24, 05:22 AM (180d ago)
resolved · Mar 20, 03:52 PM (183d ago)
resolved · Mar 3, 12:19 AM (201d ago)
resolved · Mar 2, 07:06 AM (201d ago)
resolved · Feb 18, 10:06 AM (213d ago)
resolved · Feb 5, 04:20 PM (226d ago)
resolved · Jan 21, 10:23 PM (241d ago)
resolved · Jan 12, 03:21 PM (250d ago)
resolved · Dec 18, 11:30 PM (275d ago)
resolved · Nov 19, 11:48 AM (304d ago)
resolved · Nov 18, 12:34 PM (305d ago)
Missing data is usually the agent rather than the platform: check the agent is running, is a supported version, and has a valid licence key. Data ingest has a lag of a minute or two by design, so very recent data legitimately is not there yet. NRQL queries hitting a data retention boundary return empty rather than an error, which reads exactly like data loss and is not.
New Relic is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
GrafanaOperationalDashboards and alerting over metrics you are already shipping
DatadogDegradedAPM, infrastructure and logs in one place while you are blindThis one is reporting problems too.Status shown for each is read from that provider's own feed, on the same schedule as this page.
