Vendor record
New Relic
Checked
Front door check counts and New Relic’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented New Relic endpoint and count the checks that got the answer it is documented to give.
No clear answer in 24 hours. These counts are from before this check went quiet.
Front door reachable in 0 of 0 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
2,879 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.newrelic.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
- None in this window
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every New Relic product, region or your app worked.
How we count front door checksNew Relic says
Incident posts from New Relic’s status page, with its titles, impact levels and times. They say what New Relic chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
7
incidents New Relic posted, last 1 year
Median recorded duration: 2h 37m. From 7 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Data Irregularities for US region
MajorNew Relic’s postStarted, per New Relic
Closed in our record(2h 37m)
Salesforce Service Disruption
Not specifiedNew Relic’s postStarted, per New Relic
Closed in our record(5h 41m)
Issues loading Alerts and Activity page
MinorNew Relic’s postStarted, per New Relic
Closed in our record(26m)
UI and Data Irregularities - US Region
MajorNew Relic’s postStarted, per New Relic
Closed in our record(1h 43m)
Issue when querying live edge data in the US region
MinorNew Relic’s postStarted, per New Relic
Closed in our record(2h 36m)
2 older records
Synthethcis Manager
MinorNew Relic’s postStarted, per New Relic
Closed in our record(10h 59m)
NrComputeUsage is 0 for ScannedEvents
Not specifiedNew Relic’s postStarted, per New Relic
Closed in our record(5h 25m)
Your code, your dependencies
See which of your code paths call New Relic
Connect GitHub or GitLab to find where your public or private repository uses New Relic. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add New Relic status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is New Relic currently down?
New Relic's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did New Relic last have an outage?
The most recent closed incident record began 20 days ago and spans 2h 37m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for New Relic?
No. CheckUpstream checks New Relic’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor New Relic in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track New Relic?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.