A.M.A TELECOM
Data as of 2026-08-23
BGP inherited
Cluster stats
| Netblocks | 4 · 2,049 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:12f8:0:2::55:176/128) |
| Cluster ID | 226994337 |
| 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 | |
Footprint over time
3 weekly snapshots · JSON
17
0 netblocks since 2026-07-05
2026-07-05
peak 17
2026-07-12
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.83.176/32 | A.M.A TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:2::55:176/128 | A.M.A TELECOM | PEERINGDB | ASSIGNED | ● high |
| 132.255.160.0/22 | A.M.A TELECOM | ARIN | ALLOCATED | ● low |
| 143.0.8.0/22 | A.M.A TELECOM | ARIN | ALLOCATED | ● low |
IPv6 ranges (1)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to A.M.A 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.
| 132.255.160.0/22 /22 | authorized for AS264516 — AS264516 |
| 143.0.8.0/22 /22 | authorized for AS264516 — AS264516 |
NIC Handles
10934244000103
ANBSO47
ANBSO47
ANBSO47
AS264516