bgpreport

Network · data from 2026-11-12

AS17004 BROADBANDONDEMAND - Kentucky Wimax

Registry name: BROADBANDONDEMAND - Kentucky Wimax, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17004, 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.
100.42.32.0/20 No ROA RIR databaseARIN, RADB 672 100% 67
142.202.56.0/22 No ROA RIR databaseARIN, RADB 670 100% 67

AS-SET

AS17004 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 4 are in fix.csv.

  • ROA: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none100.42.32.0/20No ROA covers it. Add a ROA for AS17004, maxLength 20.672 of 673
ROA: none142.202.56.0/22No ROA covers it. Add a ROA for AS17004, maxLength 22.670 of 673

Route objects not announced

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

12.44.213.0/24RADBNo ROA
209.65.192.0/20RADBNo 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.