AS34700 CITYNET-AS MAXNET TELECOM, LTD
🇺🇦Org handle: ORG-MTL12-RIPE
Maxnet LLC
RIPE NCCallocated
Announced Prefixes (BGP)
17total
16 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)207,104
Announced (BGP)227,840
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Routing hygiene
Score 8/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
1
0 announced against others' ROAs, 1 own announced by others
Upstreams
3
diversity 46/100
- 1 prefix of this ASN announced by another network against its ROAs
Based on 17 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)17|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)14Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.255.160.0/20 | 🇺🇦 UA | RIPENCC | allocated |
| 31.202.0.0/16 | 🇺🇦 UA | RIPENCC | allocated |
| 31.202.0.0/17 | 🇺🇦 UA | RIPE | assigned |
| 31.202.128.0/18 | 🇺🇦 UA | RIPE | assigned |
| 31.202.192.0/18 | 🇺🇦 UA | RIPE | assigned |
| 46.160.64.0/18 | 🇺🇦 UA | RIPENCC | allocated |
| 46.160.88.0/21 | 🇺🇦 UA | RIPE | assigned |
| 79.171.120.0/21 | 🇺🇦 UA | RIPENCC | allocated |
| 82.117.248.0/22 | 🇺🇦 UA | RIPENCC | allocated |
| 85.90.222.0/24 | 🇺🇦 UA | RIPENCC | allocated |
1-10 of 14
1 / 2
All 17 announced prefixes of AS34700 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS34700 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (7)
Networks whose own prefixes AS34700 passes on: usually its customers.
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 AS34700 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/34700Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/34700" | jq