AS208483 WERIDATA-LLC WERIDATA LLC
🇺🇸Org handle: ORG-WL632-RIPE
-----BEGIN TOKEN-----a507bb1027b3e51a3949180591e5dd7828704b983da4ef9bf2c21fca0095fb6239365d184f225a91dae37d524492bb2d803c2fb0e5b08e9e26c1c33fdd62bfb3-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
17total
9 IPv48 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)17|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
31.57.135.0/24MOAS | Valid | Other IRRRIPE | 2026-10-11 |
| Invalid | - | 2026-10-11 | |
45.155.159.0/24MOAS | Valid | Other IRRRIPE | 2026-10-11 |
45.158.57.0/24MOAS | Valid | Other IRRRIPE | 2026-10-11 |
91.198.66.0/24MOAS | Valid | Other IRRRIPE | 2026-10-11 |
141.11.65.0/24MOAS | Valid | Other IRRRIPE | 2026-10-11 |
143.20.20.0/24MOAS | Invalid | - | 2026-10-11 |
193.160.222.0/24MOAS | Valid | Other IRRRIPE | 2026-10-11 |
213.254.170.0/24MOAS | Valid | Other IRRRIPE | 2026-10-11 |
2a14:4b80::/32MOAS | Invalid | - | 2026-10-11 |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)17Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.57.135.0/24 | 🇹🇷 TR | RIPE | assigned |
| 45.8.196.0/24 | 🇪🇺 EU | RIPE | assigned |
| 45.155.159.0/24 | 🇹🇷 TR | RIPE | assigned |
| 45.158.57.0/24 | 🇹🇷 TR | RIPE | assigned |
| 91.198.66.0/24 | 🇱🇹 LT | RIPENCC | allocated |
| 141.11.65.0/24 | 🇹🇷 TR | RIPE | assigned |
| 143.20.20.0/24 | 🇹🇷 TR | RIPE | assigned |
| 193.160.222.0/24 | 🇹🇷 TR | RIPE | assigned |
| 213.254.170.0/24 | 🇱🇹 LT | RIPENCC | allocated |
| 2a14:4b80::/32 | 🇹🇷 TR | RIPE | assigned |
1-10 of 17
1 / 2
All 17 announced prefixes of AS208483 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS208483 hands its own prefixes to: transit providers, or peers at an exchange.
- AS44547NetundWeb TELEKOMUNIKASYON TICARET LIMITED SIRKETI17
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 AS208483 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/208483Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/208483" | jq