Google Workspace Studio on the web was unreachable for some of you for 26 minutes on 25 September 2026. Google's own status page confirms the fault sat on its side, triggered by an elevated error rate its engineers were already mitigating.
Started
16:29 UTC
Duration
Lasted 26m
Source
IsDown
Next time
Google Workspace is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
Google logged a single incident starting at 16:29 UTC, titled "Mitigating elevated error rate with Google Workspace Studio web." The one update posted gave the symptom plainly: an endless loading screen when attempting to access Google Workspace Studio on the web. Google offered no workaround, writing "Workaround: None at this time", and gave no ETA for mitigation beyond promising more information by 10:30 PDT that Friday. No components are listed as affected in Google's own breakdown, and no further updates were filed after the opening one. The incident lasted 26 minutes in total, according to Google's record, and was not flagged as still ongoing. No user reports came in during this window, so the only account of what happened is Google's single filing. That filing carries real weight, since it is the sole source here and there is nothing to cross-check it against. Over the past 90 days Google has logged 5 incidents on this service, with a median duration of 3 hours 28 minutes, which makes this a short one by that yardstick. Across all time, Google has recorded 189 incidents here, averaging 3.3 a month. Google has not published a post-mortem explaining the root cause of the elevated error rate, so why it happened is not on the record.
Learning
UptimeRobot's own 30 day checks on Google Workspace recorded 2 incidents, both resolved, with a median duration of 25 hours 28 minutes, a far longer figure than the 26 minutes Google logged for this one. That gap is not a contradiction. External probes test whether an endpoint responds at all, while an endless loading screen inside Google Workspace Studio can leave the front door open while the page behind it never finishes loading. A health check hitting the right URL and getting a 200 response has no way to see a spinner that never stops. This is the shape of failure to watch for in your own product too: the server answers, the application does not. If your team relies only on checks against your own endpoints, you would have had no signal that the problem sat upstream at Google rather than in your own code. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
