We have completed the upgrade and everything appears to be operating smoothly. As always if you notice anything out of the ordinary please email support@dnsimple.com and we'll be there to help. Thank you again for your patience everyone!
Posted Feb 21, 2017 - 02:42 UTC
Verifying
The upgrade completed successfully. So far it looks like only the redirector service lost connectivity which was quickly corrected. We're now waiting for the background queues to clear and keeping a close eye on zone updates. If you notice anything not working as it should, please email support@dnsimple.com before we proceed and close out this maintenance window.
Posted Feb 21, 2017 - 02:13 UTC
Update
We have completed synchronizing the regions which took longer than expected as we're trying very hard to avoid any outages during this upgrade. We'll be performing the database upgrade momentarily. During this time the website and API may respond with HTTP status code 503.
Posted Feb 21, 2017 - 01:16 UTC
Update
We are still synchronizing all of the regions ahead of this upgrade. We'll update here once we're ready to complete the migration. Thank you once again for your patience.
Posted Feb 20, 2017 - 23:55 UTC
In progress
We're beginning the migration and will synchronize all the regions once the upgrade is completed. Zone updates across all regions during this window will be delayed until we complete the upgrade. Once we begin the cutover process the website and API will return 503 HTTP status codes for a short period of time. We'll let you know shortly before this outage occurs.
Posted Feb 20, 2017 - 21:06 UTC
Update
Ahead of today's maintenance we're going to upgrading and reconfiguring our SecondaryDNS service and San Jose region. Updates to the San Jose region will be delayed and SecondaryDNS will be delayed for a few minutes while everything updates.
Posted Feb 20, 2017 - 20:19 UTC
Scheduled
We will be completing the database cluster upgrade that we began on 2/16 which will include a short web and API outage. During this window we will respond with HTTP status 503 on both web and API as we upgrade the cluster.