AS213488 INOXWEB Mustafa Gunes trading as Inoxweb Datacenter ve Hosting Bilisim Teknolojileri
🇹🇷Org handle: ORG-IHBV2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)4.9×10²⁷
Announced (BGP)4.9×10²⁷
Routing hygiene
Score 38/100 · Medium riskRPKI ROA coverage
50%
1 prefix RPKI invalid
IRR route objects
50%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 50% of announced prefixes (1 of 2) have no valid ROA, 1 of them RPKI invalid
- Only one upstream seen in the AS paths of its routes
- 50% of announced prefixes (1 of 2) have no IRR route object for this ASN
Based on 2 announced prefixes, updated daily (2026-10-26). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Invalid | - | 2026-10-26 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.13.190.0/24 | 🇹🇷 TR | RIPE | assigned |
| 2a14:9401:a000::/36 | 🇹🇷 TR | RIPE | assigned |
All 2 announced prefixes of AS213488 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS213488 hands its own prefixes to: transit providers, or peers at an exchange.
- AS200010OLFE Veri Merkezi Anonim Sirketi2
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 AS213488 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/213488Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/213488" | jq