Ssmidge Technologies
Cluster stats
| Netblocks | 30 |
| Cluster ID | 193375047 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 2 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
30
0 netblocks since 2026-07-05
2026-07-05
peak 30
2026-07-06
IP Ranges (30)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 23.145.168.201/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 31.44.187.122/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 80.249.215.162/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 185.1.14.176/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 185.1.125.51/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 185.1.147.240/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 185.1.184.73/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 187.16.220.39/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 192.34.27.115/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 193.189.83.5/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 193.192.12.25/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e0::c/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e1::ea/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a506:900:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:33::a106:900:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1:0:6:900:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0:4649::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0:4742::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0:4e4c::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0:5553::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:109::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:12e::60:900/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:130::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:134::6d/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::220:39/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2404:f4c0:f70e:1980::60:900/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2602:ffb1:200:0:192:34:27:115/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2a0e:b107:2080::/44 | Ssmidge Technologies | BGP | ANNOUNCED | ● high |
| 2a13:b487:3200::6:900:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(15 of 30)
No discrepancies found among checked blocks.
NIC Handles
AS199177
AS60900