Unolink Telecom Ltda
BGP inherited
Cluster stats
| Netblocks | 33 |
| Cluster ID | 191585491 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 2 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
3 weekly snapshots · JSON
33
0 netblocks since 2026-07-05
2026-07-05
peak 33
2026-07-12
IP Ranges (33)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.82.98/32 | Unolink Telecom | PEERINGDB | ASSIGNED | ● high |
| 138.121.116.0/22 | AS264295 | BGP | ANNOUNCED | ● high |
| 138.121.116.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 138.121.117.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 138.121.118.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 138.121.119.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 168.181.152.0/23 | AS264295 | BGP | ANNOUNCED | ● high |
| 168.181.152.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 168.181.152.0/22 | AS264295 | BGP | ANNOUNCED | ● high |
| 168.181.153.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 168.181.154.0/23 | AS264295 | BGP | ANNOUNCED | ● high |
| 168.181.154.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 168.181.155.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 170.246.16.0/23 | AS264295 | BGP | ANNOUNCED | ● high |
| 170.246.16.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 170.246.16.0/22 | AS264295 | BGP | ANNOUNCED | ● high |
| 170.246.17.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 170.246.18.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 170.246.18.0/23 | AS264295 | BGP | ANNOUNCED | ● high |
| 170.246.19.0/24 | AS264295 | BGP | ANNOUNCED | ● high |
| 187.16.194.27/32 | Unolink Telecom | PEERINGDB | ASSIGNED | ● high |
| 187.16.212.218/32 | Unolink Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::212:218/128 | Unolink Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:2::54:98/128 | Unolink Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:17::27/128 | Unolink Telecom | PEERINGDB | ASSIGNED | ● high |
| 2804:25b0::/32 | AS264295 | BGP | ANNOUNCED | ● high |
| 2804:25b0::/33 | AS264295 | BGP | ANNOUNCED | ● high |
| 2804:25b0::/34 | AS264295 | BGP | ANNOUNCED | ● high |
| 2804:25b0:4000::/34 | AS264295 | BGP | ANNOUNCED | ● high |
| 2804:25b0:8000::/34 | AS264295 | BGP | ANNOUNCED | ● high |
| 2804:25b0:8000::/33 | AS264295 | BGP | ANNOUNCED | ● high |
| 2804:25b0:c000::/34 | AS264295 | BGP | ANNOUNCED | ● high |
| 2804:25b0::/32 | UNKNOWN | LACNIC | allocated | ● medium |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(33 of 33)
Possible discrepancies (27)
These blocks are registered to Unolink Telecom Ltda 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.
| 2804:25b0::/32 /32 | authorized for AS264295 — AS264295 |
| 2804:25b0::/32 /32 | authorized for AS264295 — AS264295 |
| 2804:25b0::/33 /33 | authorized for AS264295 — AS264295 |
| 2804:25b0:8000::/33 /33 | authorized for AS264295 — AS264295 |
| 2804:25b0::/34 /34 | authorized for AS264295 — AS264295 |
| 2804:25b0:4000::/34 /34 | authorized for AS264295 — AS264295 |
| 2804:25b0:8000::/34 /34 | authorized for AS264295 — AS264295 |
| 2804:25b0:c000::/34 /34 | authorized for AS264295 — AS264295 |
| 138.121.116.0/22 /22 | authorized for AS264295 — AS264295 |
| 168.181.152.0/22 /22 | authorized for AS264295 — AS264295 |
| 170.246.16.0/22 /22 | authorized for AS264295 — AS264295 |
| 168.181.152.0/23 /23 | authorized for AS264295 — AS264295 |
| 168.181.154.0/23 /23 | authorized for AS264295 — AS264295 |
| 170.246.16.0/23 /23 | authorized for AS264295 — AS264295 |
| 170.246.18.0/23 /23 | authorized for AS264295 — AS264295 |
+12 more — see the REST API
NIC Handles
AS264295
AS264295