Nebius incident

Unable to allocate new public IPv4 addresses in eu-north1

Minor Resolved View vendor source →

Nebius experienced a minor incident on June 2, 2026 affecting Virtual Private Cloud (Networking), lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Jun 02, 2026, 10:53 AM UTC
Resolved
Jun 03, 2026, 11:06 AM UTC
Duration
1d
Detected by Pingoru
Jun 02, 2026, 10:53 AM UTC

Affected components

Virtual Private Cloud (Networking)

Update timeline

  1. investigating Jun 02, 2026, 10:53 AM UTC

    We are investigating an issue in eu-north1 affecting Virtual Private Cloud (Networking). New public IPv4 addresses cannot currently be allocated to workloads. Customers may be unable to assign a public IP when creating or modifying resources — for example, attaching a public IP to a virtual machine or load balancer in this region. Resources that already have a public IPv4 address assigned are not affected and continue to operate normally. We will provide an update as we learn more.

  2. identified Jun 02, 2026, 11:52 AM UTC

    We have identified the cause: the pool of available public IPv4 addresses in eu-north1 is currently exhausted, which is why new public IPv4 addresses cannot be allocated to workloads. We are reclaiming and reallocating addresses to restore allocation capacity. Workloads that already have a public IPv4 address assigned remain unaffected. We will provide a further update once new allocations are succeeding.

  3. monitoring Jun 02, 2026, 12:36 PM UTC

    Public IPv4 address capacity has been restored in eu-north1, and new public IPv4 addresses can be allocated to workloads again. We are monitoring the service to confirm full recovery before resolving this incident.

  4. resolved Jun 03, 2026, 11:06 AM UTC

    This incident has been resolved.