Serv City
ServCity
Cluster stats
| Netblocks | 20 |
| All fragments | 21 blocks across 2 clusters |
| Cluster ID | 191722013 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (20)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.18.225.193/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.233/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.0.21.62/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.0.29.94/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.0.43.29/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.1.63.54/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.1.160.124/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.1.184.173/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.1.223.11/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.1.240.11/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 185.1.240.109/32 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7f::c:62/128 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b7::a520:7994:1/128 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:115:1::1:29/128 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:12a::11/128 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:12a::109/128 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:134::ac/128 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::225:193/128 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:233/128 | ServCity | PEERINGDB | ASSIGNED | ● high |
| 2a10:ccc2:a0::/48 | Servcity | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
40.0%
of checked blocks have valid RPKI ROA coverage
(8 of 20)
Possible discrepancies (1)
These blocks are registered to ServCity but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a10:ccc2:a0::/48 /48 | authorized for AS207994 — Blockchain Creek B.V. |
NIC Handles
AS207994
Blockchain-creek-MNT
DUMY-RIPE
DUMY-RIPE