No, New Relic is not down
newrelic.com is currently up. Our monitoring probes can reach newrelic.com and complete a check without errors. Latest response time was 188 ms. The latest automated check was run 2026-08-14 18:13 UTC from primary location.
- Current status
- Operational
- Last check
- Checked every 10 minutes
- Last 24 hours
- 100%
Currently up for 2h 42m
Latest 2026-08-14 18:13 UTC · Primary location
0 incidents, 0m down
- Official status
- Operational
- Our check
- Operational
- Active incident
- None
- Last outage
- None recorded
- Response time
- 188 ms
- User reports
- Normal
None today
New Relic live status
115 of 115 operational
- Alert Notifications : EuropeOperational
- Alert Notifications : JPOperational
- Alert Notifications : USOperational
- Alerts : EuropeOperational
- Alerts : JPOperational
- Alerts : USOperational
- APM : EuropeOperational
- APM : EuropeOperational
- APM : JPOperational
- APM : JPOperational
- APM : USOperational
- APM : USOperational
- APM Agent : EuropeOperational
- APM Agent : JPOperational
- APM Agent : USOperational
- Auto-Telemetry with Pixie : EuropeOperational
- Auto-Telemetry with Pixie : JPOperational
- Auto-Telemetry with Pixie : USOperational
- AWS Lambda Integration : EuropeOperational
- AWS Lambda Integration : JPOperational
- AWS Lambda Integration : USOperational
- Browser : EuropeOperational
- Browser : EuropeOperational
- Browser : JPOperational
- Browser : JPOperational
- Browser : USOperational
- Browser : USOperational
- Browser Agent : EuropeOperational
- Browser Agent : JPOperational
- Browser Agent : USOperational
- Dashboards : EuropeOperational
- Dashboards : JPOperational
- Dashboards : USOperational
- Data Ingest : EuropeOperational
- Data Ingest : JPOperational
- Data Ingest : USOperational
- Event API : EuropeOperational
- Event API : JPOperational
- Event API : USOperational
- Incident Intelligence : EuropeOperational
- Incident Intelligence : JPOperational
- Incident Intelligence : USOperational
- Incident Intelligence API : EuropeOperational
- Incident Intelligence API : JPOperational
- Incident Intelligence API : USOperational
- Infrastructure : EuropeOperational
- Infrastructure : EuropeOperational
- Infrastructure : JPOperational
- Infrastructure : JPOperational
- Infrastructure : USOperational
- Infrastructure : USOperational
- Infrastructure Agent : EuropeOperational
- Infrastructure Agent : JPOperational
- Infrastructure Agent : USOperational
- Infrastructure Integrations : EuropeOperational
- Infrastructure Integrations : JPOperational
- Infrastructure Integrations : USOperational
- isNewUserOperational
- Log API : EuropeOperational
- Log API : JPOperational
- Log API : USOperational
- Logs : EuropeOperational
- Logs : EuropeOperational
- Logs : JPOperational
- Logs : JPOperational
- Logs : USOperational
- Logs : USOperational
- Lookout : EuropeOperational
- Lookout : JPOperational
- Lookout : USOperational
- Metric API : EuropeOperational
- Metric API : JPOperational
- Metric API : USOperational
- Mobile : EuropeOperational
- Mobile : EuropeOperational
- Mobile : JPOperational
- Mobile : JPOperational
- Mobile : USOperational
- Mobile : USOperational
- Mobile Agent : EuropeOperational
- Mobile Agent : JPOperational
- Mobile Agent : USOperational
- NRQL : EuropeOperational
- NRQL : JPOperational
- NRQL : USOperational
- Open Instrumentation : EuropeOperational
- Open Instrumentation : JPOperational
- Open Instrumentation : USOperational
- OTLP API : EuropeOperational
- OTLP API : JPOperational
- OTLP API : USOperational
- Proactive Detection : EuropeOperational
- Proactive Detection : JPOperational
- Proactive Detection : USOperational
- Serverless : EuropeOperational
- Serverless : EuropeOperational
- Serverless : JPOperational
- Serverless : JPOperational
- Serverless : USOperational
- Serverless : USOperational
- Synthetics : EuropeOperational
- Synthetics : EuropeOperational
- Synthetics : EuropeOperational
- Synthetics : JPOperational
- Synthetics : JPOperational
- Synthetics : JPOperational
- Synthetics : USOperational
- Synthetics : USOperational
- Synthetics : USOperational
- Trace API : EuropeOperational
- Trace API : JPOperational
- Trace API : USOperational
- UI : EuropeOperational
- UI : JPOperational
- UI : USOperational
Current incident
No active incidents reported by the official New Relic status source.
Response time
Latest 159 ms
Loading response-time chart…
Uptime
Availability from independent checks, with recorded incidents and downtime in each window.
Today
100%
0 incidents, 0m down
Last 7 days
100%
0 incidents, 0m down
Last 30 days
100%
0 incidents, 0m down
Last 365 days
100%
0 incidents, 0m down
Latest New Relic incidents
Recorded outages with duration and start time.
No outage history stored yet.
How this status checker works
Who's Down Today monitors New Relic independently of the company that runs it. We send reachability checks from our primary location every 10 minutes and record response time, HTTP errors, and timeouts.
When New Relic publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.
This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.
Frequently asked questions
Is New Relic down right now?
- No. No, New Relic is not down. Who's Down Today shows New Relic as operational based on the latest official signals and independent checks. If you still cannot reach newrelic.com, the issue may be local to your connection, DNS, VPN, browser, or device.
Is New Relic down for everyone or just me?
- Who's Down Today currently shows New Relic as operational from our monitoring location, which means newrelic.com is responding normally to our checks. If you are still having trouble, try another browser, device, or network, and check DNS or VPN settings.
What should I do if newrelic.com is up but I still cannot access it?
- Try opening newrelic.com from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed New Relic outage.
How does Who's Down Today check if New Relic is down?
- We combine independent HTTP reachability checks with public status information where it exists. When New Relic publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.
What does a New Relic outage mean?
- An outage on this page means recorded incidents or failed checks indicated that New Relic was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.
Can this page tell me the root cause of a New Relic outage?
- Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to New Relic's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.
How do I report an issue with New Relic?
- Use the report form on this page if New Relic looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.