SERVLINK TELECOM LTDA - ME
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2804:3124:4000::/34) |
| All fragments | 20 blocks across 2 clusters |
| Cluster ID | 213270674 |
| Registry | BGP |
| 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 · report an issue | |
Footprint over time
5 weekly snapshots · JSON
54
-19 netblocks since 2026-07-05
2026-07-05
peak 73
2026-07-19
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2804:3124::/34 | SERVLINK TELECOM LTDA - ME | BGP | ANNOUNCED | ● low |
| 2804:3124:4000::/34 | SERVLINK TELECOM LTDA - ME | BGP | ANNOUNCED | ● 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
(2 of 2)
Possible discrepancies (2)
These blocks are registered to SERVLINK TELECOM LTDA - ME 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:3124::/34 /34 | authorized for AS264996 — AS264996 |
| 2804:3124:4000::/34 /34 | authorized for AS264996 — AS264996 |
NIC Handles
AS264996