bgpreport

Network · data from 2026-11-12

AS62900 Kerfuffle Anycast

Registry name: KERFUFFLE-62900 - Kerfuffle, LLC, US · PeeringDB

0IPv4 routes
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS62900, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62900, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
2602:2d5:f0::/48 Valid RIR databaseARIN 635 100% 69
2602:2d5:f1::/48 Valid RIR databaseARIN 635 100% 69

AS-SET

AS62900's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 9 are in fix.csv.

  • Route object: not announced9

Route objects not announced

Route objects with origin AS62900 whose prefix no peer sees AS62900 announce. Many are kept on purpose (backup routes, space announced only in some places).

102.38.192.0/18NTTCOMNo ROA
192.219.120.0/21NTTCOMNo ROA
192.219.128.0/18NTTCOMNo ROA
192.219.192.0/20NTTCOMNo ROA
192.219.208.0/21NTTCOMNo ROA
199.4.151.0/24NTTCOMNo ROA
205.207.134.0/24NTTCOMNo ROA
205.210.107.0/24NTTCOMNo ROA
206.51.29.0/24NTTCOMNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.