On June 12, 2025, Google Cloud’s central sign-in service — Identity and Access Management (IAM) — stopped issuing the tokens that every Google Cloud product needs to operate. This single failure immediately disabled a long list of Google services worldwide.
Disrupted AI Services Used in Healthcare
Google confirmed that four of its cloud-based products — Vertex AI Online Prediction, Dialogflow CX, Agent Assist, and Contact Center AI — were temporarily unavailable during the outage.
Vertex AI, a machine learning platform adopted by hospitals, research institutes, digital health startups, and pharmaceutical firms, underpins diagnostic decision support systems, generates personalized treatment recommendations from patient data, powers risk scoring models, and streamlines a range of operational workflows.
Dialogflow CX and Agent Assist, likewise growing in healthcare use, drive both clinical support functions and day-to-day administrative tasks.
Contact Center AI processes scheduling, triage, billing inquiries, and other virtual “front door” services.
Cloudflare Hit
Cloudflare keeps the configuration data for its Workers KV platform inside Google Cloud. Once IAM was down, Workers KV lost access to that data and went offline at 18:19 UTC. Any Cloudflare feature that depends on KV — Access, WARP, Durable Objects, Turnstile, and parts of the dashboard—also stalled. Cloudflare’s own status page identified “a third party dependency” as the cause.
Because many popular apps rely on either Google Cloud or Cloudflare, outages showed up almost at once on monitoring sites. Spotify, Discord, Snapchat, Twitch, Shopify, and several others reported slowdowns or errors, while Amazon Web Services saw a brief spike in customer complaints because some of its users route traffic through Cloudflare.
What this means for leadership
A service advertised as “globally replicated” still failed because it relied on an unseen external system.
Modern cloud identity layers have become a choke point. When they fail, multiple vendors go down together.
Traditional “multi cloud” strategies offer limited protection unless you also verify that vendors do not share the same upstream dependencies.
Next actions
Ask suppliers for clear maps of where their control plane components run.
Require design changes (credential caching, local fallback modes) that let critical workloads keep running if an external identity service stalls.
Include “identity layer outage” scenarios in resilience drills and board level risk reviews.
Taken together, these steps reduce both the likelihood and the business impact of the next cross provider disruption.
Rate this article
Recommended posts
Our Clients' Feedback













We have been working for over 10 years and they have become our long-term technology partner. Any software development, programming, or design needs we have had, Belitsoft company has always been able to handle this for us.
Founder from ZensAI (Microsoft)/ formerly Elearningforce