Service status & outage reports

Is New Relic down?

Check New Relic availability, incident history, downtime reports, and website performance.

https://newrelic.com/ ↗
Provider reports operational

Mapped components are operational in the latest status update; individual experiences can vary.

0 recorded outage reports · rolling 24 hours

Text version ↗

My watchlist

Estimated down reports for New Relic

Last 24 hours

There is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.

Last collection attempt: 2026-10-20 08:08:35 UTC · Insufficient activity.

No user-submitted outage reports in the last 24 hours.

New Relic outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

NovDecJanFebMarAprMayJunJulAugSepOct
GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

New Relic website uptime and response time

Website responded successfully HTTP 200. Last checked 2026-10-22 00:14:57 UTC.

Checked address: https://newrelic.com/

DNS lookup: 2 ms · TCP connection: 31 ms · TLS handshake: 65 ms. Certificate expires 2027-02-08; trusted connection: yes.

100%
Successful website checks (24h)
137 successful / 137 measurable checks

26 ms
Median response time

53 ms
95th percentile response time

Successful website response times, 0 to 442 milliseconds442 ms0 ms2026-10-21T12:36:33.000Z: 31 ms2026-10-21T12:41:43.000Z: 24 ms2026-10-21T12:46:51.000Z: 20 ms2026-10-21T12:52:01.000Z: 33 ms2026-10-21T12:57:09.000Z: 23 ms2026-10-21T13:02:16.000Z: 23 ms2026-10-21T13:07:25.000Z: 35 ms2026-10-21T13:12:35.000Z: 18 ms2026-10-21T13:17:45.000Z: 19 ms2026-10-21T13:22:55.000Z: 28 ms2026-10-21T13:28:01.000Z: 442 ms2026-10-21T13:33:07.000Z: 23 ms2026-10-21T13:38:13.000Z: 20 ms2026-10-21T13:43:21.000Z: 20 ms2026-10-21T13:48:30.000Z: 24 ms2026-10-21T13:53:39.000Z: 22 ms2026-10-21T13:58:49.000Z: 21 ms2026-10-21T14:03:57.000Z: 29 ms2026-10-21T14:09:05.000Z: 27 ms2026-10-21T14:14:14.000Z: 32 ms2026-10-21T14:19:21.000Z: 32 ms2026-10-21T14:24:31.000Z: 30 ms2026-10-21T14:29:41.000Z: 29 ms2026-10-21T14:34:51.000Z: 27 ms2026-10-21T14:39:58.000Z: 25 ms2026-10-21T14:45:05.000Z: 24 ms2026-10-21T14:50:11.000Z: 50 ms2026-10-21T14:55:15.000Z: 20 ms2026-10-21T15:00:21.000Z: 21 ms2026-10-21T15:05:27.000Z: 36 ms2026-10-21T15:10:33.000Z: 33 ms2026-10-21T15:15:39.000Z: 21 ms2026-10-21T15:20:47.000Z: 32 ms2026-10-21T15:25:53.000Z: 19 ms2026-10-21T15:31:03.000Z: 29 ms2026-10-21T15:36:07.000Z: 20 ms2026-10-21T15:41:13.000Z: 31 ms2026-10-21T15:46:21.000Z: 39 ms2026-10-21T15:51:31.000Z: 25 ms2026-10-21T15:56:39.000Z: 28 ms2026-10-21T16:01:48.000Z: 22 ms2026-10-21T16:06:57.000Z: 27 ms2026-10-21T16:12:07.000Z: 19 ms2026-10-21T16:17:17.000Z: 21 ms2026-10-21T16:22:25.000Z: 48 ms2026-10-21T16:27:35.000Z: 19 ms2026-10-21T16:32:39.000Z: 21 ms2026-10-21T16:37:45.000Z: 24 ms2026-10-21T16:42:49.000Z: 51 ms2026-10-21T16:47:55.000Z: 26 ms2026-10-21T16:53:03.000Z: 19 ms2026-10-21T16:58:13.000Z: 22 ms2026-10-21T17:03:23.000Z: 23 ms2026-10-21T17:08:32.000Z: 23 ms2026-10-21T17:13:41.000Z: 22 ms2026-10-21T17:18:51.000Z: 27 ms2026-10-21T17:24:01.000Z: 55 ms2026-10-21T17:29:09.000Z: 25 ms2026-10-21T17:34:17.000Z: 17 ms2026-10-21T17:39:27.000Z: 26 ms2026-10-21T17:44:33.000Z: 27 ms2026-10-21T17:49:37.000Z: 23 ms2026-10-21T17:54:43.000Z: 21 ms2026-10-21T17:59:50.000Z: 27 ms2026-10-21T18:04:58.000Z: 20 ms2026-10-21T18:10:07.000Z: 36 ms2026-10-21T18:15:17.000Z: 28 ms2026-10-21T18:20:26.000Z: 17 ms2026-10-21T18:25:31.000Z: 29 ms2026-10-21T18:30:39.000Z: 22 ms2026-10-21T18:35:49.000Z: 29 ms2026-10-21T18:40:59.000Z: 43 ms2026-10-21T18:46:09.000Z: 27 ms2026-10-21T18:51:17.000Z: 27 ms2026-10-21T18:56:27.000Z: 29 ms2026-10-21T19:01:35.000Z: 26 ms2026-10-21T19:06:43.000Z: 23 ms2026-10-21T19:11:51.000Z: 26 ms2026-10-21T19:17:01.000Z: 34 ms2026-10-21T19:22:11.000Z: 37 ms2026-10-21T19:27:19.000Z: 22 ms2026-10-21T19:32:28.000Z: 24 ms2026-10-21T19:37:37.000Z: 20 ms2026-10-21T19:42:47.000Z: 42 ms2026-10-21T19:47:55.000Z: 22 ms2026-10-21T19:53:03.000Z: 27 ms2026-10-21T19:58:13.000Z: 27 ms2026-10-21T20:03:21.000Z: 47 ms2026-10-21T20:08:30.000Z: 19 ms2026-10-21T20:13:39.000Z: 26 ms2026-10-21T20:18:48.000Z: 39 ms2026-10-21T20:23:57.000Z: 21 ms2026-10-21T20:29:05.000Z: 44 ms2026-10-21T20:34:15.000Z: 26 ms2026-10-21T20:39:23.000Z: 24 ms2026-10-21T20:44:31.000Z: 26 ms2026-10-21T20:49:41.000Z: 26 ms2026-10-21T20:54:50.000Z: 44 ms2026-10-21T20:59:58.000Z: 38 ms2026-10-21T21:05:07.000Z: 21 ms2026-10-21T21:10:13.000Z: 20 ms2026-10-21T21:15:21.000Z: 21 ms2026-10-21T21:20:31.000Z: 20 ms2026-10-21T21:25:39.000Z: 40 ms2026-10-21T21:30:49.000Z: 27 ms2026-10-21T21:35:57.000Z: 32 ms2026-10-21T21:41:02.000Z: 36 ms2026-10-21T21:46:07.000Z: 53 ms2026-10-21T21:51:11.000Z: 25 ms2026-10-21T21:56:17.000Z: 29 ms2026-10-21T22:01:21.000Z: 42 ms2026-10-21T22:06:27.000Z: 20 ms2026-10-21T22:11:31.000Z: 30 ms2026-10-21T22:16:37.000Z: 18 ms2026-10-21T22:21:42.000Z: 80 ms2026-10-21T22:26:49.000Z: 23 ms2026-10-21T22:31:58.000Z: 48 ms2026-10-21T22:37:05.000Z: 49 ms2026-10-21T22:42:15.000Z: 22 ms2026-10-21T22:47:25.000Z: 31 ms2026-10-21T22:52:35.000Z: 28 ms2026-10-21T22:57:45.000Z: 38 ms2026-10-21T23:02:55.000Z: 23 ms2026-10-21T23:08:03.000Z: 31 ms2026-10-21T23:13:13.000Z: 21 ms2026-10-21T23:18:23.000Z: 30 ms2026-10-21T23:23:30.000Z: 21 ms2026-10-21T23:28:39.000Z: 19 ms2026-10-21T23:33:49.000Z: 16 ms2026-10-21T23:38:59.000Z: 24 ms2026-10-21T23:44:07.000Z: 22 ms2026-10-21T23:49:17.000Z: 41 ms2026-10-21T23:54:27.000Z: 21 ms2026-10-21T23:59:35.000Z: 138 ms2026-10-22T00:04:43.000Z: 82 ms2026-10-22T00:09:51.000Z: 22 ms2026-10-22T00:14:57.000Z: 136 ms

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

New Relic official status · fetched 2026-10-22 00:11:10 UTC

115 mapped components · 0 reporting problems
ComponentProvider status
APM : USoperational
APM : Europeoperational
APM Agent : USoperational
APM Agent : Europeoperational
Alerts : USoperational
Alerts : Europeoperational
Data Ingest : USoperational
APM Agent : JPoperational
APM : JPoperational
Alerts : JPoperational
APM : USoperational
Browser : USoperational
APM : Europeoperational
Browser : Europeoperational
Browser Agent : USoperational
Browser Agent : Europeoperational
Alert Notifications : USoperational
Browser Agent : JPoperational
Browser : JPoperational
APM : JPoperational
Infrastructure : USoperational
Infrastructure : Europeoperational
Event API : USoperational
Event API : Europeoperational
Auto-Telemetry with Pixie : USoperational
Auto-Telemetry with Pixie : Europeoperational
UI : USoperational
Event API : JPoperational
Infrastructure : JPoperational
Auto-Telemetry with Pixie : JPoperational
Logs : USoperational
AWS Lambda Integration : USoperational
Logs : Europeoperational
AWS Lambda Integration : Europeoperational
Incident Intelligence API : USoperational
Data Ingest : Europeoperational
Incident Intelligence API : Europeoperational
Incident Intelligence API : JPoperational
Logs : JPoperational
AWS Lambda Integration : JPoperational
Browser : USoperational
Mobile : USoperational
Browser : Europeoperational
Mobile : Europeoperational
Infrastructure Agent : USoperational
Infrastructure Agent : Europeoperational
Alert Notifications : Europeoperational
Infrastructure Agent : JPoperational
Mobile : JPoperational
Browser : JPoperational
Dashboards : USoperational
Dashboards : Europeoperational
NRQL : USoperational
NRQL : Europeoperational
Log API : USoperational
Log API : Europeoperational
UI : Europeoperational
Log API : JPoperational
NRQL : JPoperational
Dashboards : JPoperational
Serverless : USoperational
Serverless : Europeoperational
Incident Intelligence : USoperational
Metric API : USoperational
Incident Intelligence : Europeoperational
Metric API : Europeoperational
Data Ingest : JPoperational
Metric API : JPoperational
Serverless : JPoperational
Incident Intelligence : JPoperational
Synthetics : USoperational
Infrastructure : USoperational
Synthetics : Europeoperational
Infrastructure : Europeoperational
Mobile Agent : USoperational
Mobile Agent : Europeoperational
Mobile Agent : JPoperational
Alert Notifications : JPoperational
Synthetics : JPoperational
Infrastructure : JPoperational
OTLP API : USoperational
OTLP API : Europeoperational
Infrastructure Integrations : USoperational
Infrastructure Integrations : Europeoperational
OTLP API : JPoperational
UI : JPoperational
Infrastructure Integrations : JPoperational
isNewUseroperational
Logs : USoperational
Logs : Europeoperational
Trace API : USoperational
Trace API : Europeoperational
Trace API : JPoperational
Logs : JPoperational
Lookout : USoperational
Lookout : Europeoperational
Synthetics : USoperational
Synthetics : Europeoperational
Synthetics : JPoperational
Lookout : JPoperational
Mobile : USoperational
Mobile : Europeoperational
Mobile : JPoperational
Open Instrumentation : USoperational
Open Instrumentation : Europeoperational
Open Instrumentation : JPoperational
Proactive Detection : USoperational
Proactive Detection : Europeoperational
Proactive Detection : JPoperational
Serverless : USoperational
Serverless : Europeoperational
Serverless : JPoperational
Synthetics : USoperational
Synthetics : Europeoperational
Synthetics : JPoperational

Official incident timeline

Data Irregularities for US region · resolved · 2026-09-25T22:33:40.382Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    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.

  2. · identified

    At this time, we are seeing increased recovery of impacted services related to delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data in the US region.

  3. · identified

    We continue seeing recovery for impacted services as we work to resolve this service interruption where a subset of customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. Alerts are no longer suppressed.

  4. · investigating

    We are seeing recovery from some impacted services as we continue investigating a service interruption where a subset of customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. Affected alerts are currently being suppressed.

  5. · investigating

    We are continuing to investigate a service interruption where a subset of customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. Affected alerts are currently being suppressed.

  6. · investigating

    We are currently investigating a service interruption where a subset of customers may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. Affected alerts are currently being suppressed.

New Relic UI errors · resolved · 2026-09-25T06:21:46.317Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    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.

Salesforce Service Disruption · resolved · 2026-09-16T15:40:58.878Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

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

  2. · monitoring

    If you are experiencing issues and unable to access In-App support, please reach out to our Support team through this form: https://support.newrelic.com/s/contact-new-relic-support-form

Data Irregularities for EU Region · resolved · 2026-09-16T00:14:24.345Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    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.

Issues loading Alerts and Activity page · resolved · 2026-08-03T10:15:58.713Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    Between 08:13 and 9:30 UTC on August 3rd, customers in the EU and US regions may have experienced an issue when trying to load the Alerts and Issues page in the New Relic UI. The issue is now resolved, and the impacted services have returned to normal service. Please close and re-open the Alerts page to resolve the issue.

  2. · investigating

    We are investigating an issue where some customers in the EU and US regions may experience delays or errors when viewing the alerts and activity page.

E2M (Events-2-Metrics) authorization issues · resolved · 2026-07-17T10:21:26.675Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    Between 15:00 UTC on July 14th and 10:00 UTC on July 17th, we experienced an issue where some customers experienced authorization issues when attempting to create, read or update E2M (Events-2-Metrics) rules in the US, EU and JP regions. This was due to a recent change we have made to our authorization endpoints. These endpoints now require S2S authentication which has caused requests to our E2M (Events-2-Metrics) to fail. Our teams have rolled back these changes until a permanent fix can be put

Delay of Entity Relationship Data · resolved · 2026-07-06T08:28:19.349Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    Between 07:20 and 08:12 UTC on July 6th, we experienced an issue where some customers in the EU region may have experienced a delay of entity relationships appearing and refreshing in the New Relic platform. The issue is now resolved and the impacted services have returned to normal service.

Alerts and Data Irregularities - US and EU region · resolved · 2026-05-18T16:25:20.674Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    Between 10:30 UTC and 13:32 UTC on May 16th, some customers in the US and EU regions may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing, or false alert notifications for impacted data related to a service interruption involving a 3rd party cloud provider. The cloud provider resolved the service interruption and impacted services have returned to normal operations.

Recovery tracker

No recent recovery can be established from available evidence.

6 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

Slowdown detection

No sustained slowdown has been established against the earlier baseline.

Recent median: 82 ms · Earlier median: 26 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

Emerging down-report signals

  • is new relic down

Query “new relic” · observed 2026-10-22 00:10:52 UTC · 0 newly observed problem phrases.

Query “is new relic” · observed 2026-10-22 00:10:52 UTC · 0 newly observed problem phrases.

Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

Is it down in your region?

Run one public website check from a community probe. Results describe that probe, not every user in a country.

Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

Infrastructure incident context

Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of New Relic.

GitHub official status · 2026-10-22 00:13:12 UTC

No active incidents recorded.

About New Relic status on Iszdown

Check New Relic availability, incident history, downtime reports, and website performance.

This page combines the available New Relic report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

115 product-matched official components are listed above. Latest public website measurement: 2026-10-22T00:14:57.000Z.

Visit the official New Relic website · Official provider status · How it works

What to check when New Relic is not working

These are troubleshooting suggestions, not a list of currently reported problems.

New Relic will not open

Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.

New Relic is slow or only one feature fails

Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.

Website troubleshooting guide · Sign-in problems · API errors and timeouts

Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

Recent New Relic outage history

Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.

IncidentStarted (UTC)Recorded durationLast collected status
Data Irregularities for US region156 minresolved
Issues loading Alerts and Activity page17 minresolved
UI and Data Irregularities - US Region98 minresolved
Issue when querying live edge data in the US region154 minresolved
Synthetics Manager655 minresolved
Data Irregularities - US Region18 minresolved
Data Irregularities160 minresolved
Delay in executing synthetics monitors156 minresolved

Frequently asked questions about New Relic

Is New Relic down right now?

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-22T00:15:47.000Z.

How many New Relic outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

Why does New Relic show operational when it is not working for me?

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every New Relic feature.

When was New Relic status last updated?

The latest status observation was 2026-10-22T00:11:10.000Z. Only matched product components and incidents are shown. The assessment is recent.

Has New Relic had outages before?

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

How do I follow New Relic or report a problem?

Use “Watch this service” to save New Relic in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.

Related services to New Relic

Check a related product separately; its status can differ from New Relic.

Anchorage Daily NewsApple NewsBloomberg NewsCentral News Agency (Taiwan)CTV NewsCity University of New YorkLoyola University New OrleansNew RelicNewgroundsNewsmaxNew Jersey LotteryNew Orleans Saints