REDE WORKS TELECOM

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks10 · 1,537 IPv4 addresses
IPv6 3 prefixes (largest 2804:3f0c::/40)
Record ID245999306
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
128.201.56.0/24 UNKNOWN LACNIC reassigned ● high
128.201.57.0/24 UNKNOWN LACNIC reassigned ● high
128.201.58.0/24 UNKNOWN LACNIC reassigned ● high
128.201.59.0/24 UNKNOWN LACNIC reassigned ● high
177.105.246.0/24 UNKNOWN LACNIC reassigned ● high
177.105.247.0/24 UNKNOWN LACNIC reassigned ● high
187.16.213.159/32 REDE WORKS TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::213:159/128 REDE WORKS TELECOM PEERINGDB ASSIGNED ● high
2804:3f0c::/40 UNKNOWN LACNIC reassigned ● high
2804:3f0c:f900::/40 UNKNOWN LACNIC reassigned ● high

IPv6 ranges (3)

Footprint over time

7 weekly snapshots · JSON
18 +10 netblocks since 2026-07-05
2026-07-05 peak 18 2026-10-04

Network trust

what's this?
RPKI hygiene: F how networks compare →
11.1% of checked blocks have valid RPKI ROA coverage (2 of 18)
No discrepancies found among checked blocks.

NIC Handles

AS266636 AS266636