AS57723 MEDIATELEKOM Media Telekom Sp. z o.o.
🇵🇱Org handle: ORG-MTSZ2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
4 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)1,792
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.233.228.0/23 | 🇵🇱 PL | RIPENCC | assigned |
| 185.186.16.0/22 | 🇵🇱 PL | RIPENCC | allocated |
| 194.31.40.0/23 | 🇵🇱 PL | RIPENCC | assigned |
| 2001:1a68:21::/48 | 🇵🇱 PL | RIPE | assigned |
| 2a0b:ca80::/32 | 🇵🇱 PL | RIPENCC | allocated |
All 6 announced prefixes of AS57723 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS57723 hands its own prefixes to: transit providers, or peers at an exchange.
- AS3257GTT BACKBONE GTT Communications6
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 AS57723 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/57723Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/57723" | jq