Milecom LLC
BGP inherited
Cluster stats
| Netblocks | 8 |
| Registered in | Russia (2) · Germany (1) · Netherlands (1) |
| All fragments | 9 blocks across 2 clusters |
| Cluster ID | 213184364 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-19
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.81.196.20/32 | Milecom LLC | PEERINGDB | ASSIGNED | ● high |
| 80.249.213.57/32 | Milecom LLC | PEERINGDB | ASSIGNED | ● high |
| 91.221.181.29/32 | Milecom LLC | PEERINGDB | ASSIGNED | ● high |
| 185.232.60.221/32 | Milecom LLC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::beda:0:1/128 | Milecom LLC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a504:8858:1/128 | Milecom LLC | PEERINGDB | ASSIGNED | ● high |
| 2a0b:9fc0:1:0:1:3094:181:29/128 | Milecom LLC | PEERINGDB | ASSIGNED | ● high |
| 2a0d:e180::60:221/128 | Milecom LLC | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Milecom” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- Milecom-2 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- LASTMILECOM-NET via GLOBALCONNECT AS sub-allocation
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(4 of 8)
No discrepancies found among checked blocks.
NIC Handles
AS48858