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
Past Incidents
Jan 21, 2017

No incidents reported today.

Jan 20, 2017

No incidents reported.

Jan 19, 2017

No incidents reported.

Jan 18, 2017

No incidents reported.

Jan 17, 2017

No incidents reported.

Jan 16, 2017

No incidents reported.

Jan 15, 2017

No incidents reported.

Jan 14, 2017

No incidents reported.

Jan 13, 2017

No incidents reported.

Jan 12, 2017

No incidents reported.

Jan 11, 2017

No incidents reported.

Jan 10, 2017

No incidents reported.

Jan 9, 2017
Completed - This maintenance was completed without issue.
Jan 9, 15:35 GMT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 3, 12:00 GMT
Scheduled - On January 3rd 2017 between 12:00-16:00 UTC we will be deploying an improvement to our alert notification code that may prevent open group alerts from closing automatically at PagerDuty. This update changes the way that alerts are identified to allow for more granularity of group alert notifications, however, this means that any open group alerts at the time of the deployment will not have the same id passed in the fixed message which will prevent the alerts from being closed automatically. Affected users will need to manually close/resolve affected alerts at PagerDuty. Alerts triggered after the deployment of this update will close automatically, as expected, once the alert closes at Server Density.

Change: Improvement of group alert notification identification.

Affected Users: PagerDuty notification users.

Expected Impact: Once the deployment is completed any group alerts that were open at PagerDuty at the time of the deployment will not be automatically closed once the alert has been closed at Server Density. Affected users will need to manually close/resolve the alerts at PagerDuty.
Dec 23, 15:25 GMT
Jan 8, 2017

No incidents reported.

Jan 7, 2017

No incidents reported.