Rewindex

CompaniesNebiusIncidents

Nebius: Connectivity issues for newly created worker nodes

MajorStatus: resolvedStarted Resolved (15 min)4 updatesstspg.io (opens in new tab)
Part of an outage event

Google Cloud us-central1 outage, Sep 1, 2026 · 47 vendors, 54 incidents

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)

Swipe sideways to see the whole diagram.

blamed GitHubblamed Twiliosame windowGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed Google CloudPinecone, Elastic Cloud, FullStory +51 to 4 hours later6 vendors, 6 blamed Google CloudApollo GraphQL, Temporal Cloud,Clerk +3GitHubposted +18 min, did not name GoogleCloudBolt.new+24 minTwilioposted +1 h 42 min, did not nameGoogle CloudGorgias, Iterable+2 h 23 min to +2 h 37 minNebius (this incident)posted +1 h 30 min
blamed GitHubblamed Twiliosame windowGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed GoogleCloudPinecone, Elastic Cloud,FullStory +51 to 4 hours later6 vendors, 6 blamed GoogleCloudApollo GraphQL, TemporalCloud, Clerk +3GitHubposted +18 min, did not nameGoogle CloudBolt.new+24 minTwilioposted +1 h 42 min, did notname Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 minNebius (this incident)posted +1 h 30 min
Nebius is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud us-central1<br/>posted 14:42 UTC"]:::root
  h1["Within an hour<br/>8 vendors, 8 blamed Google Cloud<br/>Pinecone, Elastic Cloud, FullStory +5"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk +3"]:::blames
  root --> h4
  p0["GitHub<br/>posted +18 min, did not name Google Cloud"]:::timing
  root -.-> p0
  k0["Bolt.new<br/>+24 min"]:::hop2
  p0 -->|"blamed GitHub"| k0
  p1["Twilio<br/>posted +1 h 42 min, did not name Google Cloud"]:::timing
  root -.-> p1
  k1["Gorgias, Iterable<br/>+2 h 23 min to +2 h 37 min"]:::hop2
  p1 -->|"blamed Twilio"| k1
  me["Nebius (this incident)<br/>posted +1 h 30 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

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.

Affected components: US-CENTRAL1 - Virtual Private Cloud (Networking)Virtual Private Cloud (Networking)EU-NORTH1 - Virtual Private Cloud (Networking)Virtual Private Cloud (Networking)EU-NORTH1 - Managed Service for Kubernetes®Managed Service for Kubernetes®Managed Service for Kubernetes®US-CENTRAL1 - Managed Service for Kubernetes®

Timeline of updates

  1. identified

    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.

  2. monitoring

    The issue may have caused consequential impact to VPC functionality of VMs that are not Managed Service for Kubernetes worker nodes.

  3. monitoring

    We are continuing to monitor for any further issues.

  4. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Nebius profileRecent Nebius incidentsMarkdownJSON