bgpreport

Network · data from 2026-11-12

AS215871 XTOM-JP xTom Japan Corporation

Registry name: XTOM-JP xTom Japan Corporation, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215871, 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.
163.128.26.0/24 No ROA Other IRR onlyRADB 669 99% 67
163.128.27.0/24 No ROA Other IRR onlyRADB 666 99% 67
2402:5120:100::/40 No ROA Other IRR onlyRADB 634 100% 69
2402:5120::/40 No ROA Other IRR onlyRADB 630 99% 67
2a14:1f80::/29 Valid RIR databaseRADB, RIPE 631 99% 67

AS-SET

AS215871 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 10 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none163.128.26.0/24No ROA covers it. Add a ROA for AS215871, maxLength 24.669 of 673
Route object: RIR163.128.26.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none163.128.27.0/24No ROA covers it. Add a ROA for AS215871, maxLength 24.666 of 673
Route object: RIR163.128.27.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2402:5120:100::/40No ROA covers it. Add a ROA for AS215871, maxLength 40.634 of 636
Route object: RIR2402:5120:100::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2402:5120::/40No ROA covers it. Add a ROA for AS215871, maxLength 40.630 of 636
Route object: RIR2402:5120::/40Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

163.128.26.0/23RADBNo ROA
2402:5120::/32RADBNo 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.