AS33817 TELEGROUPUA-AS Lanet LLC
🇺🇦Org handle: ORG-LL520-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.195.74.0/23 | 🇺🇦 UA | RIPENCC | assigned |
| 91.235.68.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 193.28.184.0/24 | 🇺🇦 UA | RIPENCC | assigned |
| 194.50.81.0/24 | 🇺🇦 UA | RIPENCC | assigned |
All 4 announced prefixes of AS33817 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS33817 hands its own prefixes to: transit providers, or peers at an exchange.
- AS39608LANETUA Lanet Network4
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 AS33817 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/33817Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/33817" | jq