AS200558 CORENET Core Network Services FZE
🇦🇪Org handle: ORG-CNSF2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
1 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)3.1×10²⁶
Announced (BGP)3.6×10²⁴
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | 2026-10-11 | |
| Valid | ARINOther IRR | 2026-10-11 | |
| Valid | ARINOther IRR | 2026-10-11 | |
| Valid | Other IRRRIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 194.117.69.0/24 | 🇳🇱 NL | RIPENCC | allocated |
| 194.117.69.0/25 | 🇦🇪 AE | RIPE | assigned |
| 194.117.69.128/25 | 🇦🇪 AE | RIPE | assigned |
| 2a0f:85c1:e42::/48 | 🇦🇪 AE | RIPE | assigned |
| 2a14:67c2:c000::/40 | 🇦🇪 AE | RIPE | assigned |
All 4 announced prefixes of AS200558 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200558 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8849MELBICOM EU Melbikomas UAB4
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 AS200558 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/200558Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200558" | jq