RIPE Moved an ASN and Three Blocks to Elisa. One of Its Four Routes Belongs to Someone Else.

Summary

• RIPE NCC’s ASN transfer original lists AS58340, and its allocated IPv4 transfer original lists 83.146.128.0/19, 84.240.112.0/20 and 193.177.188.0/22, all as 3 November POLICY transfers from Napapiirin Kuituverkot Oy to Elisa Oyj. The three address blocks total 13,312 IPv4 addresses. Current ASN RDAP names NKV-AS but identifies Elisa’s ORG-EO1-RIPE as registrant. Exact RDAP for 45.146.248.0/22 identifies Neve Oy’s ORG-NEJV1-RIPE instead.
• RIPEstat’s one-peer-threshold windows for 2–3 November and 3–4 November each list the same four prefixes under AS58340: two /20s inside the transferred /19, the transferred 193.177.188.0/22, and Neve’s 45.146.248.0/22. An exact 4 November 00:00 UTC status query for 84.240.112.0/20 shows zero of 322 full-table IPv4 peers and no listed more specifics.

The fourth route is not on the receipt

The two transfer tables put an ASN and three address blocks in the same destination column. That is a compelling administrative picture. The route list is a different set. 83.146.128.0/19 appears as two adjacent /20 announcements, 83.146.128.0/20 and 83.146.144.0/20. 193.177.188.0/22 appears as an exact route. 84.240.112.0/20, despite its transfer to Elisa, has no exact route or listed more specific in the midnight status query. Three transferred blocks therefore produce three observed prefix rows, not four.

The fourth row is 45.146.248.0/22. Its exact RIPE RDAP card identifies Neve Oy, with a 2019 registration event and a September 2026 last change. It is not among the three 3 November Elisa address-transfer rows. Yet the AS58340 observation lists it in both full-day windows. The ASN’s own RDAP now names Elisa as registrant while preserving the old NKV-AS label. An ASN can originate space registered to another organisation; the route tells us what collectors saw, while the IP card tells us whose registration record is current. A customer or operator agreement would explain the arrangement here.

The arithmetic matters. The transferred /19 contains 8,192 addresses and its two observed /20s cover that parent. The transferred /20 contains 4,096 and is absent from this route-status response. The transferred /22 contains 1,024 and appears as itself. The Neve /22 adds a distinct 1,024-address route outside the transferred address set. Those quantities describe registry ranges and prefix sizes; they do not say every address carried traffic. RIPEstat’s timelines cover their requested days at a minimum one-peer threshold. A finer trace would identify any short intra-day change that a daily window smooths over.

Four boxes in a transfer file and four lines in a route result may look balanced at a glance. They are not the same four. A buyer who uses the ASN’s route list as a closing inventory would quietly count Neve’s space and miss an Elisa block. That is how a tidy spreadsheet becomes a bad asset schedule.