AS201830 ETERNITY-CLOUD-MNT Eternity Cloud Limited
🇬🇧Org handle: ORG-ECL85-RIPE
-----BEGIN TOKEN-----b642d41014a7927a5d451f5b47f8bb9d9977c1dce59c16a456c11715d50ed67150270c7bd7e2ea3e4251d31b70b457e7ac836510189d6bd6cced3ac92f029dd4-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 82.41.36.0/24 | 🇪🇺 EU | RIPE | assigned |
All 1 announced prefix of AS201830 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201830 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
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 AS201830 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/201830Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201830" | jq