GEO-COM-NET
Data as of 2026-09-05
BGP inherited
This organisation
| Netblocks | 4 |
| IPv6 | 1 prefix (largest 2001:678:3ac::360/128) |
| Record ID | 232826681 |
| Registry | PEERINGDB |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.46.145.106/32 | Geo-Com | PEERINGDB | ASSIGNED | ● high |
| 2001:678:3ac::360/128 | Geo-Com | PEERINGDB | ASSIGNED | ● high |
| 79.133.218.192/26 | GEO-COM-NET | RIPE | ASSIGNED PA | ● low |
| 80.72.39.96/29 | GEO-COM-NET | RIPE | ASSIGNED PA | ● low |
IPv6 ranges (1)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
No discrepancies found among checked blocks.
NIC Handles
AS200930
DUMY-RIPE
DUMY-RIPE
ETOP-MNT