Service-Terminal-Rotterdam
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 22 blocks across 2 clusters |
| Cluster ID | 208985433 |
| 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 | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.177.233.56/29 | Service-Terminal-Rotterdam | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Service Terminal” — 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.
- Service Terminal Media LLC 21 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.
- Qtel-use-ITCC-HQ1-DST-Qtel-Service-Terminal-16055 via Ooredoo Q.S.C. sub-allocation
- SPESTERMINALSERVICESRL sub-allocation
- TERMINALGASSERVICE via MTS PJSC sub-allocation
- TERMINALSERVICES-NET9 via MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KG sub-allocation
- TERMINALSERVICES-NET11 via MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KG sub-allocation
- Terminal-Service-WAN via PJSC MegaFon sub-allocation
- Terminal-Service-LAN via PJSC MegaFon sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
NL-BBNET-MNT