bgpreport

Network · data from 2026-11-12

AS60 Advanced Information Technology Services, LLC

Registry name: AINET-AS60-PDFFILE - American Information Network, US · PeeringDB

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

Announced routes

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

136.175.12.0/22 No ROA Other origin only 461 68% 64
147.160.157.0/24 No ROA Other origin only 461 68% 64
2607:f308::/32 Valid RIR databaseARIN 468 74% 66
205.134.160.0/19 Valid RIR databaseARIN 461 68% 64
154.54.100.0/22 Valid RIR databaseARIN 460 68% 64
38.41.112.0/22 Valid RIR databaseARIN 459 68% 64
38.100.44.0/22 Valid RIR databaseARIN 458 68% 64
38.100.56.0/22 Valid RIR databaseARIN 458 68% 64

AS-SET

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

  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none136.175.12.0/22No ROA covers it. Add a ROA for AS60, maxLength 22.461 of 673
Route object: none136.175.12.0/22Route objects for it name AS6405. Add a route object with origin AS60 in the RIR database for the space.461 of 673
ROA: none147.160.157.0/24No ROA covers it. Add a ROA for AS60, maxLength 24.461 of 673
Route object: none147.160.157.0/24Route objects for it name AS6405. Add a route object with origin AS60 in the RIR database for the space.461 of 673

Route objects not announced

Every route object with origin AS60 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.