Same issue here for the past few days, glad to see it's not just me but
it'd be nice to hear some acknowledgement from Google and hopefully it
can be fixed on the backend because setting this all up again due to a
bad update would be a terrible user ...
