Unable to allocate new public IPv4 addresses in eu-north1
minor- Started
- Jun 2, 6:53 AM EDT
- Resolved
- Jun 3, 7:06 AM EDT
- Duration
- 24h 13m
Nebius's updates (4)
- investigating · Jun 2, 6:53 AM EDT
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.
- identified · Jun 2, 7:52 AM EDT
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.
- monitoring · Jun 2, 8:36 AM EDT
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.
- resolved · Jun 3, 7:06 AM EDT
This incident has been resolved.
Updates are Nebius's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗