Telecentrum

TELECENTRUM
Registry
Cluster stats
Netblocks7
All fragments 8 blocks across 2 clusters
Cluster ID210355189
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
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

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.216.41.180/32 Telecentrum PEERINGDB ASSIGNED ● high
195.149.233.164/32 Telecentrum PEERINGDB ASSIGNED ● high
2001:7f8:5b::431/128 Telecentrum PEERINGDB ASSIGNED ● high
78.8.177.184/29 TELECENTRUM RIPE ASSIGNED PA ● low
81.168.172.0/29 TELECENTRUM RIPE ASSIGNED PA ● low
81.219.72.48/29 TELECENTRUM RIPE ASSIGNED PA ● low
213.241.54.112/28 TELECENTRUM RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TELECENTRUM” — 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: 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

AS206674 DUMY-RIPE DUMY-RIPE NETIA-MNT