bgpreport

Network · data from 2026-11-12

AS48587 net-0x2a-as PE Zharkov Mukola Mukolayovuch

Registry name: net-0x2a-as PE Zharkov Mukola Mukolayovuch, UA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48587, 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.211.118.0/32 No ROA Nonecovered by 91.211.118.0/24 2 0%low visibility 6
91.211.116.0/24 No ROA RIR databaseRIPE 671 100% 68
91.211.117.0/24 No ROA RIR databaseRIPE 671 100% 68
91.211.119.0/24 No ROA RIR databaseRIPE 671 100% 68
91.211.118.0/24 No ROA RIR databaseRIPE 668 99% 67

AS-SET

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

  • ROA: none5
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none91.211.118.0/32No ROA covers it. Add a ROA for AS48587, maxLength 32.2 of 673
Route object: none91.211.118.0/32No route object for it. A route object for 91.211.118.0/24 with origin AS48587 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48587 in the RIR database for the space.2 of 673
ROA: none91.211.116.0/24No ROA covers it. Add a ROA for AS48587, maxLength 24.671 of 673
ROA: none91.211.117.0/24No ROA covers it. Add a ROA for AS48587, maxLength 24.671 of 673
ROA: none91.211.119.0/24No ROA covers it. Add a ROA for AS48587, maxLength 24.671 of 673
ROA: none91.211.118.0/24No ROA covers it. Add a ROA for AS48587, maxLength 24.668 of 673

Route objects not announced

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

91.211.116.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.