nobre telecom
Data as of 2026-08-09
BGP inherited
Cluster stats
| Netblocks | 5 · 1,026 IPv4 addresses |
| IPv6 | 2 prefixes (largest 2001:12f8::209:57/128) |
| Cluster ID | 219776412 |
| 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 187.16.209.57/32 | nobre telecom | PEERINGDB | ASSIGNED | ● high |
| 187.16.218.186/32 | nobre telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::209:57/128 | nobre telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::218:186/128 | nobre telecom | PEERINGDB | ASSIGNED | ● high |
| 170.254.144.0/22 | nobre telecom ltda | ARIN | ALLOCATED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (1)
These blocks are registered to nobre telecom but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 170.254.144.0/22 /22 | authorized for AS265398 — AS265398 |
NIC Handles
19605210000131
AS265398
JEPBA17
JEPBA17
JEPBA17