SOCOM-BD

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks22 · 1,024 IPv4 addresses
IPv6 16 prefixes (largest 2402:a940:1000::/36)
Record ID241862157
RegistryAPNIC
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (22)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.112.128.0/24 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
103.112.129.0 – 103.112.129.254 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
103.112.129.0/24 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
103.112.130.0/24 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
103.112.131.0 – 103.112.131.254 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
103.112.131.0/24 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:1000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:2000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:3000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:4000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:5000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:6000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:7000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:8000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:9000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:a000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:b000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:c000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:d000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:e000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low
2402:a940:f000::/36 SOCOM-BD APNIC ALLOCATED NON-PORTABLE ● low

IPv6 ranges (16)

Footprint over time

13 weekly snapshots · JSON
22 +3 netblocks since 2026-07-05
2026-07-05 peak 22 2026-09-20

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (22 of 22)
RPKI-inferred operator SAYEM ONLINE COMMUNICATION
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

AS2626-AP MAINT-SOCOM-BD SOCA1-AP SOCA1-AP