Live / BlazeMeter / Incident
BlazeMeter: London, Google Location is Experiencing Availability Issues
BlazeMeter · blazemeter.comMinor incidentResolved2026-10-20 16:04 UTC
Public — what happened
Summary
BlazeMeter said a Google Cloud outage was disrupting its London, Google location, starting around 13:39 UTC on 2026-10-20. The company reported that Virtual Services set up in that location would fail to start and have problems during test runs, while performance tests there were working but might have trouble getting their test engines set up. BlazeMeter attributed the problem to Google, advised customers to avoid the location until Google fixed it, and the incident was later marked resolved at 16:04.
Affected
Service Virtualization, Performance Testing
Timeline
- Started — 2026-10-20 13:39 UTC
- Identified — 2026-10-20 13:39 UTC
- Resolved — 2026-10-20 16:04 UTC · 2h 25m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach BlazeMeter against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for BlazeMeter: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the BlazeMeter report →
More from BlazeMeter
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.