AS35032 TAHIONISP-AS LLC SIP "NIS"
🇷🇺Org handle: ORG-LS21-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
30total
18 IPv412 IPv6
IPv4 Addresses
Allocated (RIR)17,920
Announced (BGP)31,232
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)30|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
80.76.128.0/22MOAS | Valid | RIPE | 2026-10-11 |
80.76.132.0/23MOAS | Valid | RIPE | 2026-10-11 |
80.76.134.0/23MOAS | Valid | RIPE | 2026-10-11 |
80.76.136.0/23MOAS | Valid | RIPE | 2026-10-11 |
80.76.138.0/23MOAS | Valid | RIPE | 2026-10-11 |
80.76.140.0/22MOAS | 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 30
1 / 3
Allocated Prefixes
(RIR)9Prefix | Country | RIR | Status |
|---|---|---|---|
| 80.76.132.0/23 | 🇷🇺 RU | RIPE | assigned |
| 109.124.192.0/19 | 🇷🇺 RU | RIPE | assigned |
| 109.124.224.0/21 | 🇷🇺 RU | RIPE | assigned |
| 109.124.232.0/21 | 🇷🇺 RU | RIPE | assigned |
| 109.124.240.0/21 | 🇷🇺 RU | RIPE | assigned |
| 109.124.248.0/22 | 🇷🇺 RU | RIPE | assigned |
| 109.124.252.0/23 | 🇷🇺 RU | RIPE | assigned |
| 109.124.254.0/23 | 🇷🇺 RU | RIPE | assigned |
| 185.224.8.0/22 | 🇷🇺 RU | RIPENCC | allocated |
All 30 announced prefixes of AS35032 →
BGP Neighbours
(seen in AS paths)Upstreams (6)
Networks AS35032 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS35032 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/35032Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35032" | jq