Skip to main content

AS200365

Possibly-Lizards

Possibly Lizards Limited

Registry

Authoritative registration data

AS number
200365
Name
Possibly-Lizards
Organisation
Possibly Lizards Limited
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

2

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS200365
2a0b:6b86:a00::/40 IPv6 /40 not checked
2a0b:6b86:aff::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS200365 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS200365 in AS paths

Observed upstreams
Families
AS50673 Serverius-as 303 615
v4 v6
AS6939 HURRICANE 120 162
v6
AS39351 ESAB-AS 1 1
v6
AS58057 SECUREBIT 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS200365 in AS paths

Observed downstreams
Families
AS202562 APERTURE-NETWORKS 134 412
v4 v6
AS203729 igloo22225 32 37
v6

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v6
AS24961 MYLOC-AS 1 1
v6
AS25091 IP-Max 1 1
v6
AS34019 HIVANE 1 1
v6
AS56662 EUTPNET 1 1
v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.