AS35236 AS35236 UVT Internet s.r.o.
π¨πΏOrg handle: ORG-UIS8-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
20total
12 IPv48 IPv6
IPv4 Addresses
Allocated (RIR)11,008
Announced (BGP)12,288
IPv6 Addresses
Allocated (RIR)1Γ10Β³β°
Announced (BGP)1.1Γ10Β³β°
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
50
Country
π¨πΏ CZRIR
RIPE NCCStatus
allocated
Allocated
2005-06-29
Announced Prefixes
(BGP)20|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 20
1 / 2
Allocated Prefixes
(RIR)16Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.170.176.0/21 | π¨πΏ CZ | RIPENCC | allocated |
| 37.221.117.0/24 | π¨πΏ CZ | RIPE | assigned |
| 45.91.28.0/22 | π¨πΏ CZ | RIPENCC | allocated |
| 91.241.8.0/22 | π¨πΏ CZ | RIPENCC | assigned |
| 109.205.72.0/21 | π¨πΏ CZ | RIPENCC | allocated |
| 109.205.73.0/24 | π¨πΏ CZ | RIPE | assigned |
| 185.124.80.0/22 | π¨πΏ CZ | RIPENCC | allocated |
| 185.205.136.0/22 | π¨πΏ CZ | RIPENCC | allocated |
| 185.205.137.0/24 | π¨πΏ CZ | RIPE | assigned |
| 188.92.96.0/21 | π¨πΏ CZ | RIPENCC | allocated |
1-10 of 16
1 / 2
All 20 announced prefixes of AS35236 β
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS51661 | π¨πΏALLSTARNET UVT Internet s.r.o. |
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS35236 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (6)
Networks whose own prefixes AS35236 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS35236 in the transit part of AS paths: peers, providers or customers.
- AS3257GTT BACKBONE GTT Communications12
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/35236Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35236" | jq