AS200365 Possibly-Lizards Possibly Lizards Limited
🇬🇧Org handle: ORG-PLL7-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
0 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)3×10²⁶
Announced (BGP)3.1×10²⁶
Routing hygiene
Score 5/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
2
diversity 50/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 2 announced prefixes, updated daily (2026-10-26). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-24 | |
| Valid | - | 2026-10-24 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0b:6b86:a00::/40 | 🇬🇧 GB | RIPE | assigned |
All 2 announced prefixes of AS200365 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS200365 hands its own prefixes to: transit providers, or peers at an exchange.
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
- 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/200365Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200365" | jq