Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frequent 503 error returns #103

Closed
HarveyWMiller opened this issue Jan 20, 2014 · 1 comment
Closed

Frequent 503 error returns #103

HarveyWMiller opened this issue Jan 20, 2014 · 1 comment

Comments

@HarveyWMiller
Copy link

This issue was raised before, but the resolution made it sound like no data would be lost. We've been experiencing many 503 errors each day on multiple servers. At times it is severe enough (over 5 minutes) that we have gaps in our NewRelic data. It appears that the time between 11:00am and 2:00pm PST are when we experience it the most, although we also have error messages from earlier and later as well. Since the servers on our end are on multiple different networks, I believe the issue must be coming from the NewRelic side of the network.

@brunkle
Copy link

brunkle commented Jan 21, 2014

Hi @HarveyWMiller,

Sorry you are having problems with New Relic. We did have some issues today - you can always view the current status at http://status.newrelic.com/

If you are seeing problems outside of the outage period, please reach out to our team at https://support.newrelic.com. I would gladly open a ticket on your behalf, but I don't see enough information on your Github profile to do so. Please log into your New Relic account and then go to "help," and then "File a support ticket." If you have already done this, great! You can reply to the ticket and let us you know that you are still experiencing problems.

Hope this helps. I will close this issue since there doesn't appear to be anything to change on the agent side.

Belinda

@brunkle brunkle closed this as completed Jan 21, 2014
cmcadams-newrelic pushed a commit to cmcadams-newrelic/node-newrelic that referenced this issue Jan 29, 2024
…/sequelize-app/app/semver-6.3.1

chore(deps): bump semver from 6.3.0 to 6.3.1 in /sequelize-app/app
jsumners-nr pushed a commit to jsumners-nr/node-newrelic that referenced this issue Apr 11, 2024
jsumners-nr pushed a commit to jsumners-nr/node-newrelic that referenced this issue Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants