SEA TELECOM AS266445

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks10
IPv6 5 prefixes (largest 2001:12f8:0:13::151/128)
Registered in Brazil (4) · United States (1)
All fragments 12 blocks across 2 clusters
Cluster ID214585582
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 · report an issue

Footprint over time

3 weekly snapshots · JSON
10 0 netblocks since 2026-07-13
2026-07-13 peak 10 2026-07-26

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.73.1/32 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
45.184.144.151/32 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
64.191.233.113/32 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
187.16.195.25/32 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
187.16.212.109/32 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
2001:504:0:7:0:26:6445:1/128 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
2001:12f8::212:109/128 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
2001:12f8:0:9::145:1/128 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
2001:12f8:0:13::151/128 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high
2001:12f8:0:18::25/128 SEA TELECOM AS266445 PEERINGDB ASSIGNED ● high

IPv6 ranges (5)

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (8 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS266445