Sentry’s real-time error tracking gives you insight into production deployments and information to reproduce and fix crashes.
Homepage: https://sentry.io
Status Page: https://status.sentry.io
Action | Date | Description |
---|---|---|
Resolved | 2017-01-18 23:13:00 | This incident has been resolved. |
Monitoring | 2017-01-18 21:09:00 | We have resolved the root cause and response times are recovering. We'll be monitoring the situation and update this ticket if anything changes. |
Investigating | 2017-01-18 20:03:00 | We're currently investigating high response times from our load balancers. |
Action | Date | Description |
---|---|---|
Resolved | 2017-01-04 22:42:00 | Maintenance is complete without any issues or downtime. |
Monitoring | 2017-01-04 21:57:00 | We are about to begin some necessary unscheduled maintenance. There should be no downtime and no loss of event ingestion, but there will be slight delays once maintenance begins for a brief period. |
Action | Date | Description |
---|---|---|
Resolved | 2016-12-06 09:01:00 | Everything has fully recovered and back to normal. |
Monitoring | 2016-12-06 08:38:00 | Network latency seems better and our queue backlog is recovering. We're actively monitoring to make sure things recover fully. |
Investigating | 2016-12-06 07:02:00 | We are experiencing a widespread network outage at our datacenter and have opened up a ticket with our provider. |
Action | Date | Description |
---|---|---|
Resolved | 2016-10-21 23:34:00 | We have confirmed that everything appears to be fine now with Dyn. |
Monitoring | 2016-10-21 20:41:00 | We have added in a redundant DNS provider and things appear to be healthier again and all DNS records should be resolving. Going to leave in Monitoring state until Dyn has resolved their issues entirely.See https://www.dynstatus.com/incidents/nlr4yrr162t8 for more information. |
Identified | 2016-10-21 17:40:00 | The infrastructure of our DNS provider is currently suffering under a DDOS attack and as such some users might be unable to resolve the Sentry servers. |
Action | Date | Description |
---|---|---|
Resolved | 2016-10-14 01:14:00 | We have completely rolled onto a new SSL certificate 100% mitigating the issue. |
Update | 2016-10-13 21:55:00 | We are in process of rolling out a new certificate for cdn.ravenjs.com that should 100% resolve the issue, but in the meantime, GlobalSign has provided information on resolving the issue:https://www.globalsign.com/en/customer-revocation-error/https://support.globalsign.com/customer/portal/articles/2599710-ocsp-revocation-errors---troubleshooting-guide |
Identified | 2016-10-13 20:33:00 | The SSL Certificate provider for cdn.ravenjs.com and our own status page, status.sentry.io may be experiencing issues for some users.This was due to a massive premature revocation of certificates by GlobalSign. https://www.globalsign.com/en/status/ |
Action | Date | Description |
---|---|---|
Resolved | 2016-09-27 22:50:00 | We have resolved the core issue around 12:00 PDT. During the time period of 08:00 to 12:00 PDT, some customers may have seen dropped events. We greatly apologize for this, and we are doing everything we can to prevent this from happening again in the future. If you have any further questions, feel free to contact us through our support channels. |
Monitoring | 2016-09-27 17:11:00 | The issue has stabilized and our queue is catching up now. |
Investigating | 2016-09-27 16:37:00 | We're currently investigating slow processing time on our queues. |
Action | Date | Description |
---|---|---|
Resolved | 2016-09-06 00:20:00 | FastMail has addressed the issue, and we are delivering email again. |
Identified | 2016-09-05 23:15:00 | FastMail customers are not getting emails. Our outbound IPs are being rate limited by FastMail. We have an open ticket with them to try and alleviate the issue. In the meantime, you may want to switch your Sentry email to something not backed by FastMail. |
Action | Date | Description |
---|---|---|
Resolved | 2016-09-02 08:01:00 | This incident has been resolved. |
Monitoring | 2016-09-02 05:20:00 | A fix has been implemented and we are monitoring the results. |
Investigating | 2016-09-02 04:59:00 | We are investigating an outage with our web nodes. |
Action | Date | Description |
---|---|---|
Completed | 2016-08-30 21:18:00 | We have completed migrating our top level domain: https://blog.sentry.io/2016/08/30/sentry-io.html |
Scheduled | 2016-08-30 21:00:00 | We are transitioning our top level domain (getsentry.com to sentry.io). Users affected by this change have already been notified via email, and are limited to U2F accounts. We don't expect any additional issues, and things should be seamless for all other components. |
Action | Date | Description |
---|---|---|
Resolved | 2016-07-29 05:13:00 | Backlog has caught up and network appears to be stable. |
Monitoring | 2016-07-29 04:42:00 | Our provider claims to have resolved the issue and our queue backlog is catching up. We're continuing to monitor to make sure things stay stable. |
Investigating | 2016-07-29 03:13:00 | Our datacenter is currently experiencing some internal networking issues that we are investigating. Our event processing queue is backing up, so notifications will be delayed. |