Live / Solace Cloud / Incident
Solace Cloud: GKE West-Europe 2 Zone B degraded
Solace Cloud · solace.cloudMinor incidentResolved2026-10-21 01:19 UTC
Public — what happened
Summary
Solace Cloud said that Google Cloud's GKE europe-west2-b zone in the London region was degraded, starting 2026-10-20 at 07:12 UTC, and that its engineering team was watching recovery and any effect on its services. At 12:49 UTC the company said the affected zone's nodes had been restored and all impacted Solace brokers had fully recovered and were running normally. Solace Cloud said it would keep monitoring for stability, and the incident was marked resolved at 01:19 on 2026-10-21.
Affected
GKE - Europe-West2 (London)
Timeline
- Started — 2026-10-20 07:12 UTC
- Identified — 2026-10-20 07:12 UTC
- Monitoring — 2026-10-20 12:49 UTC
- Resolved — 2026-10-21 01:19 UTC · 18h 07m 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 Solace Cloud 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 Solace Cloud: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Solace Cloud report →
More from Solace Cloud
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.