GARS-NET
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 80 blocks across 8 clusters |
| Cluster ID | 193827773 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.8.177.0/24 | GARS | RIPE | ASSIGNED PA | ● low |
| 77.220.210.0/23 | GARS-NET | RIPE | SUB-ALLOCATED PA | ● low |
| 185.68.146.0/23 | GARS-NET | RIPE | SUB-ALLOCATED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
RPKI-inferred operator
PJSC MegaFon
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
DUMY-RIPE
DUMY-RIPE
GARS-MNT