ITCare’s RIPE /24 Transfer: Zero RIS Peers Next to 321

RIPE Registered ITCare’s /24. The Next /24 Reached 321 Peers; This One Reached Zero.

Why it matters

A Polish /24 changed hands on RIPE NCC’s transfer ledger. At the next RIS snapshot, its exact route reached no full-table peer; the numerically adjacent /24 reached almost all of them. The receipt and the route were telling different stories.

Theo March4 November 2026Reading Time 2 minLast update: 4 November 2026

RIPE records ITCare’s /24 transfer; RIS sees its exact route at zero peers while the separately registered adjacent /24 reaches 321.

Summary

RIPE NCC’s assignment-transfer file records a permanent POLICY move of 91.206.90.0/24 from Hydro Extrusion Poland Sp z o.o. to Pawel Staszewski trading as ITCare on 3 November 2026. Exact RDAP names PL-ITCARE1, ASSIGNED PI, registered at 13:30:34 UTC.
In RIPE RIS’s 4 November 00:00 UTC snapshot, no full-table IPv4 peer among 322 saw that exact /24. The numerically adjacent 91.206.91.0/24, a separate PROFILAN-NET registration, was seen by 321 of the same 322 peers.

The transfer line moves 256 IPv4 addresses within Poland. The RDAP card for the transferred /24 bears ITCare’s registrant handle and the same-day registration time. That is the registry side of the story: a dated permanent transfer and a new, exact PI assignment. It is a useful receipt. It is not a BGP announcement.

At midnight UTC on 4 November, RIPE RIS’s routing-status endpoint found the exact 91.206.90.0/24 at 0/322 full-table IPv4 peers and listed no origin. Its last_seen field points to 23 September 2025, when the /24 appeared with AS198163. That is 407 calendar days before this snapshot. A separate RIS history query from 1 September to 4 November 2026 also returned no exact-prefix origin with the minimum set to one peer.

One address block higher, 91.206.91.0/24 gave the opposite picture at the same instant: 321/322 peers, origin AS196849. Its RDAP object is PROFILAN-NET, an ASSIGNED PI record first registered in 2011. The two /24s sit beside each other numerically; the transfer file names only the lower one. The upper one supplies a useful same-time comparison, not a second asset in the deal.

RIPE’s own routing-status guide says the peer count covers full-table RIS peers and the origins list covers an exact matching prefix. The practical question is when the newly registered /24 becomes visible under a route, if it does. A later RIS exact-prefix sighting or a dated operator notice would answer that. For now, the registry has a fresh name while the route collectors have an empty chair.

Official records: RIPE assignment-transfer file; ITCare /24 RDAP; adjacent /24 RDAP; transferred /24 RIS status; adjacent /24 RIS status; transferred /24 RIS history; routing-status documentation; routing-history documentation.