Google Cloud Storage throwing a large number of 503's

#1

Post by ricberw » Thu, Jul 06, 2017, 10:55 PM UTC

Seems that GCS is throwing a boatload of 503's and is sometimes taking >10 seconds to respond. Anyone else seeing this?

Google has denied anything is wrong, but I'm seeing a lot of images not loading on other sites that I know use GCS as well...

Re: Google Cloud Storage throwing a large number of 503's

#2

Post by priyadarshy » Thu, Jul 06, 2017, 10:58 PM UTC

I'm unable to OAuth in to a variety of Google Services e.g. Asana, FullStory.

At work, our applications using Google Calendar V3 is seeing a ton of 503s in all environments (dev, staging and production).

Re: Google Cloud Storage throwing a large number of 503's

#3

Post by ricberw » Thu, Jul 06, 2017, 11:06 PM UTC

priyadarshy wrote: post #2

I'm unable to OAuth in to a variety of Google Services e.g. Asana, FullStory. At work, our applications using Google Calendar V3 is seeing a ton of 503s in all environments (dev, staging and production).

Yep - we're starting to see proof from a lot of different sides that Google is having a rather major issue. Now to hope they find the culprit and resolve it quickly :)

Re: Google Cloud Storage throwing a large number of 503's

#4

Post by zackify » Fri, Jul 07, 2017, 12:09 AM UTC

How is this not getting more notice? It must be isolated to only a few of us...

Re: Google Cloud Storage throwing a large number of 503's

#5

Post by jhgg » Fri, Jul 07, 2017, 12:20 AM UTC

It's happening to us too. Firebase status page was updated, but it looks like GCS in general was not.

Re: Google Cloud Storage throwing a large number of 503's

#6

Post by P3R3 » Fri, Jul 07, 2017, 12:37 AM UTC

zackify wrote: post #4

How is this not getting more notice? It must be isolated to only a few of us...

I guess it shows how widespread GCS usage is among enterprises

Re: Google Cloud Storage throwing a large number of 503's

#7

Post by alpb » Fri, Jul 07, 2017, 1:17 AM UTC

This is now reported at https://status.cloud.google.com/incident/storage/17002.

Re: Google Cloud Storage throwing a large number of 503's

#8

Post by gkop » Fri, Jul 07, 2017, 2:41 AM UTC

alpb wrote: post #7

This is now reported at https://status.cloud.google.com/incident/storage/17002 .

Thanks. Our monitoring says it started at 4pm pacific. So the incident lasted 2.5 hours.