Google Cloud Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Google Cloud Issues Reports

Latest outage, problems and issue reports in social media:

• 
  teo (@teodorio) reported 51 seconds ago

  @googlecloud it's a P0 on chrome while having Google Meets open your Query UI does not allow any typing. It's a web UI issue so I suggest you mark it as a bug and move it to the frontend team

• 
  abzal gylymbai (@abzalgylymbai) reported 3 minutes ago

  @googlecloud Recurring unexplained charges (~$83, repeating) on my Google Cloud Billing account despite no active projects showing in Console. Already paid multiple times, keeps reappearing. No response from support for days. Billing ID: 01B3C0-1899D2-F0DA8D.

• 
  Arpit Rajpurohit (@arpraj) reported 4 minutes ago

  @googlecloud Guys this is not been solved yet. It has been the worst experience working with your team

• 
  zbt3sup (@zbt3sup1) reported 7 minutes ago

  @intel @googlecloud Bad choice for your engineers

• 
  Henry Lorenzo (@ilhanerdal_) reported 9 minutes ago

  $GOOGL’s Q2 results produced the most profitable quarter in Alphabet’s history: $112.1B in net income—the company’s first quarter above $100B. But that headline needs context. Most of it came from unrealized gains in Alphabet’s equity portfolio, likely driven largely by its stakes in $SPCX and Anthropic. At the same time, $44.9B in CapEx pushed quarterly free cash flow to negative $5.9B. That is what the market focused on. The number I keep coming back to is Google Cloud’s $514B backlog—nearly 5x what it was a year ago. Demand is not the problem. Capacity is. Google still does not have enough compute and data-center capacity to serve that demand, so I believe management is right to keep investing aggressively. The buildout is pressuring free cash flow today. But if it unlocks even a meaningful portion of that backlog, investors may eventually view this spending very differently. The real question is not whether demand exists. It is how quickly $GOOGL can build enough capacity to capture it. #GOOGL #GoogleCloud #AI

• 
  Mariz (@MarizMelo) reported 10 minutes ago

  @googlecloud forcing users into prepaid sucks. Maybe time to look for alternatives to host your #AI product :/

• 
  身是业的根 (@muyang14756529) reported 16 minutes ago

  @googlecloud The Trust & Safety team is completely cold & irresponsible. They just sent a generic 48-72hr weekend template while knowing my countdown is in HOURS. Absolute zero empathy for small businesses. Help Ticket 2XWJSBKNPMM7QOD3U5KVHZU5WI! #GoogleCloud @GoogleCloud

• 
  KleurigDrieluik (@KleurigD) reported 19 minutes ago

  @GooglePlayBiz he Google play, why is Developer Support ignoring support questions with detailed technical analysis from @googlecloud Gemini and @Firebase support?

• 
  63green (@63green) reported 22 minutes ago

  Another day, another need to 'unsubscribe' from @googlecloud marketing emails. This is why I've fully removed myself from all things @Google - they treat everyone with complete contempt, refuse to honor preferences, and are happy to **** you as a customer at every opportunity.

• 
  Adel Bucetta (@adelbucetta) reported 22 minutes ago

  @googlecloud the honest answer is that many companies think they can just bolt ai on top of their existing data mess, but it's not that simple. you need a robust data strategy from day one to support autonomous agents.

• 
  Andrea Volpini (@cyberandy) reported 23 minutes ago

  @VeryWellVersed @googlecloud Something similar happened to me last week. The request came from an Internet Service Provider in Romania that hacked into our Vertex AI account, and burned $13k of tokens for generating videos using Veo 3.1.

• 
  M (@mdw864) reported 24 minutes ago

  @googlecloud @GoogleCloudTech do you accommodate customers with disabilities? In case we have problems and need to speak to you? I think I may have to switch to you because @awscloud has not provided accommodations for people with disabilities.

• 
  Jakob (@jakob_btc) reported 25 minutes ago

  The privacy paradox of the AI era is that utility requires intimacy. To make an AI agent genuinely useful, you have to give it access to proprietary context: internal knowledge, emails, code, workflows. Generic data does not get you very far. So what happens to privacy when hiding the data is no longer realistic? My view is that the privacy stack is shifting from data redaction to verifiable processing. Three major shifts happening right now: 1. Confidential AI at Scale: We’re moving past relying on corporate promises. @googlecloud recently rolled out Confidential G4 VMs with NVIDIA Blackwell GPUs. The tech is mainstreaming. With hardware-based Trusted Execution Environments, your knowledge base is encrypted in memory while the model processes it. Even the cloud provider can’t peek 2. End-to-End Prompt Encryption: Infinite AI memory is a privacy nightmare. The next wave of tools will use localized, cryptographic session gates. Google again recently open-sourced Prompt Encryption SDKs to tackle this problem, establishing a secure channel that keeps data encrypted from the client all the way until it hits the secure chip, before the session vanishes 3. Local Middleware & Edge SLMs: Instead of sending everything blindly to centralized frontier models, enterprises are routing data through local semantic firewalls The bottom line: You will feed AI everything it needs to know, but the tech stack will make sure the vendor never actually "learns" or retains a single byte of it.

• 
  Luca 🦖 | #fncforever | 🍉 (@sinister_in) reported 25 minutes ago

  @sammathews @googlecloud The worst possible time line

• 
  Garrett Smith (@gsmithw91) reported 26 minutes ago

  @googlecloud @ThomasOrTK What is the magic number of follow ups and requests someone has to do to get resolution for billing support? Its beyond 30 at this point.