bgpreport

Network · data from 2026-11-12

AS15638 UTL Octopusnet LTD

Registry name: UTL Octopusnet LTD, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15638, 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.
46.46.17.0/24 No ROA Nonecovered by 46.46.16.0/20 672 100% 67
93.88.216.0/23 No ROA Nonecovered by 93.88.216.0/22 672 100% 67
93.88.218.0/23 No ROA Nonecovered by 93.88.216.0/22 672 100% 67
46.46.32.0/21 No ROA RIR databaseRIPE 672 100% 67
80.93.96.0/21 No ROA RIR databaseRIPE 672 100% 67
80.93.104.0/22 No ROA RIR databaseRIPE 672 100% 67
80.93.108.0/22 No ROA RIR databaseRIPE 672 100% 67
93.88.208.0/23 No ROA RIR databaseRIPE 672 100% 67
93.88.210.0/23 No ROA RIR databaseRIPE 672 100% 67
93.88.212.0/23 No ROA RIR databaseRIPE 672 100% 67
93.88.214.0/23 No ROA RIR databaseRIPE 672 100% 67
93.88.216.0/22 No ROA RIR databaseRIPE 672 100% 67

AS-SET

AS15638 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 30 are in fix.csv.

  • ROA: none12
  • Route object: none3
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none46.46.17.0/24No ROA covers it. Add a ROA for AS15638, maxLength 24.672 of 673
Route object: none46.46.17.0/24No route object for it. A route object for 46.46.16.0/20 with origin AS15638 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15638 in the RIR database for the space.672 of 673
ROA: none93.88.216.0/23No ROA covers it. Add a ROA for AS15638, maxLength 23.672 of 673
Route object: none93.88.216.0/23No route object for it. A route object for 93.88.216.0/22 with origin AS15638 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15638 in the RIR database for the space.672 of 673
ROA: none93.88.218.0/23No ROA covers it. Add a ROA for AS15638, maxLength 23.672 of 673
Route object: none93.88.218.0/23No route object for it. A route object for 93.88.216.0/22 with origin AS15638 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15638 in the RIR database for the space.672 of 673
ROA: none46.46.32.0/21No ROA covers it. Add a ROA for AS15638, maxLength 21.672 of 673
ROA: none80.93.96.0/21No ROA covers it. Add a ROA for AS15638, maxLength 21.672 of 673
ROA: none80.93.104.0/22No ROA covers it. Add a ROA for AS15638, maxLength 22.672 of 673
ROA: none80.93.108.0/22No ROA covers it. Add a ROA for AS15638, maxLength 22.672 of 673
ROA: none93.88.208.0/23No ROA covers it. Add a ROA for AS15638, maxLength 23.672 of 673
ROA: none93.88.210.0/23No ROA covers it. Add a ROA for AS15638, maxLength 23.672 of 673
ROA: none93.88.212.0/23No ROA covers it. Add a ROA for AS15638, maxLength 23.672 of 673
ROA: none93.88.214.0/23No ROA covers it. Add a ROA for AS15638, maxLength 23.672 of 673
ROA: none93.88.216.0/22No ROA covers it. Add a ROA for AS15638, maxLength 22.672 of 673

Route objects not announced

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

46.46.0.0/20RIPENo ROA
46.46.16.0/20RIPENo ROA
46.46.32.0/20RIPENo ROA
46.46.40.0/21RIPENo ROA
46.46.48.0/20RIPENo ROA
46.46.48.0/21RIPENo ROA
46.46.56.0/21RIPENo ROA
80.93.96.0/22RIPENo ROA
80.93.100.0/22RIPENo ROA
80.93.104.0/21RIPENo ROA
93.88.208.0/21RIPENo ROA
93.88.208.0/22RIPENo ROA
93.88.212.0/22RIPENo ROA
93.88.216.0/21RIPENo ROA
93.88.220.0/22RIPENo 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.