AS44927 Telecom-MPK LLC Telecom MPK
π·πΊOrg handle: ORG-LTM3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
11total
11 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)6,656
Announced (BGP)7,424
IPv6 Addresses
Allocated (RIR)7.9Γ10Β²βΈ
Announced (BGP)0
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
5
Country
π·πΊ RURIR
RIPE NCCStatus
allocated
Allocated
2008-04-03
Announced Prefixes
(BGP)11|
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 | |
| No ROA | RIPE | 2026-10-11 |
1-10 of 11
1 / 2
Allocated Prefixes
(RIR)9Prefix | Country | RIR | Status |
|---|---|---|---|
| 62.84.104.0/21 | π·πΊ RU | RIPENCC | allocated |
| 91.203.80.0/22 | π·πΊ RU | RIPENCC | assigned |
| 91.224.76.0/23 | π·πΊ RU | RIPENCC | assigned |
| 146.120.89.0/24 | π·πΊ RU | RIPE | assigned |
| 146.120.96.0/24 | π·πΊ RU | RIPE | assigned |
| 185.48.36.0/22 | π·πΊ RU | RIPENCC | allocated |
| 192.162.250.0/23 | π·πΊ RU | RIPENCC | assigned |
| 193.201.88.0/22 | π·πΊ RU | RIPENCC | assigned |
| 2a03:c440::/32 | π·πΊ RU | RIPENCC | allocated |
All 11 announced prefixes of AS44927 β
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS44927 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS44927 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/44927Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/44927" | jq