SEPCO

BGP inherited
Cluster stats
Netblocks6
Registered in India (3) · Saudi Arabia (3)
All fragments 14 blocks across 7 clusters
Cluster ID205271344
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 14 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
117.239.36.192/28 SEPCO APNIC ASSIGNED NON-PORTABLE ● high
117.239.37.16/28 SEPCO APNIC ASSIGNED NON-PORTABLE ● high
117.240.229.64/28 SEPCO APNIC ASSIGNED NON-PORTABLE ● high
87.101.148.10/32 SEPCO RIPE ASSIGNED PA ● low
87.101.148.50/32 SEPCO RIPE ASSIGNED PA ● low
87.101.148.51/32 SEPCO RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SEPCO” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

AB1061-AP CDN1-AP DUMY-RIPE DUMY-RIPE HK1010-AP HK1011-AP ITC-NOC-MNT LD744-AP LD745-AP LVJ1-AP LVJ3-AP MAINT-IN-DOT +2 more