TELECOM FOZ
Data as of 2026-08-16
BGP inherited
Cluster stats
| Netblocks | 4 · 3,073 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:504:0:7:0:26:2567:1/128) |
| Cluster ID | 222465398 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 64.191.233.69/32 | TELECOM FOZ | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:7:0:26:2567:1/128 | TELECOM FOZ | PEERINGDB | ASSIGNED | ● high |
| 191.37.196.0/22 | TELECOM FOZ | ARIN | ALLOCATED | ● medium |
| 177.73.96.0/21 | TELECOM FOZ | ARIN | ALLOCATED | ● low |
IPv6 ranges (1)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
Possible discrepancies (2)
These blocks are registered to TELECOM FOZ but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 177.73.96.0/21 /21 | authorized for AS262567 — AS262567 |
| 191.37.196.0/22 /22 | authorized for AS263404 — AS263404 |
NIC Handles
13222825000100
AS262567
STTEI10
STTEI10
STTEI10