ScopeSky gets three /24s; one still routes via Elsuhd AS197893

RIPE Gave ScopeSky Three /24s. One Still Speaks Through Elsuhd’s ASN.

Why it matters

At 10:11 UTC, the registry put three Iraqi IPv4 blocks under ScopeSky. More than an hour later, RIPE NCC’s route collectors still heard one of them from AS197893, registered to the company that had transferred it.

Theo March3 November 2026Reading Time 2 minLast update: 3 November 2026

RIPE NCC registered three /24s to ScopeSky on 3 November; after registration, RIS still observed one prefix originating from Elsuhd’s AS197893.

Summary

RIPE NCC’s transfer ledger records three permanent, policy-based Iraq-to-Iraq transfers on 3 November: 176.28.75.0/24, 176.28.76.0/24 and 185.58.13.0/24. Elsuhd is the source, ScopeSky the recipient; together they contain 768 IPv4 addresses.
RIPE NCC’s live Looking Glass still showed the exact 176.28.76.0/24 route with origin AS197893 at 322 peers across 23 collectors around 11:29 UTC. AS197893’s registry record names it ELSUHD-AS.

The registry changed first. ScopeSky’s RDAP record covers 176.28.75.0–176.28.76.255 and was registered at 10:11:14 UTC. The neighbouring 176.28.74.0/24 record remains under Elsuhd. The transfer ledger’s original 176.28.74.0/23 is the source envelope; the moved part was only its upper /24. The other moved /24, 176.28.76.0/24, joined it in ScopeSky’s current registry object.

The live route had another timetable. In the Looking Glass response, 321 of the 322 peer entries had confirmed the AS197893-origin route after the 10:11:14 registry timestamp. An administrative receipt and a BGP origin are different records, with different operators and clocks. Here they pointed to different names at the same time.

The third recipient record spans 185.58.12.0–185.58.14.255; the published transfer row names only 185.58.13.0/24. Counting the whole RDAP object as newly moved would invent another 512 addresses. The disclosed transfer remains three /24s and 768 addresses.

The public records do not disclose who operated the traffic on 176.28.76.0/24 after registration. A later route-origin change or an operating agreement would answer that question. The observable fact today is sharper: the new holder was already in RIPE’s database while the old holder’s ASN was still on the wire.