Ssmidge Technologies
Data as of 2026-10-04
BGP inherited
This organisation
| Netblocks | 48 · 1,296 IPv4 addresses |
| IPv6 | 29 prefixes (largest 2602:f50c::/36) |
| Registered in | Netherlands (4) · Canada (3) · Russia (3) · Germany (2) · United States (2) · France (1) |
| Record ID | 246655218 |
| Registry | BGP |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 10 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (48)
⬇ 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.0.2.36/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 185.0.15.48/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 185.0.46.9/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.161.37/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 185.1.184.73/32 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 185.1.223.85/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:b7::a506: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:e6::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:eb::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:109::ede4:1/128 | Ssmidge Technologies | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:10f::ede4:292/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:7f8:16d::36/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:f92a:1315:2::9a/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 |
| 169.128.48.0/22 | Ssmidge Technologies | ARIN | DIRECT ALLOCATION | ● medium |
| 169.128.48.0/24 | Ssmidge Technologies | ARIN | ALLOCATION | ● medium |
| 170.39.49.0/24 | Ssmidge Technologies | ARIN | ALLOCATION | ● medium |
| 2602:2b7:420::/48 | Ssmidge Technologies | ARIN | ASSIGNMENT | ● medium |
| 2602:f50c::/36 | Ssmidge Technologies | ARIN | DIRECT ALLOCATION | ● medium |
| 2602:f9ba:a3::/48 | Ssmidge Technologies | ARIN | ALLOCATION | ● medium |
| 2602:fab8::/36 | Ssmidge Technologies | ARIN | ALLOCATION | ● medium |
IPv6 ranges (29)
Footprint over time
15 weekly snapshots · JSON
48
+18 netblocks since 2026-07-05
2026-07-05
peak 48
2026-10-04
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(24 of 48)
Possible discrepancies (1)
These blocks are registered to Ssmidge Technologies 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.
| 169.128.48.0/24 /24 | authorized for AS59920 — Lusory Limited |
NIC Handles
AS199177
AS60900
ATSPDBAST
INFRA286-ARIN
SSMID1-ARIN
SSMID1-ARIN
SSMID1-ARIN
SSMID1-ARIN
SSMID1-ARIN
SSMID1-ARIN