A.M.A TELECOM
Cluster stats
| Netblocks | 17 |
| Cluster ID | 191320898 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.83.176/32 | A.M.A TELECOM | PEERINGDB | ASSIGNED | ● high |
| 132.255.160.0/23 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 132.255.160.0/24 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 132.255.161.0/24 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 132.255.163.0/24 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 143.0.8.0/24 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 143.0.9.0/24 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 143.0.10.0/24 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 143.0.10.0/23 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 143.0.11.0/24 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 2001:12f8:0:2::55:176/128 | A.M.A TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2804:20d8::/32 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 2804:20d8::/33 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 2804:20d8:11d::/48 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 2804:20d8:8000::/33 | A.M.A TELECOM | BGP | ANNOUNCED | ● high |
| 143.0.11.240/29 | UNKNOWN | LACNIC | reallocated | ● medium |
| 2804:20d8::/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
(17 of 17)
No discrepancies found among checked blocks.
NIC Handles
AS264516
AS264516