AS41206 United-Telecom-HU-AS United Telecom Zartkoruen Mukodo Reszvenytarsasag
🇭🇺Org handle: ORG-UTZM1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.219.48.0/22 | 🇭🇺 HU | RIPENCC | allocated |
| 2a0b:e0c0::/29 | 🇭🇺 HU | RIPENCC | allocated |
All 4 announced prefixes of AS41206 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS41206 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (5)
Networks whose own prefixes AS41206 passes on: usually its customers.
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 AS41206 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/41206Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/41206" | jq