Google Cloud Outage Disrupts AI Services and Exposes Cloud Dependency Risks

Cloud collapse: Replit and LlamaIndex knocked offline by Google Cloud identity outage

Join the event trusted by enterprise leaders for nearly two decades. VB Transform brings together the people building real enterprise AI strategy. Learn more Days after OpenAI and Google Cloud announced a partnership to support the growing use of generative AI platforms, much of the AI-powered web and tools went down due to an outage of the leading cloud providers. Google Cloud Service Platform (GCP) and some Cloudflare services began experiencing issues around 10:00 a.m. PT, affecting several AI development tools and data storage services, including ChatGPT and Claude, as well as a variety of other AI platforms. A GCP spokesperson confirmed the outage to VentureBeat, urging users to check its public status dashboard. GCP said affected services include API Gateway, Agent Assist, Cloud Data Fusion, Contact Center AI Platform, Google App Engine, Google BigQuery, Google Cloud Storage, Identity Platform, Speech-to-Text, Text-to-Speech and Vertex AI Search, among other tools. Google's mobile development platform, Firebase, also went down. VentureBeat staffers had trouble accessing Google Meet, but other Google services on Workspace remained online. A Cloudflare spokesperson told VentureBeat only "a limited number of services at Cloudflare use Google Cloud and were impacted. We expect them to come back shortly. The core Cloudflare services were not impacted." Despite media reports and user-provided feedback on Down Detector, AWS stated that its service remains up, including AI platforms such as Bedrock and Sagemaker. OpenAI acknowledged some users had issues logging into their platforms but have since resolved the problem. Anthropic noted on its status page that Claude experienced "elevated error rates on the API, console and Claude AI." Developer tools like LlamaIndex's LlamaCloud, Weights & Biases, Windsurf, Supabase, and Replit reported issues. Other platforms like Character AI also announced they were affected. In addition to AI tools, other websites and internet services, such as Spotify and Discord, also reportedly went down. Needing more cloud In many ways, the outage highlights the challenges of relying on a single cloud service or database provider and the risks associated with an interconnected internet. If one of your cloud services goes down, it could impact some users who have their log-in or data stream hosted there. Google Cloud has been gradually wresting market leadership in enterprise AI from its competitors, thanks to the large number of developer and database tools it has begun offering organizations. On the other hand, Cloudflare has been partnering with companies like Hugging Face to deploy AI apps faster. First reported by Reuters, Google and OpenAI have struck a deal that will allow OpenAI to utilize Google Cloud to meet the growing demand on its platform. But that's not to say Google or Cloudflare may lose an edge among enterprise AI users who depend on consistent uptime. While the company continues to investigate the cause of the outage, businesses often have, and should have, redundancies in case their provider goes down. Outages happen, and they happen far too frequently. The last massive outage happened around the same time last year, in July, when CrowdStrike accidentally triggered outages that impacted Microsoft Windows users. In typical fashion, many people saw the outages as an opportunity for comedy, or at least to catch up on tasks they'd been putting off.

When Google Cloud Paused the Internet | AIM

Platforms such as Spotify, Replit, Discord, Claude, Snapchat, Twitch, Cloudflare, and other services that use the Google Cloud faced outages. Google Cloud Platform (GCP), which offers a wide range of cloud services for various applications worldwide, experienced downtime on Thursday, the company reported. In a status report, Google said that "multiple GCP products are experiencing service issues" across several locations worldwide. The incident began at 10:51 am (PT) on Thursday and was resolved hours later, at 6:18 pm (PT), which is 11:21 am IST and 6:48 am IST, respectively. Platforms such as Spotify, Replit, Discord, Claude, Snapchat, Twitch, Cloudflare, and other services that use the Google Cloud faced outages. Besides, many of Google's products, like Google Meet, Drive, Chat, and Gmail, that rely on GCP were said to be affected. These products use Google Cloud's infrastructure for services such as storage, computing, networking, data processing, and more. Amjad Masad, CEO of Replit, said on X, "Google Cloud is having an outage and that's taking Replit down." Anthropic, the company that develops the Claude family of AI models, stated on a status page that it has identified several issues with its products due to the outage affecting GCP. The company also mentioned that image and file uploads via the API and the Claude web app were unavailable due to the GCP issue. GitHub, the code hosting platform that also provides AI-assisted programming capabilities with GitHub Copilot, said in an incident report that underlying AI models like Claude and Google Gemini were facing issues. "Copilot is experiencing degraded performance," said GitHub. However, all of the above services were restored to normalcy after a few hours. Cloudflare was one of the platforms most impacted by GCP's outage. The company provides internet security services to some of the leading websites worldwide, with around 19.3 million websites using its services. "The outage lasted 2 hours and 28 minutes, and globally impacted all Cloudflare customers using the affected services," said the company in a blog post. It added that the outage was due to a failure in an underlying storage infrastructure, a part of which runs on a third-party cloud provider. A spokesperson from Cloudflare told CNBC that its issue stemmed from Google's Cloud services as well. "A limited number of services at Cloudflare use Google Cloud and were impacted. We expect them to come back shortly. The core Cloudflare services were not impacted," said the spokesperson. The company's stock also fell by 5% on Thursday. "While the proximate cause (or trigger) for this outage was a third-party vendor failure, we are ultimately responsible for our chosen dependencies and how we choose to architect around them," said the company. Cloudflare's Workers KV service -- a distributed, serverless key-value store designed for use with Cloudflare's Workers, the company's serverless computing platform -- was significantly affected. "Workers KV saw 90.22% of requests failing: any key-value pair not cached and that required to retrieve the value from Workers KV's origin storage backends resulted in failed requests," said the company. Several Cloudflare products, such as Access, Gateway, WARP client, and Dashboard, were also impacted. These products are a key part of the overall infrastructure that Cloudflare provides to its customers. For instance, Access is a service that users Workers KV to store application and policy configuration along with user identity information. During this incident, Cloudflare said, Access failed 100% of identity-based logins for all application types. The company claims that no data was lost as a result of the incident. Several reports emerged that GCP's counterparts, Microsoft's Azure and Amazon's Web Services, also faced outages, based on information from Down Detector, a website that checks what websites are currently facing downtime. However, neither Microsoft nor AWS have officially confirmed this. Gergely Orosz, author of The Pragmatic Engineer, said this is likely a misunderstanding of how DownDetector checks for outages. "It cannot differentiate between 'Azure is having issues' vs 'some sites hosted on Azure are having issues' (that can be the case due to, eg, CF (Cloudflare))," said Orosz in a post on X. According to Tom's Guide, an AWS spokesperson has confirmed that they are not experiencing any service disruptions and stated that "Down Detector does not accurately reflect AWS issues." Overall, Thursday's events were a stark reminder of how relying on a single cloud service provider can bring down some of the most popular apps on the internet. "We build all this powerful tech, then that one Google Cloud outage takes it all offline," said a user on X. "Feels like the universe saying: 'Take a break. Go outside. You're not in control anyway'," they added.

Identity and access management failure in Google Cloud causes widespread internet service disruptions - SiliconANGLE

Identity and access management failure in Google Cloud causes widespread internet service disruptions An identity and access management failure within Google Cloud earlier today caused widespread service disruptions across a range of internet services, including portions of Cloudflare Inc., Google Workspace apps and third-party platforms reliant on Google infrastructure. The incident began late Wednesday morning PDT and was traced to a misconfiguration within Google Cloud's IAM systems. The disruption triggered outages in critical cloud components such as App Engine, Firestore, Cloud SQL, BigQuery and Memorystore. As a result, numerous services that depend on these components either failed or became intermittently available. Among the first to report issues was Cloudflare, which confirmed that some of its services, including Workers KV, Access authentication, Workers AI, Stream and parts of the dashboard, were affected due to their dependency on Google Cloud. "This is a Google Cloud outage," a spokesperson for Cloudflare told CRN. "A limited number of services at Cloudflare use Google Cloud and were impacted." The outage was widely felt. Users of Google Workspace experienced failures across Gmail, Drive, Docs, Calendar, Meet and Chat, while Google Home and Nest devices also suffered connectivity problems. Google's Gemini and search-related services, including Lens and Discover, were also intermittently down. On social media, users reported that voice search and assistant functions were nonresponsive. Companies that rely on Google services were also affected by the outage. Some of the companies affected included Spotify Technology Inc., Discord Inc., Snap Inc., Shopify Inc., Replit Inc., Anthropic PBC, Character Technologies Inc., fuboTV Inc. and United Parcel Service Inc., many of which experienced partial downtime or degraded performance. In probably one of the most visited pages on the internet today, the Google Cloud status page gave regular updates, starting from 11:46 a.m. PDT. As of the time of writing, the status page stated that most Google Cloud products are fully recovered, but added that "there is some residual impact for the products currently marked as affected on the dashboard." According to Downdetector, a site that tracks outages, reports from affected users peaked at around 2:30 p.m. EDT, but there were still a few people reporting issues as of 5:30 p.m. EDT. Some reports today also suggested at the Amazon Web Services Inc. may have also suffered an outage, but there is no evidence that AWS, other than maybe a few minor product issues, were affected by the Google outage. One exception, though, wasn't directly AWS-related, but a service owned by Amazon.com Inc. -- the streaming service Twitch, which may have been affected by network-level interdependencies, such as DNS, authentication or content delivery network provision.

Google Cloud Outage: Technical Wake-Up Call for Our Cloud-Dependent World?

The recent Google Cloud Platform (GCP) outage sent shockwaves through the digital ecosystem, disrupting services from Gmail and YouTube to Spotify, Discord, and even critical healthcare applications powered by Vertex AI. This incident, rooted in a failure of Google's Identity and Access Management (IAM) system, exposed the fragility of our increasingly cloud-dependent infrastructure. Beyond the immediate inconvenience, it raises profound technical and systemic questions about resilience, redundancy, and the risks of centralized cloud architectures. This editorial dissects the outage from a technical perspective and argues for a reevaluation of our reliance on a handful of hyperscale cloud providers. The outage started when Google's IAM service, a critical component responsible for authenticating users and enforcing access policies, failed. IAM is the gatekeeper of cloud services, ensuring that only authorized entities can access resources like storage, compute, or APIs. According to posts on X and Google's service health dashboard, the issue cascaded across GCP's infrastructure, affecting services like Cloud Firestore, Cloud Run, and BigQuery, as well as third-party platforms like Cloudflare, which relies on GCP for certain components. The root cause, as Google vaguely stated, was identified and mitigated, but no detailed technical explanation has been provided. Speculation on X points to a potential misconfiguration or failure in Google's "Chemist" service, a lesser-known system possibly tied to IAM policy enforcement. Whatever the trigger, the outage lasted over seven hours, with residual impacts lingering for some services. Downdetector reported over 14,000 incidents at its peak, underscoring the global scale of the disruption. From a technical standpoint, IAM failures are particularly insidious because they disrupt the trust layer that underpins cloud operations. Without functional authentication, services cannot verify user identities or access rights, effectively locking out applications and users. This is similar to a bank vault refusing to open because the security system has crashed, not because the vault is broken, but because the system validating the key is offline. The cascading effect was amplified by GCP's tightly integrated architecture, where IAM is a dependency for nearly every service.

Google Cloud outage: What happened and why it's scary

One cloud error can disrupt businesses, hospitals, and the internet around the world. On June 12, 2025, a major Google Cloud Platform (GCP) outage disrupted global digital services, exposing the fragility of cloud-dependent systems. The world didn't go offline but it certainly stumbled. In a world tethered to the cloud, Google's massive outage felt like the digital equivalent of a citywide power cut, sudden, sprawling, and deeply unsettling. Also read: Cybersecurity platform Crowdstrike down worldwide, many users logged out of systems In the early hours of June 12th, Google Cloud services faltered, affecting Google's own tools, Gmail, Google Drive, Google Meet, Google Maps, and third-party platforms like Spotify, Discord, Snapchat, Shopify, Twitch, and Character.AI. For 8 hours, the internet lost a piece of its spine all due to a failure in Google Cloud's identity and Access management system (IAM). The outage impacted users worldwide, with over 13,000 reports on Downdetector in the U.S. alone and disruptions in cities like Mumbai and Delhi. Critical GCP services, including Cloud Storage, BigQuery, App Engine, and Vertex AI, were hit, alongside Google Workspace tools vital for businesses. Cloudflare's analytics and key-value services also suffered due to Google Cloud dependencies. In healthcare, AI tools like Vertex AI Online Prediction and Dialogflow CX, used for patient care, were down for nearly four hours. Google identified the issue early on, applied fixes, and restored most services within four hours, with full recovery soon after. A detailed post-mortem was promised to address the outage's root cause. This wasn't just a Google problem. It was a wake-up call, a glimpse at how delicate our digital dependencies have become. The issue wasn't malicious, but the impact almost felt like a cyberattack, hospitals lost access to AI diagnostic tools, businesses hemorrhaged productivity, online services blinked out in major metros like Delhi and Mumbai. The consequences were real, and they were global. Also read: X outage: Hacker group claims cyberattack, Musk hints at coordinated nation-level attack Behind it all is a sobering reality: today's cloud architecture often relies on a handful of centralized pillars. IAM, meant to keep services secure, became the single point of failure. If attackers were to target similar chokepoints, the chaos wouldn't just be accidental. It would be weaponized. From Spotify to Shopify, the outage showed how deeply interwoven services have become. The digital supply chain is brittle, and when one provider falters, the ripple effects can be seismic. Organizations have been told to "go cloud" for years. Few were prepared for the cloud to go down. For Google Cloud, the timing couldn't be worse. With $43.2 billion in revenue last year and a 31% growth rate, GCP has been gunning for AWS and Azure's market share. But trust is currency in the cloud world, and repeated outages, like the one in May 2024 that deleted an entire Australian client's environment, chip away at it. There's also a communications lesson here. Google acted quickly, services were mostly back up in four hours, but its silence during those crucial moments left a vacuum. In the age of disinformation, silence can be as damaging as failure. The public deserves clarity, not ambiguity. The financial losses from this blackout will likely stretch into the millions. But the long-term consequences could be even costlier. Cloud providers may soon face stricter regulatory oversight, with governments demanding uptime guarantees, transparent post-mortems, and legal accountability, especially for healthcare, finance, and defense sectors. Meanwhile, businesses will look inward. Expect a renewed interest in multi-cloud strategies, hybrid environments, and even old-school offline backups. Uptime will no longer be a selling point. It will be a baseline expectation, legally binding and contractually enforced. This wasn't just a bad day for Google Cloud. It was a glimpse into a more fragile digital future. As AI, remote work, telemedicine, and critical infrastructure all become cloud-native, resilience isn't optional anymore. The June 2025 outage was a failure of a system built for trust. Rebuilding that trust will require more than a post-mortem. It will take re-engineering, rethinking, and rebalancing our entire relationship with the cloud. Because if the cloud is the new electricity then we need to start treating outages like blackouts, not bugs.