Router maintenance (fcr05.wdc01 and bcr05.wdc01)
Scheduled Maintenance Report for Server Density
Completed
Yesterday at 11:20 UTC device payload processing fell into the expected boundaries and we have enabled automated nodata protection.
This completes this maintenance.
Posted Jun 08, 2017 - 11:42 BST
Verifying
We are coming to the end of this maintenance window. Our provider has completed their work.

We will be enabling nodata alerts next. However, during this maintenance, we have experienced out of boundaries device payload processing which prevents the automated nodata protection from working as expected. Please email hello@serverdensity.com if you get a false device nodata alert.
Posted Jun 06, 2017 - 10:56 BST
Update
As some customers are sending payloads through the previously affected endpoint (.serverdensity.io) they will see gaps on graphs and those devices didn't trigger alerts for that period. This endpoint is deprecated for all but Windows device postbacks and we will be contacting these customers to work a move to the current endpoint .agent.serverdensity.io to all but the windows agent.

For all other customers the current impact is device nodata alerts being off as a precaution measure while this maintenance is ongoing to prevent false positives.
Posted Jun 06, 2017 - 09:24 BST
In progress
This maintenance has disabled UI access 05:05 UTC until 06:59 UTC. We're continuing to monitor our provider progress on this work and continue to update this event.
Posted Jun 06, 2017 - 08:11 BST
Scheduled
As a result of the outages we have been experiencing at our infrastructure provider, they have been working with their networking equipment manufacturer and have identified an issue on their routers, which provides connectivity for some of our servers. In order to prevent an unplanned outage resulting in significant downtime, our provider will be upgrading the firmware during this maintenance window.

During two brief periods in this maintenance window, traffic will be first stopped at the public network and then on the private network. This will impact our service as it relies on the public network for customer access and on the private network for internal communication.

While the maintenance window is set for 6 hours, our provider expects no more than two occurrences of 3 minutes of downtime. Should they encounter an unexpected issue, the disruption could extend to as much as 30 minutes. However, since they have worked with the router's manufacturer on optimizing the maintenance procedure, each downtime should be no more than 3 minutes.

We will follow up this closely and update this as it progresses.
Posted May 17, 2017 - 12:29 BST