bgpreport

Network · data from 2026-11-12

AS1097 Core Transit 1097

Registry name: CORE-TRANSIT - Core Transit LLC, US · PeeringDB

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

Announced routes

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

134.199.54.0/24 Valid Nonecovered by 134.199.54.0/23 673 100% 67
134.199.56.0/24 Valid Nonecovered by 134.199.56.0/23 672 100% 66
50.20.192.0/24 Valid Nonecovered by 50.20.192.0/23 671 100% 68
50.20.195.0/24 Valid Nonecovered by 50.20.192.0/22 671 100% 68
192.34.112.0/24 Valid Nonecovered by 192.34.112.0/23 670 100% 67
2607:77c0:3000::/36 Valid Nonecovered by 2607:77c0::/32 636 100% 67
2607:77c0:4000::/48 Valid Nonecovered by 2607:77c0::/32 636 100% 67
2607:77c0:4001::/48 Valid Nonecovered by 2607:77c0::/32 636 100% 67
2607:77c0:5000::/36 Valid Nonecovered by 2607:77c0::/32 636 100% 68
2607:77c0:2000::/36 Valid Nonecovered by 2607:77c0::/32 634 100% 67
2607:77c0:1000::/36 Valid Other IRR onlyRADB 635 100% 69
167.88.222.0/24 Valid RIR databaseARIN 673 100% 67
23.145.20.0/24 Valid RIR databaseARIN 672 100% 66
23.152.68.0/24 Valid RIR databaseARIN 672 100% 66
134.199.56.0/23 Valid RIR databaseARIN 672 100% 66
172.81.148.0/22 Valid RIR databaseARIN 672 100% 66
198.22.165.0/24 Valid RIR databaseARIN 672 100% 66
167.88.212.0/24 Valid RIR databaseARIN 671 100% 68
216.146.16.0/24 Valid RIR databaseARIN 670 100% 67
216.146.17.0/24 Valid RIR databaseARIN 670 100% 67
216.146.18.0/24 Valid RIR databaseARIN 670 100% 67
216.146.19.0/24 Valid RIR databaseARIN 669 99% 67
2602:81c:3000::/44 Valid RIR databaseARIN 634 100% 67
2602:81c:f000::/44 Valid RIR databaseARIN 634 100% 67

AS-SET

AS1097'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 22 are in fix.csv.

  • Route object: none10
  • Route object: RIR1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: none134.199.54.0/24No route object for it. A route object for 134.199.54.0/23 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.673 of 673
Route object: none134.199.56.0/24No route object for it. A route object for 134.199.56.0/23 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.672 of 673
Route object: none50.20.192.0/24No route object for it. A route object for 50.20.192.0/23 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.671 of 673
Route object: none50.20.195.0/24No route object for it. A route object for 50.20.192.0/22 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.671 of 673
Route object: none192.34.112.0/24No route object for it. A route object for 192.34.112.0/23 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.670 of 673
Route object: none2607:77c0:3000::/36No route object for it. A route object for 2607:77c0::/32 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.636 of 636
Route object: none2607:77c0:4000::/48No route object for it. A route object for 2607:77c0::/32 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.636 of 636
Route object: none2607:77c0:4001::/48No route object for it. A route object for 2607:77c0::/32 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.636 of 636
Route object: none2607:77c0:5000::/36No route object for it. A route object for 2607:77c0::/32 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.636 of 636
Route object: none2607:77c0:2000::/36No route object for it. A route object for 2607:77c0::/32 with origin AS1097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1097 in the RIR database for the space.634 of 636
Route object: RIR2607:77c0:1000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

50.20.192.0/22ARINValid
50.20.192.0/23RADBValid
50.20.194.0/24RADBValid
134.199.54.0/23ARINValid
167.88.211.0/24ARINValid
192.34.112.0/23ARINValid
198.102.29.0/24ARINValid
216.146.16.0/22ARINValid
2606:6fc0::/32ARINValid
2607:77c0::/32ARINValid
2607:77c0::/36ARINValid

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.