AS200800 ZURGANF-AS Zurganf Ltd
🇬🇧Org handle: ORG-ZA248-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
0 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)3.1×10²⁶
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | - | 2026-10-09 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0a:6040:a200::/40 | 🇺🇸 US | RIPE | assigned |
| 2a0a:6040:a201::/48 | 🇬🇧 GB | RIPE | assigned |
| 2a0a:6040:a202::/48 | 🇸🇪 SE | RIPE | assigned |
All 1 announced prefix of AS200800 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200800 hands its own prefixes to: transit providers, or peers at an exchange.
- AS34927IFog1
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 AS200800 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/200800Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200800" | jq