bgpreport

Network · data from 2026-11-12

AS54106 8WIRE - 8-Wire LLC

Registry name: 8WIRE - 8-Wire LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54106, 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.
135.129.96.0/24 No ROA Nonecovered by 135.129.96.0/23 671 100% 68
135.129.97.0/24 No ROA Nonecovered by 135.129.96.0/23 671 100% 68
135.129.106.0/24 No ROA Nonecovered by 135.129.106.0/23 671 100% 68
135.129.107.0/24 No ROA Nonecovered by 135.129.106.0/23 671 100% 68
72.249.254.0/24 No ROA RIR databaseARIN 671 100% 68

AS-SET

AS54106 isn't in PeeringDB, where networks name their 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none135.129.96.0/24No ROA covers it. Add a ROA for AS54106, maxLength 24.671 of 673
Route object: none135.129.96.0/24No route object for it. A route object for 135.129.96.0/23 with origin AS54106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54106 in the RIR database for the space.671 of 673
ROA: none135.129.97.0/24No ROA covers it. Add a ROA for AS54106, maxLength 24.671 of 673
Route object: none135.129.97.0/24No route object for it. A route object for 135.129.96.0/23 with origin AS54106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54106 in the RIR database for the space.671 of 673
ROA: none135.129.106.0/24No ROA covers it. Add a ROA for AS54106, maxLength 24.671 of 673
Route object: none135.129.106.0/24No route object for it. A route object for 135.129.106.0/23 with origin AS54106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54106 in the RIR database for the space.671 of 673
ROA: none135.129.107.0/24No ROA covers it. Add a ROA for AS54106, maxLength 24.671 of 673
Route object: none135.129.107.0/24No route object for it. A route object for 135.129.106.0/23 with origin AS54106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54106 in the RIR database for the space.671 of 673
ROA: none72.249.254.0/24No ROA covers it. Add a ROA for AS54106, maxLength 24.671 of 673

Route objects not announced

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

135.129.96.0/23ARINNo ROA
135.129.106.0/23ARINNo 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.