AS31368 PROMOCOM-NET ASTELNET s.r.o.
🇨🇿Org handle: ORG-AS64-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
5 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.173.156.0/22 | 🇨🇿 CZ | RIPENCC | allocated |
| 185.173.156.0/24 | 🇷🇺 RU | RIPE | assigned |
All 5 announced prefixes of AS31368 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS31368 hands its own prefixes to: transit providers, or peers at an exchange.
- AS28917Fiord Networks, UAB5
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 AS31368 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/31368Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/31368" | jq