AS39841 NETGSM NETGSM Iletisim ve Bilgi Teknolojileri A.S.
🇹🇷Org handle: ORG-NIVB1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,792
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.88.4.0/22 | 🇹🇷 TR | RIPENCC | allocated |
| 185.88.4.0/24 | 🇹🇷 TR | RIPE | assigned |
| 185.88.6.0/24 | 🇹🇷 TR | RIPE | assigned |
| 185.88.7.0/24 | 🇹🇷 TR | RIPE | assigned |
| 2a03:7d20::/32 | 🇹🇷 TR | RIPENCC | allocated |
All 3 announced prefixes of AS39841 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS39841 hands its own prefixes to: transit providers, or peers at an exchange.
- AS9121TTNet Turk Telekomunikasyon Anonim Sirketi3
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 AS39841 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/39841Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39841" | jq