bgpreport

Network · data from 2026-11-12

AS397468 THINKON

Registry name: THINKON - Think On, Inc., CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS397468, 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.
149.5.5.0/24 No ROA None 2 0%low visibility 2
2001:550:1800::/48 No ROA Other IRR onlyRADB 635 100% 70
38.84.8.0/24 Valid Other IRR onlyRADB 670 100% 67
192.92.246.0/24 Valid RIR databaseARIN 673 100% 67
216.83.4.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.83.5.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.83.11.0/24 Valid RIR databaseARIN 673 100% 67
216.83.19.0/24 Valid RIR databaseARIN 673 100% 67
216.83.20.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.83.27.0/24 Valid RIR databaseARIN 673 100% 67
216.83.28.0/24 Valid RIR databaseARIN, RADB 673 100% 67
38.20.176.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.20.177.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.102.93.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.102.103.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.121.58.0/24 Valid RIR databaseARIN, BELL, RADB 672 100% 67
38.129.0.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.248.1.0/24 Valid RIR databaseARIN 672 100% 67
38.69.220.0/24 Valid RIR databaseARIN 671 100% 67
38.99.138.0/24 Valid RIR databaseARIN, RADB 671 100% 67
160.191.42.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.14.38.0/24 Valid RIR databaseAPNIC 671 100% 67
203.15.172.0/23 Valid RIR databaseAPNIC 671 100% 67
216.83.25.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.64.255.0/24 Valid RIR databaseARIN, RADB 669 99% 67

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none149.5.5.0/24No ROA covers it. Add a ROA for AS397468, maxLength 24.2 of 673
Route object: none149.5.5.0/24No route object for it. Add a route object with origin AS397468 in the RIR database for the space.2 of 673
ROA: none2001:550:1800::/48No ROA covers it. Add a ROA for AS397468, maxLength 48.635 of 636
Route object: RIR2001:550:1800::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR38.84.8.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

216.83.18.0/24ARINNo ROA
2001:470:26c::/48ARINValid

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.