AS42310 IEDR IE Domain Registry CLG
🇮🇪Org handle: ORG-IDRL2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
9total
6 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)2,560
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)3.6×10²⁴
Announced Prefixes
(BGP)9|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.72.72.0/21 | 🇮🇪 IE | RIPENCC | allocated |
| 2a01:4b0::/32 | 🇮🇪 IE | RIPENCC | allocated |
All 9 announced prefixes of AS42310 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS42310 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS42310 passes on: usually its customers.
- AS1921RCODEZERO ANYCAST SEC1 TLD Ipcom1
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 AS42310 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/42310Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/42310" | jq