AS35223 HOI-AS Hoi Internet AG
🇱🇮Org handle: ORG-na28-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)9,216
Announced (BGP)9,216
IPv6 Addresses
Allocated (RIR)6.4×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 82.117.0.0/19 | 🇱🇮 LI | RIPENCC | allocated |
| 193.168.168.0/22 | 🇱🇮 LI | RIPENCC | allocated |
| 2a03:5480::/29 | 🇱🇮 LI | RIPENCC | allocated |
| 2a03:5480::/36 | 🇱🇮 LI | RIPE | assigned |
| 2a03:5480:1000::/36 | 🇱🇮 LI | RIPE | assigned |
All 3 announced prefixes of AS35223 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS35223 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 AS35223 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/35223Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35223" | jq