Skip to main content
Vendor reliability

Vendor record

GCP Storage

Vendor reports Operational

Checked

Front door check counts and GCP Storage’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We have no front door checks against GCP Storage in the last 30 days. That does not show whether it was reachable.

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every GCP Storage product, region or your app worked.

How we count front door checks

GCP Storage says

Incident posts from GCP Storage’s status page, with its titles, impact levels and times. They say what GCP Storage chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

2

incidents GCP Storage posted, last 180 days

All vendors’ incidents

Most recent records · all dates

  • Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.

    Major

    Started, per GCP Storage

    Closed in our record(1d 5h)

    GCP Storage’s post
  • We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.

    Critical

    Started, per GCP Storage

    Closed in our record(3h 40m)

    GCP Storage’s post
  • We are investigating elevated error rates with multiple products in us-east1

    Major

    Started, per GCP Storage

    Closed in our record(2h 5m)

    GCP Storage’s post
  • Multiple GCP products are experiencing Service issues.

    Critical

    Started, per GCP Storage

    Closed in our record(7h 27m)

    GCP Storage’s post

Your code, your dependencies

See which of your code paths call GCP Storage

Connect GitHub or GitLab to find where your public or private repository uses GCP Storage. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add GCP Storage status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · GCP StorageStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/gcp-storage?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="GCP Storage status badge"></iframe>

Frequently Asked Questions

Is GCP Storage currently down?

GCP Storage's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did GCP Storage last have an outage?

The most recent closed incident record began 8 days ago and spans 1d 5h. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for GCP Storage?

No. CheckUpstream does not run front door checks against GCP Storage. The incident history on this page is what GCP Storage reported, not a measure of how often it was available.

How do I monitor GCP Storage in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track GCP Storage?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.