AS201934 SATAN-NET HD Internet s.r.o.
🇨🇿Org handle: ORG-HDIN2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.22.152.0/24 | 🇨🇿 CZ | RIPE | assigned |
| 193.38.252.0/24 | 🇨🇿 CZ | RIPE | assigned |
| 2001:67c:658::/48 | 🇨🇿 CZ | RIPENCC | assigned |
All 2 announced prefixes of AS201934 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201934 hands its own prefixes to: transit providers, or peers at an exchange.
- AS49985IP4ISP Z.S.P.O2
Transfer History
Registry transfers of AS201934 between organisations.
- AS201934Transfer ·
- AS201934Transfer ·
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 AS201934 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/201934Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201934" | jq