AS16223 COLUMBUS-PE-TE MAXNET TELECOM, LTD
🇺🇦Org handle: ORG-MTL12-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
13total
12 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)69,888
Announced (BGP)135,936
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 3/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
4
diversity 73/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 13 announced prefixes, updated daily (2026-10-27). How the score works · RPKI explained
Announced Prefixes
(BGP)13|
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 13
1 / 2
Allocated Prefixes
(RIR)8Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.58.0.0/19 | 🇺🇦 UA | RIPE | assigned |
| 5.58.32.0/19 | 🇺🇦 UA | RIPE | assigned |
| 5.58.64.0/19 | 🇺🇦 UA | RIPE | assigned |
| 5.58.96.0/19 | 🇺🇦 UA | RIPE | assigned |
| 5.58.128.0/17 | 🇺🇦 UA | RIPE | assigned |
| 185.53.79.0/24 | 🇺🇦 UA | RIPENCC | allocated |
| 217.196.160.0/20 | 🇺🇦 UA | RIPENCC | allocated |
| 2a00:1210:fffd::/48 | 🇺🇦 UA | RIPE | assigned |
All 13 announced prefixes of AS16223 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS208979 | 🇺🇦CANADA-TE-UA-AS Canada Network Group LLC |
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS16223 hands its own prefixes to: transit providers, or peers at an exchange.
Transfer History
Registry transfers of AS16223 between organisations.
- AS16223Transfer ·
- AS16223Transfer ·
- AS16223Transfer ·
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/16223Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/16223" | jq