AS207239 GiG-net LLC G&G-Telecom
🇷🇺Org handle: ORG-GA912-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 194.190.220.0/23 | 🇷🇺 RU | RIPE | assigned |
| 195.64.140.0/23 | 🇷🇺 RU | RIPENCC | assigned |
| 2001:67c:b5c::/48 | 🇷🇺 RU | RIPENCC | assigned |
All 4 announced prefixes of AS207239 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS207239 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS207239 passes on: usually its customers.
- AS219340KUSIGMA1
Other adjacent networks (1)
Adjacent to AS207239 in the transit part of AS paths: peers, providers or customers.
- AS57304RETNRU JSC "RetnNet"1
ASPA
No ASPA
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
- ASPA explainedWhy AS207239 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/207239Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/207239" | jq