[db-wg] RIPE-NONAUTH route object anomalies
- Previous message (by thread): [db-wg] RIPE-NONAUTH route object anomalies
- Next message (by thread): [db-wg] RIPE-NONAUTH route object anomalies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Fri Jun 11 12:04:28 CEST 2021
Hi Ronald, > On 11 Jun 2021, at 11:33, Edward Shryane via db-wg <db-wg at ripe.net> wrote: > > ... > >> 192.70.0.0/17 > > This prefix is referenced from 1 NONAUTH route: 192.70.0.0/17AS2200 > > The prefix is mostly assigned to the RIPE region, except for a /24: > > ripencc|FR|ipv4|192.70.0.0|23552|19930901|assigned|4c5e10ae-266a-4127-84ac-04b780309b1d > ripencc|FR|ipv4|192.70.92.0|1280|20050411|assigned|b8f87e41-6e2a-427f-af98-60c978d51985 > ripencc|FR|ipv4|192.70.97.0|4352|19930901|assigned|3e011729-91a0-412e-8947-1ac32eef22e2 > 192.70.113.0 - 192.70.113.255 not in *any* delegated stats file? Apologies, I mis-calculated this range: 4352 = /20 + /24, the 192.70.113.0/24 *is* assigned to the RIPE region. > ripencc|FR|ipv4|192.70.114.0|256|19900315|assigned|3e219d39-a2e5-476b-bf9b-835f172f89ae > ripencc|FR|ipv4|192.70.115.0|256|19900315|assigned|4d073146-29da-45c5-a74c-e90c3963405f > ripencc|FR|ipv4|192.70.116.0|256|19900315|assigned|ef2d7312-e300-4850-83d0-e99faa095c12 > ripencc|FR|ipv4|192.70.117.0|256|19930520|assigned|a4b599d8-871f-4f0a-b5c3-5b5d96a614e4 > I also omitted a few ranges, this prefix is also split between RIPE and ARIN: ripencc|FR|ipv4|192.70.118.0|256|20090824|assigned|93a1d9ff-0291-4ecd-a36d-6e231d34e12c ripencc|FR|ipv4|192.70.119.0|256|19930419|assigned|97f599a0-440b-4d6c-a58e-a56c5436a43a arin|US|ipv4|192.70.120.0|256|19900324|allocated|1f99771bc3e23e6097509a331544ab65 arin|US|ipv4|192.70.121.0|256|19900324|allocated|1f99771bc3e23e6097509a331544ab65 arin|US|ipv4|192.70.122.0|256|19900324|allocated|1f99771bc3e23e6097509a331544ab65 arin|US|ipv4|192.70.123.0|256|19900324|allocated|1f99771bc3e23e6097509a331544ab65 arin|US|ipv4|192.70.124.0|256|19900324|allocated|1f99771bc3e23e6097509a331544ab65 arin|US|ipv4|192.70.125.0|256|19900324|allocated|1f99771bc3e23e6097509a331544ab65 arin|US|ipv4|192.70.126.0|256|19900324|allocated|1f99771bc3e23e6097509a331544ab65 arin|US|ipv4|192.70.127.0|256|19900324|allocated|1f99771bc3e23e6097509a331544ab65 These 4 prefixes you mentioned are historically split between RIRs, and not due to an Inter-RIR transfer. Regards Ed Shryane RIPE NCC
- Previous message (by thread): [db-wg] RIPE-NONAUTH route object anomalies
- Next message (by thread): [db-wg] RIPE-NONAUTH route object anomalies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]