AS43341 MDLINK MDlink online service center GmbH
🇩🇪Org handle: ORG-Mosc1-RIPE
MDlink online service center GmbH
RIPE NCCallocated
Announced Prefixes (BGP)
14total
10 IPv44 IPv6
IPv4 Addresses
Allocated (RIR)53,504
Announced (BGP)53,504
IPv6 Addresses
Allocated (RIR)1.9×10³⁰
Announced (BGP)1.9×10³⁰
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
20
Country
🇩🇪 DERIR
RIPE NCCStatus
allocated
Allocated
2007-07-17
Routing hygiene
Score 5/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 46/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 14 announced prefixes, updated daily (2026-10-26). How the score works · RPKI explained
Announced Prefixes
(BGP)14|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 |
1-10 of 14
1 / 2
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.141.38.0/23 | 🇩🇪 DE | RIPENCC | allocated |
| 77.83.176.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 88.150.0.0/17 | 🇩🇪 DE | RIPENCC | allocated |
| 95.156.192.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 185.188.120.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 193.26.123.0/24 | 🇩🇪 DE | RIPENCC | assigned |
| 194.45.154.0/24 | 🇩🇪 DE | RIPENCC | assigned |
| 194.113.144.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 213.211.192.0/18 | 🇩🇪 DE | RIPENCC | allocated |
| 2a03:5080::/32 | 🇩🇪 DE | RIPENCC | allocated |
1-10 of 13
1 / 2
All 14 announced prefixes of AS43341 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS200570 | 🇩🇪KID_Magdeburg Kommunale Informationsdienste Magdeburg GmbH |
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS43341 hands its own prefixes to: transit providers, or peers at an exchange.
Abuse Contact
+31205354444
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/43341Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/43341" | jq