POLOTSK-BYFLY

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8
Cluster ID217018060
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

5 weekly snapshots · JSON
8 +2 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.209.206.61/32 POLOTSK-BYFLY RIPE ASSIGNED PA ● low
82.209.206.71/32 POLOTSK-BYFLY RIPE ASSIGNED PA ● low
86.57.183.180/32 POLOTSK-BYFLY RIPE ASSIGNED PA ● low
86.57.244.8/32 POLOTSK-BYFLY RIPE ASSIGNED PA ● low
93.85.226.39/32 POLOTSK-BYFLY RIPE ASSIGNED PA ● low
93.85.226.50/32 POLOTSK-BYFLY RIPE ASSIGNED PA ● low
93.85.226.115/32 POLOTSK-BYFLY RIPE ASSIGNED PA ● low
93.85.226.139/32 POLOTSK-BYFLY RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE VITEBSKOBLTELECOM-MNT