Solutions by STC

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks7
IPv6 4 prefixes (largest 2001:16a0:1:201d::/64)
Registered in BH (1) · Germany (1) · KW (1)
All fragments 10 blocks across 2 clusters
Cluster ID213729673
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

Footprint over time

6 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-26

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.69.248.26/32 Solutions by STC PEERINGDB ASSIGNED ● high
185.1.8.118/32 Solutions by STC PEERINGDB ASSIGNED ● high
194.54.136.3/32 Solutions by STC PEERINGDB ASSIGNED ● high
2001:7f8:73::23c3:0:1/128 Solutions by STC PEERINGDB ASSIGNED ● high
2001:1a40:10:0:a500:91:55:1/128 Solutions by STC PEERINGDB ASSIGNED ● high
2a0c:c9c0::3/128 Solutions by STC PEERINGDB ASSIGNED ● high
2001:16a0:1:201d::/64 Solutions-by-stc RIPE ALLOCATED-BY-LIR ● low

IPv6 ranges (4)

Network trust

what's this?
RPKI hygiene: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS9155 DUMY-RIPE DUMY-RIPE SAUDINET-STC