bgpreport

Network · data from 2026-11-12

AS55192 TEKNET-WISP - teknet

Registry name: TEKNET-WISP - teknet, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55192, 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.

130.51.204.0/24 No ROA Nonecovered by 130.51.204.0/22 673 100% 67
130.51.205.0/24 No ROA Nonecovered by 130.51.204.0/22 673 100% 67
130.51.206.0/24 No ROA Nonecovered by 130.51.204.0/22 673 100% 67
130.51.207.0/24 No ROA Nonecovered by 130.51.204.0/22 673 100% 67
208.99.28.0/24 No ROA Nonecovered by 208.99.28.0/22 673 100% 67
208.99.29.0/24 No ROA Nonecovered by 208.99.28.0/22 673 100% 67
208.99.30.0/24 No ROA Nonecovered by 208.99.28.0/22 673 100% 67
208.99.31.0/24 No ROA Nonecovered by 208.99.28.0/22 673 100% 67
23.150.16.0/24 No ROA RIR databaseARIN 673 100% 67
23.150.17.0/24 No ROA RIR databaseARIN 673 100% 67
23.150.18.0/24 No ROA RIR databaseARIN 673 100% 67
23.150.19.0/24 No ROA RIR databaseARIN 673 100% 67
23.150.20.0/24 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS55192 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 23 are in fix.csv.

  • ROA: none13
  • Route object: none8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none130.51.204.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
Route object: none130.51.204.0/24No route object for it. A route object for 130.51.204.0/22 with origin AS55192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55192 in the RIR database for the space.673 of 673
ROA: none130.51.205.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
Route object: none130.51.205.0/24No route object for it. A route object for 130.51.204.0/22 with origin AS55192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55192 in the RIR database for the space.673 of 673
ROA: none130.51.206.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
Route object: none130.51.206.0/24No route object for it. A route object for 130.51.204.0/22 with origin AS55192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55192 in the RIR database for the space.673 of 673
ROA: none130.51.207.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
Route object: none130.51.207.0/24No route object for it. A route object for 130.51.204.0/22 with origin AS55192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55192 in the RIR database for the space.673 of 673
ROA: none208.99.28.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
Route object: none208.99.28.0/24No route object for it. A route object for 208.99.28.0/22 with origin AS55192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55192 in the RIR database for the space.673 of 673
ROA: none208.99.29.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
Route object: none208.99.29.0/24No route object for it. A route object for 208.99.28.0/22 with origin AS55192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55192 in the RIR database for the space.673 of 673
ROA: none208.99.30.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
Route object: none208.99.30.0/24No route object for it. A route object for 208.99.28.0/22 with origin AS55192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55192 in the RIR database for the space.673 of 673
ROA: none208.99.31.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
Route object: none208.99.31.0/24No route object for it. A route object for 208.99.28.0/22 with origin AS55192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55192 in the RIR database for the space.673 of 673
ROA: none23.150.16.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
ROA: none23.150.17.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
ROA: none23.150.18.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
ROA: none23.150.19.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673
ROA: none23.150.20.0/24No ROA covers it. Add a ROA for AS55192, maxLength 24.673 of 673

Route objects not announced

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

130.51.204.0/22ARINNo ROA
208.99.28.0/22ARINNo 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.