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
Maintenance
Scheduled Maintenance
On 2017-03-31, CentOS & Red Hat 5 reached end of life. On 2017-04-28, Ubuntu 12.04 will also reach end of life. After these dates, there will be no further updates for these operating systems. We have maintained support in our monitoring agent for these operating systems whilst they are supported by their vendors because our policy is to support all OSs currently in active maintenance.

As of 2017-04-28, we will no longer officially support older OSs running Python 2.6 and the minimum Python version required for the monitoring agent will be 2.7. A final bug fix release for the agent will be made available after this date but there will be no further agent updates. This release will be made available indefinitely for any customers who wish to continue with older OSs. However, we have a range of new features planned in the coming months which will be released in a new agent point release which will require Python 2.7 support, and so will only be available on newer OSs.

For customers running older OSs, nothing will change - your monitoring will continue to work without any problems. However, you will need to upgrade to new OSs to gain access to new features and/or agent bug fixes. We will also only be able to provide technical support on for these older OSs on a "best efforts" basis, which may mean we have to request you upgrade to fix agent problems.

For customers running newer OSs but without Python 2.7 (e.g. CentOS & Red Hat 6) we will provide an officially supported guide for installing Python 2.7 similar to the guide we provide for installing Python 2.6 onto CentOS & Red Hat 5 (which come with Python 2.4 by default). This will be available at the same time as the agent release which requires Python 2.7.

If you have any questions about this or wish to discuss extended support options for older OS, please get in touch: hello@serverdensity.com
Posted on Apr 5, 15:16 BST
Past Incidents
Apr 26, 2017

No incidents reported today.

Apr 25, 2017

No incidents reported.

Apr 24, 2017

No incidents reported.

Apr 23, 2017

No incidents reported.

Apr 22, 2017

No incidents reported.

Apr 21, 2017
Resolved - We have not seen a re-occurrence of this issue again.
Also, we have deployed a code fix to prevent false nodata alerts if the received postbacks drop below a certain number.

We'll be releasing a postmortem about this incident in the next few days.
Apr 21, 20:43 BST
Monitoring - Response times to our postbacks endpoint has normalized. We will continue to monitor this and confirm with our provider if this has been a re-ocurrence. If you got a false nodata alert between 00:00 and 05:00 UTC today please report to hello@serverdensity.com.
Apr 21, 07:11 BST
Identified - In the last hours we have seen elevated response times to our postback endpoint again. We're actively investigating the cause to determine if the same or a new issue. If you got a false nodata alert please report to hello@serverdensity.com.
Apr 21, 06:24 BST
Update - We're keeping this open a few more hours because we observed some transient timeouts during this morning.
Apr 20, 14:04 BST
Monitoring - Our provider reported: "An upstream transit provider incorrectly advertised a route that caused customer traffic to be incorrectly sent to that provider which would have caused customers to be unable to reach multiple datacenters for the duration of the event. Routing was corrected by the upstream transit provider at approximately 11:40 UTC and services should have begun to to stabilize at that time."

We have confirmed expected monitoring values in the last 40 minutes and have enabled nodata alerting at 14:30 UTC.

During the next hours we will continue to monitor networking parameters for re-occurrences.
Apr 19, 15:37 BST
Update - Our provider has informed that a routing anomaly is causing the higher than normal latency and timeouts we've been seeing and is working to identify its source. We will continue to keep nodata alerts disabled.
Apr 19, 14:19 BST
Update - Our provider has identified the ongoing problem and is working to restore full service. We are still seeing some network degradation and we are keeping nodata alerts disabled to prevent further occurrences from false nodata triggers. Alerting delays, if any, are residual now.
Apr 19, 13:45 BST
Update - We are continuing to work with our provider on this issue. We are seeing a reduced error rate but haven't received confirmation yet. We're currently keeping nodata alerts disabled to prevent further occurrences from false nodata triggers.
Apr 19, 13:07 BST
Identified - We have identified network degradation on our public Internet uplinks. We're are reaching to our provider on this.
This is causing gaps on graphs, delayed alerting triggers and false nodata on some devices.
Apr 19, 12:30 BST
Investigating - We're currently investigating a high error rate on postback intake
Apr 19, 12:10 BST
Apr 18, 2017

No incidents reported.

Apr 17, 2017

No incidents reported.

Apr 16, 2017

No incidents reported.

Apr 15, 2017

No incidents reported.

Apr 14, 2017

No incidents reported.

Apr 13, 2017

No incidents reported.

Apr 12, 2017

No incidents reported.