Is Google Cloud down right now?

No. Our checks are finding no problems with Google Cloud right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Google Cloud continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, can't connect, API errors, 5xx error pages, slow or laggy, no response / timing out, DNS / site unreachable and backup not completing. Those are the options the report button offers for Google Cloud, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Google Cloud specifically, Google Cloud is regional and zonal, so most incidents stay inside a single zone while everything else runs normally. Identity and the console are global, though, so an IAM problem reaches every project at once no matter where your resources live. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Google Cloud, run the same call against a resource in another region and check whether the console itself loads. One region failing is theirs and scoped; everything failing including sign-in points at identity or your own credentials. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Google Cloud's side. Specifically: read Personalized Service Health in the console rather than the public dashboard, because it knows which projects and regions you use. Avoid changing IAM policy during an authentication incident, since you cannot tell whether the change applied. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Google Cloud publishes a machine-readable status feed, so our first check reads it directly and reports what Google Cloud itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.cloud.google.com, and it is linked further up this page. That is Google Cloud's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Google Cloud or cloud.google.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Google Cloud's own support, not us.