Live Domain Check

Is New Relic Down? Check newrelic.com Status and Outages

Run a live reachability check for newrelic.com. Compare the regional responses with the problem you see in New Relic.

Find New Relic help and reporting links, specific checks, and step-by-step guidance below the live result.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked-

Verdict-

Response Time-

Final URL-

Regional checks8 regions

Rate:

No ratings yet.

Is New Relic working for you?

Share a quick update and see what other visitors are experiencing.

Loading community reports…

Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy

Understanding New Relic connection and service problems

New Relic dashboard access and telemetry ingestion may fail in different account regions or products.

The checker above requests newrelic.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual New Relic action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

Looking for another service? Browse developer service checks.

New Relic status information and official help

New Relic service status

Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.

New Relic help and reporting

Choose the account data region and affected telemetry product.

Open newrelic.com

Open the website in your browser and compare it with the result above.

Where to report problems with New Relic

Open New Relic help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.

Details to include in your report

Account region, product, agent/version, query/time range and ingestion/request error without licence keys.

Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to New Relic.

What to check when New Relic is not working

These are troubleshooting comparisons, not claims that New Relic is currently experiencing a particular incident.

Start with the action that failed

Check the account/data region and compare another query over the same time window.

Narrow down the affected service

Inspect one agent or ingestion response and the relevant status component before restarting every monitored host.

Read the actual checker response

A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.

How to check if New Relic is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the newrelic.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
Check for a service notice. Open New Relic status and check whether the named service and incident time fit your error.
Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.

If New Relic Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when New Relic seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open newrelic.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.

2. Preserve a working account session

Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader New Relic issue.

3. Try another network

If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting New Relic support.

Frequently asked questions about New Relic problems

Is New Relic down, or is the problem limited to one feature?

Run the newrelic.com check and compare its original timestamps and responses with your actual error. New Relic dashboard access and telemetry ingestion may fail in different account regions or products.

Where can I report a problem with New Relic?

Use the community buttons on this page to share whether the service works for you. For help from New Relic, use the official help/reporting resource linked above. Choose the account data region and affected telemetry product.

What should I check first when New Relic is not working?

Check the account/data region and compare another query over the same time window. Inspect one agent or ingestion response and the relevant status component before restarting every monitored host.

What information helps New Relic support investigate?