AS35311 PR-TELECOM-AS PR-TELECOM Zrt.
🇭🇺Org handle: ORG-PR8-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
13total
12 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)134,144
Announced (BGP)70,656
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)13|
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 13
1 / 2
Allocated Prefixes
(RIR)17Prefix | Country | RIR | Status |
|---|---|---|---|
| 87.242.0.0/18 | 🇭🇺 HU | RIPENCC | allocated |
| 87.242.0.0/19 | 🇭🇺 HU | RIPE | assigned |
| 87.242.32.0/19 | 🇭🇺 HU | RIPE | assigned |
| 88.132.0.0/17 | 🇭🇺 HU | RIPENCC | allocated |
| 88.132.0.0/19 | 🇭🇺 HU | RIPE | assigned |
| 88.132.32.0/19 | 🇭🇺 HU | RIPE | assigned |
| 88.132.64.0/21 | 🇭🇺 HU | RIPE | assigned |
| 88.132.72.0/21 | 🇭🇺 HU | RIPE | assigned |
| 88.132.80.0/21 | 🇭🇺 HU | RIPE | assigned |
| 88.132.88.0/21 | 🇭🇺 HU | RIPE | assigned |
1-10 of 17
1 / 2
All 13 announced prefixes of AS35311 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS35311 hands its own prefixes to: transit providers, or peers at an exchange.
- AS21334ASN ONE HU 2Connect Telecommunications Infrastructure & Network Services13
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 AS35311 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/35311Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35311" | jq