bgpreport

Network · data from 2026-11-12

AS21691 TMCC-2 - Toyota Motor Credit Corporation

Registry name: TMCC-2 - Toyota Motor Credit Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21691, 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.
12.29.87.0/24 No ROA None 672 100% 67
12.159.13.0/24 No ROA None 672 100% 67
8.18.96.0/23 No ROA Other IRR onlyRADB 673 100% 67
8.20.50.0/23 No ROA Other IRR onlyRADB 673 100% 67
64.124.190.0/24 Valid None 672 100% 67
64.125.44.0/24 Valid None 672 100% 67
209.249.30.0/24 Valid None 672 100% 67
209.249.200.0/24 Valid None 671 100% 67

AS-SET

AS21691 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 13 are in fix.csv.

  • ROA: none4
  • Route object: none6
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none12.29.87.0/24No ROA covers it. Add a ROA for AS21691, maxLength 24.672 of 673
Route object: none12.29.87.0/24No route object for it. Add a route object with origin AS21691 in the RIR database for the space.672 of 673
ROA: none12.159.13.0/24No ROA covers it. Add a ROA for AS21691, maxLength 24.672 of 673
Route object: none12.159.13.0/24No route object for it. Add a route object with origin AS21691 in the RIR database for the space.672 of 673
ROA: none8.18.96.0/23No ROA covers it. Add a ROA for AS21691, maxLength 23.673 of 673
Route object: RIR8.18.96.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none8.20.50.0/23No ROA covers it. Add a ROA for AS21691, maxLength 23.673 of 673
Route object: RIR8.20.50.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none64.124.190.0/24No route object for it. Add a route object with origin AS21691 in the RIR database for the space.672 of 673
Route object: none64.125.44.0/24No route object for it. Add a route object with origin AS21691 in the RIR database for the space.672 of 673
Route object: none209.249.30.0/24No route object for it. Add a route object with origin AS21691 in the RIR database for the space.672 of 673
Route object: none209.249.200.0/24No route object for it. Add a route object with origin AS21691 in the RIR database for the space.671 of 673

Route objects not announced

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

64.95.109.0/24RADBNo ROA

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.