Jeff Epler🦉Apr 11, 2017
"Our engineering team has identified the cause of this connectivity issue in the SFO2 region and is working with our facility vendor to have this corrected as soon as possible." #digitalocean
Show threadJeff Epler🦉Apr 12, 2017
@Daenyth my #digitalocean SFO2 instance came up something like 14 hours after things started going wrong, and then because of my own self-maintained DNS problems I still had to bounce a couple more systems before things went back to normal, and I still need to figure out why my self-administered secondary DNS stopped serving records during the time the primary was down.
Show threadMorgan Davis
@jepler @Daenyth It was not a fun day for SFO2 droplets.
Apr 12, 2017 at 2:08amWeb