DBS TELECOM

BGP inherited
Cluster stats
Netblocks6
Cluster ID213186218
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
6 0 netblocks since 2026-07-13
2026-07-13 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.184.144.26/32 DBS TELECOM PEERINGDB ASSIGNED ● high
187.16.213.246/32 DBS TELECOM PEERINGDB ASSIGNED ● high
200.192.111.66/32 DBS TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::213:246/128 DBS TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:13::26/128 DBS TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:14::66/128 DBS TELECOM PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
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

AS268892