PE-TDP-GRS
Data as of 2026-07-26
Handle
Cluster stats
| Netblocks | 3 · 102,400 IPv4 addresses |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 214627180 |
| Registry | LACNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 190.234.0.0/17 | PE-TDP-GRS | LACNIC | REALLOCATED | ● low |
| 190.236.0.0/16 | PE-TDP-GRS | LACNIC | REALLOCATED | ● low |
| 200.60.192.0/20 | PE-TDP-GRS | LACNIC | REALLOCATED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
RPKI-inferred operator
AS6147
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
GRT2
GRT2
GRT2
GRT2
GRT2
GRT2
PE-PETD2-LACNIC
PE-PETD2-LACNIC