Dear colleagues, With less than 100 IPv4 /22-equivalents remaining in our pool, we expect that we will announce run-out early next week. Ahead of this, we have published a table and graph which will show the number of /24 requests when the waiting list becomes active (both the table/graph will obviously remain at zero until then). You can find this here: https://www.ripe.net/manage-ips-and-asns/ipv4/ipv4-waiting-list Because of the way we have implemented the waiting list, there is a small chance that some people will know we have reached IPv4 run-out before we do. While this is not overly important, to avoid confusion we thought it might be worth explaining why this could happen. To ensure fairness, each request effectively "reserves" a /22 until the allocation can be made. Depending on the rate of IPv4 requests, it's possible that we might end a workday with only a handful of /22s remaining in our pool. If the number of requests we receive outside of office hours exceeds the number of remaining allocations, any further requests will be added to the waiting list automatically. This will generate an email notification for the LIR that submitted the request - thereby informing them that we are out of /22 allocations. Of course, we would not have "officially" run out, as we would still have some (at least one) /22s waiting to be allocated when we returned to the office. We will make our announcement only once we have made the final /22 allocation. Kind regards, Nikolas Pediaditis Registration Services and Policy Development Manager RIPE NCC