I also have problems with firebase virtual device testing service and google play console api sice yesterday. I keep getting 500 as response, dont know if related though.
The root of this is definitely GCS. We noticed some keys in a GCS bucket go inaccessible since like 19:15-19:20ish PDT, and then we noticed increased timeouts/503's ramping up at 19:30 and plateauing at 19:45. But error rate for us seems to have gone back to nominal levels since 20:10... but the keys that originally went unavailable are still returning 503's.
If Google's GCP marketing material is to be believed, you are truly on their infrastructure on GCP, so if GCP is having issues so are Google's main services.
YouTube ain't a Gsuite service with SLA. So this is much more likely to have a public report. Whether it's detailed or not is another thing.
Also it's probably due to the underlying GAE or GCS issue is my guess.
"
Elevated error rate with Google App Engine Blobstore API and App Engine Version Deployment
Incident began at 2019-03-12 19:49 (all times are US/Pacific).
Mitigation work is currently underway by our Engineering Team. We will provide another status update by Tuesday, 2019-03-12 20:45 US/Pacific with current details.
"
These are the not that well designed scenarios, when the status pages are hosted on the very same infrastructure that suffers an outage. This is a common pattern across cloud providers I have seen happen.
It's more likely that your browser just isn't loading the CSS background images for some reason. If you inspect the circles, do you still see the background-image declaration?
Honestly, it's not hard. Just don't design everything around color. On ticket to ride, the grey lines ones have a dot or shape in the middle whereas the black ones do not. I can see that dot, but it's small. If it was larger then the problem would be solved.
Heck, I'm not colorblind and I had trouble seeing the difference between "service disruption" and "service outage" at first in the legend at the bottom of the page.
It wasn't until I zoomed in on them that I could see that one was orange and the other red. Once I saw them zoomed, I could then identify which was which at normal size on the status part of the page.
BTW, the orange circle is actually a span whose class is "aad-yellow-circle", and whose CSS loads the colored circle from the file yellow_circle.png.
This suggests that at one time they intended it to be a yellow circle, not an orange circle [1]. I wonder why they switched from yellow to orange?
[1] Actually, RGB to name sites suggest that it is neon carrot.
If the user had e.g. red/green colorblindness, that wouldn't help. Google's made a nice tradeoff for this application, though, and used differently-shaped icons (checkmark vs. exclamation point) as well.
Edit: looks like the icons are served as images. Google should probably consider making them text icons instead to mitigate loading problems.
May I ask - why the downvote? I know it was a blip, but still, a reminder for a moment that most of life relies on them. And some of my data is not replicated else ware... that is changing.
I just emailed some folks images. Got a few warnings of something going wrong, so I then checked in my outbox. It showed that the images went, but there was a message that the "virus scanners were down, download at your own risk." Or some such. Seems to be back to working now, so I just assumed it was a time delay.
Edit: Just saw it again. Full message is:
Gmail virus scanners are temporarily unavailable – The attached files haven't been scanned for viruses. Download these files at your own risk.
First time I've seen something like this, actually kind of glad they had this failure case coded for. :)
Because it's largely unnecessary. If people were more willing to push for decentralized alternatives then world-wide outages would be a thing of the past, short of the entire internet itself going down in which case you probably have bigger problems to worry about that loss of access to [x].
In my opinion it's not a question of if, but when we'll have our first disgruntled higher level employee manage to effectively destroy massive amounts of information and redundancies. As people become more and more dependent upon centralized services, the impact of this first 'digital nuke' will only continue to grow.
In some ways the internet feels like we have created a machine that can take us anywhere in the universe, but we've decided that instead we'll use it to take us strictly between New York and LA - occasionally with some 'wild' idea to take us to London.
Maybe think of it more as an opportunity to remember how we've let ourselves be lulled by this behemoth. Google itself is pretty much a spof for most of the world. If Google is down, so is business.
Of course, the report afterwards will be very interesting, while we pick apart the reasons on what and how it failed.
Probably just a Google employee waking up and becoming sentient again, running around pulling out as many cables as possible to save humanity. It should be up and running again when they catch and reset him.
