[6.15am] Marking this as finished, although will be monitoring closely over the next 24 hours. If you are seeing a maintenance page, please refresh your browser (and maybe try to clear cache) as it’s probably the old DNS settings have been stored in your browser. You can try Googling “clear DNS cache in [Chrome/Safari/Internet Explorer/Firefox]”
[6.10am] Booking.com Reservations are being synchronised properly.
[6.08am] All services seem to be back up and running.
[6.04am] DNS reconfigured.
[6.03am] All checks passing.
[5.53am] Fixes deployed, we’re now checking the app again.
[5.50am] A few unexpected configuration problems have arisen. We’re fixing and redeploying.
[5.45am] App is deployed and being tested. Taking a little longer than first thought, but we’ll be up and running very soon.
[5.30am] Briefing QA team on how to test app before we switch DNS configuration.
[5.23am] We’re deploying the app to the new servers.
[5.22am] The DB has finished uploading to RDS.
[5.19am] We’re building Docker images on the new servers.
[5.15am] The hedgehog who lives under my shed has come for an early morning snack.
[5.06am] We’re uploading the DB to Amazon’s Relational Database Service (RDS). This will take some time.
[4.59am] Main application DB is downloading.
[4.57am] Okay, we’re closing down the app and beginning migration.
resolved on 25 Jun 2017