PERSIS TELECOM
BGP inherited
Cluster stats
| Netblocks | 16 |
| Registered in | Brazil (7) · United States (1) |
| Cluster ID | 208801515 |
| Registry | PEERINGDB |
| Customers | find 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 | |
Footprint over time
5 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-19
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.184.146.142/32 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 64.191.232.78/32 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 187.16.201.5/32 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 187.16.208.148/32 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 187.16.212.195/32 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 200.219.141.88/32 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 200.219.144.3/32 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 200.219.144.46/32 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:7::f0/128 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::208:148/128 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::212:195/128 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:4::142/128 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:5::88/128 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:7::3/128 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:7::46/128 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:24::5/128 | PERSIS TELECOM | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
87.5%
of checked blocks have valid RPKI ROA coverage
(14 of 16)
No discrepancies found among checked blocks.
NIC Handles
AS14282