W3TEL SAS

W3TEL
BGP inherited
Cluster stats
Netblocks7
All fragments 12 blocks across 2 clusters
Cluster ID209643225
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 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
37.49.237.139/32 W3TEL PEERINGDB ASSIGNED ● high
195.42.145.166/32 W3TEL PEERINGDB ASSIGNED ● high
2001:7f8:43::5:1326:1/128 W3TEL PEERINGDB ASSIGNED ● high
2001:7f8:54::1:139/128 W3TEL PEERINGDB ASSIGNED ● high
46.28.168.0/25 W3TEL RIPE ASSIGNED PA ● low
46.28.168.128/25 W3TEL_Hosting RIPE ASSIGNED PA ● low
2a02:5360::/48 W3TEL RIPE ASSIGNED ● low

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: C how networks compare →
57.1% of checked blocks have valid RPKI ROA coverage (4 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS51326 DUMY-RIPE DUMY-RIPE w3tel-mnt