AS44922 MEDYABIM-AS Emre Erim trading as Medyabim Datacenter
🇹🇷Org handle: ORG-MIH2-RIPE
-----BEGIN TOKEN-----f3b97f26c1a0fb19c7d1f16f6fed5d40c0a4c7e632138b8519697d73cf69a6f65ef96717bf8cfea2ac1bff5411af0b10bae739700c90940de0a9b8e780e03aae-----END TOKEN-----
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Routing hygiene
Score 10/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
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 1 announced prefix, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-24 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.247.116.0/24 | 🇹🇷 TR | RIPE | assigned |
All 1 announced prefix of AS44922 →
Upstream Providers(1)
| ASN | Name |
|---|---|
| AS16276 | 🇫🇷OVH OVH SAS |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS44922 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
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
- 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/44922Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/44922" | jq