On Thursday afternoon, many people with smart home setups connected to Google Home / Nest, or who are trying to stream music on Spotify, are coming up empty. All I’m seeing when I try to open the Spotify website is a message that says “Audiences in Jwt are not allowed,” and opening the app also pops up an error saying it can’t connect. However, previously cached music and podcasts are still playing, and both services are still working for some of our staff members.
We’ve seen issue reports on outage trackers like Downdetector and ThousandEyes, as well as some error messages popping up for other large cloud-based services, like Twitch, Snapchat, and Discord, but so far, it’s not entirely clear what is causing the problem or exactly which platforms are affected.
Google Cloud’s status page initially didn’t list any issues, but has since updated to report “Multiple GCP products are experiencing impact due to Identity and Access Management Service Issue,” along with a list of server locations around the world having problems that began at around 1:51PM ET.
The most recent note from Google, posted at 3:09PM ET, says:
Our engineers are continuing to mitigate the issue and we have confirmation that the issue is recovered in some locations.
We do not have an ETA on full mitigation at this point.
We will provide an update by Thursday, 2025-06-12 12:45 PDT with current details
Google’s update trailed a message from Replit CEO Amjad Masad at 2:34PM ET, when he had already tweeted, “Google cloud is having an outage and that’s taking Replit down. We’re working with them to bring it back up ASAP.”
Another possible cause could be an outage listed by Cloudflare, which provides network infrastructure and content delivery services to a number of online platforms. Noting “Broad Cloudflare service outages,” it’s reporting intermittent failures for the last half hour that certainly could cause global issues for many of the websites and apps we like to use.
We are starting to see services recover. We still expect to see intermittent errors across the impacted services as systems handle retried and caches are filled.
We’ve reached out to both Google and Cloudflare, and will update this article with more information once we have it.
