bgpreport

Network · data from 2026-11-12

AS15626 ITL Company AS15626

Registry name: ITL-UA ROUTE 95 LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15626, 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.
38.244.192.0/24 Invalid: origin Other origin only 1 0%low visibility 1
130.0.232.0/21 Invalid: origin Other origin only 1 0%low visibility 1
45.128.148.0/24 No ROA Other origin only 1 0%low visibility 1
171.33.241.0/24 Valid RIR databaseRIPE 673 100% 67
185.253.0.0/24 Valid RIR databaseRIPE 673 100% 67
195.28.182.0/23 Valid RIR databaseRIPE 673 100% 67
217.12.192.0/23 Valid RIR databaseRIPE 673 100% 66
217.12.195.0/24 Valid RIR databaseRIPE 673 100% 66
217.12.196.0/23 Valid RIR databaseRIPE 673 100% 66
217.12.198.0/24 Valid RIR databaseRIPE 673 100% 66
217.12.205.0/24 Valid RIR databaseRIPE 673 100% 66
217.12.210.0/24 Valid RIR databaseRIPE 673 100% 67
217.12.211.0/24 Valid RIR databaseRIPE 673 100% 66
217.12.212.0/23 Valid RIR databaseRIPE 673 100% 66
217.12.214.0/24 Valid RIR databaseRIPE 673 100% 66
217.12.216.0/23 Valid RIR databaseRIPE 673 100% 66
217.12.222.0/24 Valid RIR databaseRIPE 673 100% 66
2a02:27a8::/32 Valid RIR databaseRIPE 636 100% 67
2a02:27ad::/32 Valid RIR databaseRIPE 635 100% 67
2001:67c:2f6c::/48 Valid RIR databaseRIPE 634 100% 67
2a0a:8c46::/32 Valid RIR databaseRIPE 634 100% 67
5.34.183.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
82.118.17.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
193.238.152.0/23 Valid RIR databaseRIPE 2 0%low visibility 2
217.12.221.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
217.12.223.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS15626'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 19 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none3
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin38.244.192.0/24ROAs covering it name AS44894, not AS15626. If AS15626 should announce it, add a ROA for AS15626.1 of 673
Route object: none38.244.192.0/24Route objects for it name AS44894. Add a route object with origin AS15626 in the RIR database for the space.1 of 673
ROA: origin130.0.232.0/21ROAs covering it name AS44894, not AS15626. If AS15626 should announce it, add a ROA for AS15626.1 of 673
Route object: none130.0.232.0/21Route objects for it name AS44894. Add a route object with origin AS15626 in the RIR database for the space.1 of 673
ROA: none45.128.148.0/24No ROA covers it. Add a ROA for AS15626, maxLength 24.1 of 673
Route object: none45.128.148.0/24Route objects for it name AS44894. Add a route object with origin AS15626 in the RIR database for the space.1 of 673

Route objects not announced

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

5.34.182.0/23RIPENo ROA
5.34.182.0/24RIPEValid
217.12.192.0/19RIPENo ROA
217.12.192.0/21RIPENo ROA
217.12.204.0/23RIPENo ROA
217.12.210.0/23RIPENo ROA
217.12.212.0/22RIPENo ROA
217.12.220.0/22RIPENo ROA
2a02:128:4:2000::/64RIPEInvalid: origin
2a02:27a8:0:2::/64RIPEInvalid: maxLength
2a02:27a8:0:a::/64RIPEInvalid: maxLength
2a02:27a8:feed::/48RIPEValid
2a05:9407::/32RIPEValid

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.