bgpreport

Network · data from 2026-11-12

AS48082 DIALECT-NET FOP Mikhailyuk Yuri Ivanovitch

Registry name: DIALECT-NET FOP Mikhailyuk Yuri Ivanovitch, UA · not in PeeringDB

8IPv4 routes 12.5% RPKI valid · 87.5% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
7No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS48082, seen from no peer

Announced routes

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

91.210.21.0/24 No ROA Nonecovered by 91.210.20.0/23 670 100% 68
91.210.20.0/23 No ROA RIR databaseRIPE 671 100% 68
91.210.22.0/23 No ROA RIR databaseRIPE 670 100% 68
91.218.104.0/24 No ROA RIR databaseRIPE 670 100% 68
91.218.105.0/24 No ROA RIR databaseRIPE 670 100% 68
91.218.106.0/24 No ROA RIR databaseRIPE 670 100% 68
91.218.107.0/24 No ROA RIR databaseRIPE 670 100% 68
46.33.60.0/22 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS48082 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 20 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none91.210.21.0/24No ROA covers it. Add a ROA for AS48082, maxLength 24.670 of 673
Route object: none91.210.21.0/24No route object for it. A route object for 91.210.20.0/23 with origin AS48082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48082 in the RIR database for the space.670 of 673
ROA: none91.210.20.0/23No ROA covers it. Add a ROA for AS48082, maxLength 23.671 of 673
ROA: none91.210.22.0/23No ROA covers it. Add a ROA for AS48082, maxLength 23.670 of 673
ROA: none91.218.104.0/24No ROA covers it. Add a ROA for AS48082, maxLength 24.670 of 673
ROA: none91.218.105.0/24No ROA covers it. Add a ROA for AS48082, maxLength 24.670 of 673
ROA: none91.218.106.0/24No ROA covers it. Add a ROA for AS48082, maxLength 24.670 of 673
ROA: none91.218.107.0/24No ROA covers it. Add a ROA for AS48082, maxLength 24.670 of 673

Route objects not announced

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

91.210.20.0/22RIPENo ROA
91.218.104.0/22RIPENo ROA
91.218.107.0/25RIPENo ROA
91.218.107.128/25RIPENo ROA
2001:470:174::/48ARINValid
2001:470:23d::/48ARINValid
2001:470:2a1::/48ARINValid
2001:470:427::/48ARINValid
2001:470:44c::/48ARINValid
2001:470:4bd::/48ARINValid
2001:470:542::/48ARINValid
2001:470:647::/48ARINValid

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.