Unable to allocate new public IPv4 addresses in eu-north1
Jun 2, 10:53 UTCJun 3, 11:06 UTC
Duration
24h 13m
Impact
Minor
Root cause
Not disclosed
Nebius, 90 days
22 incidents
Affected
Virtual Private Cloud (Networking)EU-NORTH1 - Virtual Private Cloud (Networking)
Final update
This incident has been resolved.
Timeline
- Resolved · Jun 3, 11:06 UTC
This incident has been resolved.
- Monitoring · Jun 2, 12:36 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.
- Identified · Jun 2, 11:52 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.
- Investigating · Jun 2, 10:53 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.
More from Nebius
Full historyMetrics unavailable in Management Console for Monitoring in eu-west1lasted 11mProblems with power for several dozens of nodeslasted 14h 45mIssues with preempted Managed Kubernetes nodes in all regionslasted 24hInfiniBand connectivity issues for GPU clusters in eu-west2lasted 6h 28mCompute VM creation and Object storage are partial unavailablelasted 9mNetwork issues in eu-west2lasted 3h 12m