AS35539 INFOLINK-T-AS Information and Communication Technologies LLC
๐ท๐บOrg handle: ORG-OIT1-RIPE
Moscow, Russia
RIPE NCCallocated
Announced Prefixes (BGP)
17total
16 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)98,304
Announced (BGP)116,736
IPv6 Addresses
Allocated (RIR)7.9ร10ยฒโธ
Announced (BGP)7.9ร10ยฒโธ
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
5
Country
๐ท๐บ RURIR
RIPE NCCStatus
allocated
Allocated
2005-08-30
Announced Prefixes
(BGP)17|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)14Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.134.192.0/21 | ๐ท๐บ RU | RIPENCC | assigned |
| 46.160.192.0/18 | ๐ท๐บ RU | RIPENCC | allocated |
| 93.95.160.0/21 | ๐ท๐บ RU | RIPENCC | allocated |
| 93.95.160.0/22 | ๐ท๐บ RU | RIPE | assigned |
| 93.95.164.0/22 | ๐ท๐บ RU | RIPE | assigned |
| 93.123.128.0/17 | ๐ท๐บ RU | RIPENCC | allocated |
| 93.123.128.0/18 | ๐ท๐บ RU | RIPE | assigned |
| 93.123.192.0/18 | ๐ท๐บ RU | RIPE | assigned |
| 95.131.208.0/21 | ๐ท๐บ RU | RIPENCC | allocated |
| 95.131.208.0/22 | ๐ท๐บ RU | RIPE | assigned |
1-10 of 14
1 / 2
All 17 announced prefixes of AS35539 โ
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS35539 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS35539 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS35539 in the transit part of AS paths: peers, providers or customers.
- AS202984Team Host Chernyshov Aleksandr Aleksandrovich1
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 AS35539 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/35539Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35539" | jq