BYFLY
Cluster stats
| Netblocks | 21 |
| All fragments | 10,206 blocks across 5,404 clusters |
| Cluster ID | 192040076 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (21)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 82.209.202.16/30 | BYFLY | RIPE | ASSIGNED PA | ● low |
| 93.84.104.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 93.84.109.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 93.84.120.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 93.84.126.0/23 | BYFLY | RIPE | ASSIGNED PA | ● low |
| 93.85.82.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 93.85.92.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 93.85.93.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 93.85.94.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 93.85.95.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 93.85.128.0/18 | BYFLY | RIPE | ASSIGNED PA | ● low |
| 178.124.156.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 178.124.172.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 178.124.176.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 178.124.190.0/24 | BYFLY | RIPE | ASSIGNED PA | ● low |
| 194.158.201.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 194.158.202.0/24 | BYFLY | RIPE | ASSIGNED PA | ● low |
| 194.158.203.0/24 | BYFLY | RIPE | ASSIGNED PA | ● low |
| 194.158.204.0/24 | BYFLY | RIPE | ASSIGNED PA | ● low |
| 194.158.205.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
| 194.158.210.0/24 | BYFLY | RIPE | LIR-PARTITIONED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(21 of 21)
RPKI-inferred operator
Republican Unitary Telecommunication Enterprise Beltelecom
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
AS6697-MNT
BYBF-RIPE
BYGF-RIPE
BYGO-RIPE
BYVI-RIPE
DUMY-RIPE
DUMY-RIPE
MGTS-RIPE
VITEBSKOBLTELECOM-MNT