SOCOM-BD

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks19 · 766 IPv4 addresses
IPv6 16 prefixes (largest 2402:a940:1000::/36)
Cluster ID214474696
RegistryAPNIC
Customersfind customers using 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

Footprint over time

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

IP Ranges (19)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.112.129.0 – 103.112.129.254 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
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)

showing the 15 largest allocations

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (19 of 19)
Possible discrepancies (17)

These blocks are registered to SOCOM-BD 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.

2402:a940::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:1000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:2000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:3000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:4000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:5000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:6000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:7000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:8000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:9000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:a000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:b000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:c000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:d000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
2402:a940:e000::/36 /36 authorized for AS137542 — SAYEM ONLINE COMMUNICATION
+2 more — see the REST API

NIC Handles

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