bgpreport

Network · data from 2026-11-12

AS400205 INFONETWORKS - InfoNet

Registry name: INFONETWORKS - InfoNet, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400205, 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.
174.136.208.0/24 No ROA Nonecovered by 174.136.208.0/22 673 100% 67
174.136.209.0/24 No ROA Nonecovered by 174.136.208.0/22 673 100% 67
174.136.210.0/24 No ROA Nonecovered by 174.136.208.0/22 673 100% 67
174.136.211.0/24 No ROA Nonecovered by 174.136.208.0/22 673 100% 67
206.251.60.0/22 No ROA None 671 100% 68
174.136.208.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
199.127.156.0/22 No ROA RIR databaseARIN 671 100% 68

AS-SET

AS400205 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 12 are in fix.csv.

  • ROA: none7
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none174.136.208.0/24No ROA covers it. Add a ROA for AS400205, maxLength 24.673 of 673
Route object: none174.136.208.0/24No route object for it. A route object for 174.136.208.0/22 with origin AS400205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400205 in the RIR database for the space.673 of 673
ROA: none174.136.209.0/24No ROA covers it. Add a ROA for AS400205, maxLength 24.673 of 673
Route object: none174.136.209.0/24No route object for it. A route object for 174.136.208.0/22 with origin AS400205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400205 in the RIR database for the space.673 of 673
ROA: none174.136.210.0/24No ROA covers it. Add a ROA for AS400205, maxLength 24.673 of 673
Route object: none174.136.210.0/24No route object for it. A route object for 174.136.208.0/22 with origin AS400205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400205 in the RIR database for the space.673 of 673
ROA: none174.136.211.0/24No ROA covers it. Add a ROA for AS400205, maxLength 24.673 of 673
Route object: none174.136.211.0/24No route object for it. A route object for 174.136.208.0/22 with origin AS400205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400205 in the RIR database for the space.673 of 673
ROA: none206.251.60.0/22No ROA covers it. Add a ROA for AS400205, maxLength 22.671 of 673
Route object: none206.251.60.0/22No route object for it. Add a route object with origin AS400205 in the RIR database for the space.671 of 673
ROA: none174.136.208.0/22No ROA covers it. Add a ROA for AS400205, maxLength 22.671 of 673
ROA: none199.127.156.0/22No ROA covers it. Add a ROA for AS400205, maxLength 22.671 of 673

Route objects not announced

Every route object with origin AS400205 is announced.

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.