AS42512 X-COM-AS X-COM LLC
πΊπ¦Org handle: ORG-XL37-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
26total
25 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)5,632
Announced (BGP)10,752
IPv6 Addresses
Allocated (RIR)1.2Γ10Β²β΄
Announced (BGP)1.2Γ10Β²β΄
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
5
Country
πΊπ¦ UARIR
RIPE NCCStatus
allocated
Allocated
2007-03-05
Announced Prefixes
(BGP)26|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
1-10 of 26
1 / 3
Allocated Prefixes
(RIR)8Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.43.168.0/22 | πΊπ¦ UA | RIPENCC | assigned |
| 31.43.180.0/22 | πΊπ¦ UA | RIPENCC | assigned |
| 80.70.68.0/22 | πΊπ¦ UA | RIPE | assigned |
| 91.208.65.0/24 | πΊπ¦ UA | RIPENCC | assigned |
| 91.225.120.0/22 | πΊπ¦ UA | RIPENCC | assigned |
| 193.110.76.0/22 | πΊπ¦ UA | RIPENCC | assigned |
| 194.110.126.0/24 | πΊπ¦ UA | RIPENCC | assigned |
| 2001:67c:a28::/48 | πΊπ¦ UA | RIPENCC | assigned |
All 26 announced prefixes of AS42512 β
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS42512 hands its own prefixes to: transit providers, or peers at an exchange.
ASPA
No ASPA
Abuse Contact
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 AS42512 should publish an ASPA object
- IPv4 transfers in the RIPE NCC 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/42512Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/42512" | jq