AS263681 IPTP NETWORKS S.A.C.
π΅πͺOrg handle: 285276
LACNICallocated
Announced Prefixes (BGP)
6total
4 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)7.9Γ10Β²βΈ
Announced (BGP)7.9Γ10Β²βΈ
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
10
Country
π΅πͺ PERIR
LACNICStatus
allocated
Allocated
2015-07-24
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-11 | |
| Valid | LACNIC | 2026-10-11 | |
| Valid | LACNIC | 2026-10-11 | |
| Valid | LACNIC | 2026-10-11 | |
| Valid | LACNIC | 2026-10-11 | |
| Valid | LACNIC | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.236.172.0/23 | π΅πͺ PE | LACNIC | allocated |
| 138.204.12.0/22 | π΅πͺ PE | LACNIC | allocated |
| 2803:c240::/32 | π΅πͺ PE | LACNIC | allocated |
All 6 announced prefixes of AS263681 β
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS263681 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 AS263681 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/263681Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/263681" | jq