AS203647 WORLDBUS TradeZone LLC
🇬🇪Org handle: ORG-TL838-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Listed on the threat map (2026-10-09)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 181.215.15.0/24 | 🇬🇪 GE | RIPE | assigned |
| 194.135.119.0/24 | 🇦🇪 AE | RIPENCC | allocated |
| 2a12:e340::/32 | 🇬🇪 GE | RIPE | assigned |
All 3 announced prefixes of AS203647 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS203647 hands its own prefixes to: transit providers, or peers at an exchange.
- AS47810Proservice3
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 AS203647 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/203647Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203647" | jq