bgpreport

Network · data from 2026-11-12

AS17506 ARTERIA Networks Corporation (UCOM)

Registry name: UCOM - ARTERIA Networks Corporation, JP · PeeringDB

40IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS17506, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17506, 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.

2405:f800::/32 No ROA Other IRR onlyRADB 636 100% 67
43.232.0.0/14 Valid Other IRR onlyRADB 673 100% 67
58.4.0.0/15 Valid Other IRR onlyRADB 673 100% 67
58.12.0.0/15 Valid Other IRR onlyRADB 673 100% 67
58.80.0.0/15 Valid Other IRR onlyRADB 673 100% 67
58.156.0.0/15 Valid Other IRR onlyRADB 673 100% 67
58.158.0.0/15 Valid Other IRR onlyRADB 673 100% 67
58.159.0.0/17 Valid Other IRR onlyRADB 673 100% 67
58.159.128.0/18 Valid Other IRR onlyRADB 673 100% 67
58.159.196.0/22 Valid Other IRR onlyRADB 673 100% 67
58.159.200.0/21 Valid Other IRR onlyRADB 673 100% 67
58.159.208.0/20 Valid Other IRR onlyRADB 673 100% 67
58.159.224.0/20 Valid Other IRR onlyRADB 673 100% 67
59.87.0.0/16 Valid Other IRR onlyRADB 673 100% 67
113.40.0.0/14 Valid Other IRR onlyRADB 673 100% 67
115.125.0.0/16 Valid Other IRR onlyRADB 673 100% 67
122.208.0.0/14 Valid Other IRR onlyRADB 673 100% 67
122.212.0.0/14 Valid Other IRR onlyRADB 673 100% 67
122.216.0.0/14 Valid Other IRR onlyRADB 673 100% 67
122.220.0.0/15 Valid Other IRR onlyRADB 673 100% 67
124.32.0.0/14 Valid Other IRR onlyRADB 673 100% 67
124.36.0.0/14 Valid Other IRR onlyRADB 673 100% 67
125.100.0.0/14 Valid Other IRR onlyRADB 673 100% 67
202.210.192.0/18 Valid Other IRR onlyRADB 673 100% 67
202.226.128.0/18 Valid Other IRR onlyRADB 673 100% 67
219.113.128.0/17 Valid Other IRR onlyRADB 673 100% 67
219.120.0.0/16 Valid Other IRR onlyRADB 673 100% 67
219.123.0.0/16 Valid Other IRR onlyRADB 673 100% 67
220.151.0.0/16 Valid Other IRR onlyRADB 673 100% 67
220.218.0.0/16 Valid Other IRR onlyRADB 673 100% 67
221.112.0.0/16 Valid Other IRR onlyRADB 673 100% 67
221.114.0.0/16 Valid Other IRR onlyRADB 673 100% 67
221.115.0.0/16 Valid Other IRR onlyRADB 673 100% 67
221.116.0.0/16 Valid Other IRR onlyRADB 673 100% 67
221.117.0.0/16 Valid Other IRR onlyRADB 673 100% 67
59.158.0.0/15 Valid Other IRR onlyRADB 672 100% 67
210.79.0.0/20 Valid Other IRR onlyRADB 672 100% 67
58.158.0.0/16 Valid Other IRR onlyRADB 670 100% 67
61.122.112.0/20 Valid Other IRR onlyRADB 670 100% 67
113.32.0.0/13 Valid Other IRR onlyRADB 669 99% 67
221.240.0.0/12 Valid Other IRR onlyRADB 669 99% 67

AS-SET

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

  • ROA: none1
  • Route object: RIR41
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2405:f800::/32No ROA covers it. Add a ROA for AS17506, maxLength 32.636 of 636
Route object: RIR2405:f800::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR43.232.0.0/14Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.4.0.0/15Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.12.0.0/15Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.80.0.0/15Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.156.0.0/15Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.158.0.0/15Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.159.0.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.159.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.159.196.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.159.200.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.159.208.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.159.224.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR59.87.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR113.40.0.0/14Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR115.125.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR122.208.0.0/14Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR122.212.0.0/14Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR122.216.0.0/14Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR122.220.0.0/15Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.32.0.0/14Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR124.36.0.0/14Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR125.100.0.0/14Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.210.192.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.226.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR219.113.128.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR219.120.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR219.123.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR220.151.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR220.218.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR221.112.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR221.114.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR221.115.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR221.116.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR221.117.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR59.158.0.0/15Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.79.0.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.158.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR61.122.112.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR113.32.0.0/13Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR221.240.0.0/12Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

221.114.0.0/15RADBValid
221.116.0.0/15RADBValid

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.