AS265605 VELOCOM SA DE CV
🇲🇽Org handle: 303548
LACNICallocated
Announced Prefixes (BGP)
57total
28 IPv429 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)7,680
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)8.3×10²⁸
Announced Prefixes
(BGP)57|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARINOther IRR | 2026-10-11 | |
| Valid | ARIN | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 |
1-10 of 57
1 / 6
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.188.164.0/22 | 🇲🇽 MX | LACNIC | allocated |
| 2806:361::/32 | 🇲🇽 MX | LACNIC | allocated |
All 57 announced prefixes of AS265605 →
BGP Neighbours
(seen in AS paths)Upstreams (8)
Networks AS265605 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS265605 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/265605Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/265605" | jq