bgpreport

Network · data from 2026-11-12

AS398340 ANET-LAB - IDC

Registry name: ANET-LAB - IDC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS398340, 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.12.16.0/24 Valid Nonecovered by 130.12.16.0/22 672 100% 67
130.12.17.0/24 Valid Nonecovered by 130.12.16.0/22 672 100% 67
130.12.19.0/24 Valid Nonecovered by 130.12.16.0/22 672 100% 67
2602:f864:d00::/40 Valid Nonecovered by 2602:f864::/32 635 100% 69
156.9.163.0/24 Valid RIR databaseARIN 666 99% 67
156.9.160.0/22 Valid RIR databaseARIN 0 0%low visibility 1

AS-SET

AS398340 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.

  • Route object: none4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none130.12.16.0/24No route object for it. A route object for 130.12.16.0/22 with origin AS398340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398340 in the RIR database for the space.672 of 673
Route object: none130.12.17.0/24No route object for it. A route object for 130.12.16.0/22 with origin AS398340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398340 in the RIR database for the space.672 of 673
Route object: none130.12.19.0/24No route object for it. A route object for 130.12.16.0/22 with origin AS398340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398340 in the RIR database for the space.672 of 673
Route object: none2602:f864:d00::/40No route object for it. A route object for 2602:f864::/32 with origin AS398340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398340 in the RIR database for the space.635 of 636

Route objects not announced

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

23.185.104.0/24ARINValid
130.12.16.0/22ARINValid
156.9.160.0/23ARINValid
156.9.160.0/24ARINValid
156.9.161.0/24ARINValid
156.9.162.0/23ARINValid
156.9.162.0/24ARINValid
2602:f864::/32ARINValid

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.