bgpreport

Network · data from 2026-11-12

AS138380 VOLVO-GROUP-IT-APNIC-AS-AP - VOLVO GROUP KOREA CO LTD, Construction Equipment Seoul

Registry name: VOLVO-GROUP-IT-APNIC-AS-AP - VOLVO GROUP KOREA CO LTD, Construction Equipment Seoul, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138380, 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.
203.254.239.0/24 No ROA Other IRR onlyRADB 673 100% 66
203.254.240.0/24 No ROA Other IRR onlyRADB 673 100% 66
153.112.200.0/23 Valid Other IRR onlyRADB 673 100% 67
192.157.12.0/23 Valid Other IRR onlyRADB 673 100% 67
193.235.108.0/23 Valid Other IRR onlyRADB 673 100% 67
192.157.12.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
192.157.13.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS138380 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 12 are in fix.csv.

  • ROA: none2
  • Route object: RIR5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none203.254.239.0/24No ROA covers it. Add a ROA for AS138380, maxLength 24.673 of 673
Route object: RIR203.254.239.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.254.240.0/24No ROA covers it. Add a ROA for AS138380, maxLength 24.673 of 673
Route object: RIR203.254.240.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR153.112.200.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.157.12.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR193.235.108.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

153.112.200.0/24RIPEValid
153.112.204.0/24RADBValid
193.183.234.0/23RADBNo ROA
193.235.108.0/24RIPEValid
193.235.109.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.