bgpreport

Network · data from 2026-11-12

AS58653 VolvoITJapan - UD Trucks Corporation, Volvo Information Technology Japan

Registry name: VolvoITJapan - UD Trucks Corporation, Volvo Information Technology Japan, JP · not in PeeringDB

7IPv4 routes 71.4% RPKI valid · 85.7% with a route object
0IPv6 routes
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
1Route objects not announced registered with origin AS58653, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58653, 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.
153.112.224.0/22 No ROA None 2 0%low visibility 2
170.102.224.0/24 No ROA RIR databaseRIPE 672 100% 67
153.112.224.0/23 Valid RIR databaseRIPE 672 100% 67
153.112.228.0/22 Valid RIR databaseRIPE 672 100% 67
192.157.14.0/24 Valid RIR databaseRIPE 672 100% 67
192.157.15.0/24 Valid RIR databaseRIPE 672 100% 67
193.53.29.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none153.112.224.0/22No ROA covers it. Add a ROA for AS58653, maxLength 22.2 of 673
Route object: none153.112.224.0/22No route object for it. Add a route object with origin AS58653 in the RIR database for the space.2 of 673
ROA: none170.102.224.0/24No ROA covers it. Add a ROA for AS58653, maxLength 24.672 of 673

Route objects not announced

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

193.235.104.0/24RIPEValid

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.