Nebius’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (hop 1, posted +1 h 30 min vs Google Cloud’s own post)
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
What changed
Struck in red is what Nebius removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Connectivity issues for newly created worker nodes
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-09-01 16:11 UTC
AddedResolved time#5
Before: not present
After: 2026-09-01 16:26 UTC
AddedAffected components#6
Before: not present
After: EU-NORTH1 - Managed Service for Kubernetes®, EU-NORTH1 - Virtual Private Cloud (Networking), Managed Service for Kubernetes®, US-CENTRAL1 - Managed Service for Kubernetes®, US-CENTRAL1 - Virtual Private Cloud (Networking), Virtual Private Cloud (Networking)
AddedUpdateidentified#7
Before: not present
After: Worker nodes of Managed Service for Kubernetes clusters created after 15:13 CET Sep 1 2026 could experience problems connecting to/from other nodes in the same cluster. The root cause is understood and mitigation is underway.
AddedUpdatemonitoring#8
Before: not present
After: The issue may have caused consequential impact to VPC functionality of VMs that are not Managed Service for Kubernetes worker nodes.
AddedUpdatemonitoring#9
Before: not present
After: We are continuing to monitor for any further issues.