METROPORT Sp. z o.o.
METROPORT
BGP inherited
Cluster stats
| Netblocks | 6 · 511 IPv4 addresses |
| All fragments | 10 blocks across 2 clusters |
| Cluster ID | 209616017 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-19
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.216.40.229/32 | METROPORT | PEERINGDB | ASSIGNED | ● high |
| 185.1.4.34/32 | METROPORT | PEERINGDB | ASSIGNED | ● high |
| 195.43.72.0/23 | METROPORT | RIPE | ASSIGNED PI | ● high |
| 195.149.232.241/32 | METROPORT | PEERINGDB | ASSIGNED | ● high |
| 195.182.218.121/32 | METROPORT | PEERINGDB | ASSIGNED | ● high |
| 212.91.0.96/32 | METROPORT | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “METROPORT” — 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.
- METROPORT Sp. z o.o. 4 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.
- METROPORTLOGISTIC-TMNET via TM TECHNOLOGY SERVICES SDN BHD sub-allocation
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
No discrepancies found among checked blocks.
NIC Handles
AS197091
DUMY-RIPE
DUMY-RIPE
MNT-INSITE-SPZOO
ORG-MSzo11-RIPE
RIPE-NCC-END-MNT