All Systems Operational
Alerting ? Operational
Alert Delivery Operational
SMS Operational
E-mail Operational
PagerDuty (Incident Creation) Operational
PagerDuty (Notification Delivery) Operational
Slack Operational
Webhooks Operational
HipChat Operational
Push notifications (global) ? Operational
Push notifications (iOS) Operational
Push notifications (Android) Operational
Agent payloads ? Operational
API Operational
Availability monitoring ? Operational
Web UI Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Past Incidents
Jul 26, 2016

No incidents reported today.

Jul 25, 2016
Completed - We have completed this maintenance and revert the postback agent payloads IP back to 208.43.108.42. The temporary IP 169.55.60.233 will be kept routed until the initial end date planned for this maintenance: 27 July (Wednesday) at 10AM UTC / 11AM BST.
Jul 25, 12:27 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 21, 15:01 BST
Scheduled - On 21 July (Thursday) at 2PM UTC / 3PM BST we'll be changing the IP address used to postback agent payloads from 208.43.108.42 to 169.55.60.233 for 1 week after which we'll revert to 208.43.108.42. If you currently hard code our postback endpoints within your server's hosts file, you'll need to update it to use the temporary IP (169.55.60.233) as well as update any firewall whitelists.

This change will be reverted on 27 July (Wednesday) at 10AM UTC / 11AM BST.

If you haven't hard coded the IP in your hosts file, you don't need to do anything.
Jul 20, 14:58 BST
Jul 24, 2016

No incidents reported.

Jul 23, 2016
Resolved - We have confirmed all alerting and postback processing have been working as expected since we pushed out our correction at about 11:00 UTC. Nodata alerts have also been activated.

We will be publishing a comprehensive postmortem in the next few days.
Jul 23, 13:08 BST
Monitoring - So far the correction we pushed earlier is proving to be effective. We are still monitoring as we have still to complete the initial maintenance procedure.
Jul 23, 12:24 BST
Update - We have identified the cause of this outage and pushed a fix. We're now confirming it is working as expected.
Jul 23, 11:50 BST
Identified - Following http://status.serverdensity.com/incidents/kkdb6gy84gyw we are still recovering agent payload processing. Graphs are currently not updating and alerting is disabled.
Jul 23, 11:34 BST
Completed - The scheduled maintenance has been completed.
Jul 23, 11:30 BST
Update - During this second part of this maintenance we have experienced a failure to quickly restore service. We're currently not processing payloads and alerting is disabled.
Jul 23, 10:44 BST
Update - We have now completed the first part of this maintenance. The UI was unresponsive between 07:05 and 07:08 UTC and we forced nodata alerts to disabled between 07:05 and 07:40.
Our next brief interruption will be at 08:30 UTC.
Jul 23, 08:45 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 23, 08:06 BST
Scheduled - Tomorrow, July 23nd, between 07:00 and 12:30 UTC we'll be performing maintenance operations on our internal load balancers. The total downtime is expected to be just a few minutes in that time window, as we will be taking advantage of our redundant setup for this service.
Payload processing and alerting will only be affected during that small time window.
We will update this as it happens.
Jul 22, 21:54 BST
Jul 22, 2016
Resolved - Following this incident we'll be announcing a maintenance for tomorrow.
Jul 22, 21:46 BST
Update - This is now fully resolved and nodata alerts are enabled. We will be monitoring for re-occurrences during the next hours.
Jul 22, 17:33 BST
Monitoring - The user interface has been responsive since the last update and we're now monitoring how the systems evolve. Nodata alerts are disabled until we clear all issues.
Unlike what was stated on the previous updates, some devices may have missed postbacks. We'll determine that exactly next.
Jul 22, 15:37 BST
Identified - We have identified a high error rate on one of our load balancers and have diverted the traffic from it. The user interface access is restored now while we continue working on the root failure.
Jul 22, 14:50 BST
Update - We have confirmed that alerting is operational. We are still investigating the user interface loading issue.
Jul 22, 14:25 BST
Investigating - We're currently experiencing an intermittent failure in loading the user interface at .serverdensity.io. We're investigating the cause.
Jul 22, 14:23 BST
Jul 21, 2016
Resolved - This incident has been resolved.
Jul 21, 13:13 BST
Monitoring - Payload processing and alerting has recovered, we'll continue to monitor and update this post with more details about the problem shortly.
Jul 21, 12:23 BST
Update - We're continuing to resolve a problem with one of our payload processing clusters.
Jul 21, 12:12 BST
Investigating - We're looking into a problem with processing payloads. Alerts may trigger slower than expected or not at all while this incident is ongoing and we have disabled no data alerts as a precaution.
Jul 21, 11:55 BST
Jul 20, 2016

No incidents reported.

Jul 19, 2016
Resolved - Nodata alerts have been active again for some minutes now. We will continue to track the cause for the observed drop and post an update once we get it.
Jul 19, 04:19 BST
Monitoring - Traffic is back to normal and nodata alerting will be activated soon. The cause for the earlier traffic drop is still unknown.
Jul 19, 03:11 BST
Update - We are continuing to investigate the drop in agent payload traffic. So far we have independent confirmation from our providers that we are indeed getting less traffic than expected. As such we're leaving the nodata protection active and nodata alerts disabled until we know more.
Jul 19, 02:17 BST
Investigating - We are seeing an abnormally low traffic volume (-5%) from agents into Server Density. Nodata alerts have been automatically disabled to prevent false alerts while we investigate the cause of the low traffic. All other alerting is working as normal.
Jul 19, 01:39 BST
Jul 18, 2016

No incidents reported.

Jul 17, 2016

No incidents reported.

Jul 16, 2016

No incidents reported.

Jul 15, 2016

No incidents reported.

Jul 14, 2016

No incidents reported.

Jul 13, 2016

No incidents reported.

Jul 12, 2016

No incidents reported.