bgpreport

Network · data from 2026-11-12

AS400005 Wilco Wireless

Registry name: WILCO-WIRELESS - Wilco Wireless Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400005, 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:fc46::/39 Valid Nonecovered by 2602:fc46::/36 635 100% 67
2602:fc46:200::/39 Valid Nonecovered by 2602:fc46::/36 635 100% 69
23.185.240.0/24 Valid RIR databaseARIN 671 100% 67
23.185.241.0/24 Valid RIR databaseARIN 670 100% 68

AS-SET

AS400005'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 3 are in fix.csv.

  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2602:fc46::/39No route object for it. A route object for 2602:fc46::/36 with origin AS400005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400005 in the RIR database for the space.635 of 636
Route object: none2602:fc46:200::/39No route object for it. A route object for 2602:fc46::/36 with origin AS400005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400005 in the RIR database for the space.635 of 636

Route objects not announced

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

2602:fc46::/36ARINValid

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.