AS40966 L7GUARD-AS ZAO Web Hosting
🇷🇺Org handle: ORG-ZWH2-RIPE
L7GUARD Network
RIPE NCCallocated
Announced Prefixes (BGP)
12total
12 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)6,400
Announced (BGP)8,192
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)12|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
185.67.164.0/24MOAS | Valid | RIPE | 2026-10-11 |
185.67.165.0/24MOAS | Valid | RIPE | 2026-10-11 |
185.67.166.0/24MOAS | Valid | RIPE | 2026-10-11 |
185.67.167.0/24MOAS | Valid | RIPE | 2026-10-11 |
| Valid | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
217.112.44.0/24MOAS | Valid | RIPE | 2026-10-11 |
1-10 of 12
1 / 2
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.67.164.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 217.112.32.0/20 | 🇷🇺 RU | RIPENCC | allocated |
| 217.112.36.0/23 | 🇷🇺 RU | RIPE | assigned |
| 217.112.42.0/23 | 🇷🇺 RU | RIPE | assigned |
| 217.112.46.0/24 | 🇷🇺 RU | RIPE | assigned |
All 12 announced prefixes of AS40966 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS40966 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS40966 passes on: usually its customers.
- AS63258Web Hosting4
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 AS40966 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/40966Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/40966" | jq