AS265579 TELECOMUNICACIONES OTOMIES
🇲🇽Org handle: 359743
LACNICallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.174.168.0/22 | 🇲🇽 MX | LACNIC | allocated |
| 2806:333::/32 | 🇲🇽 MX | LACNIC | allocated |
All 5 announced prefixes of AS265579 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS265579 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS265579 passes on: usually its customers.
- AS270163ELEAZAR ORTIZ CRUZ1
ASPA
No ASPA
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS265579 should publish an ASPA object
- IPv4 transfers in the LACNIC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/265579Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/265579" | jq