Skip to main content

AS208236

LiHAS

Adrian Reyer

Registry

Authoritative registration data

AS number
208236
Name
LiHAS
Organisation
Adrian Reyer
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

7

Total announced

11

Announced prefixes

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

Prefixes announced by AS208236
45.150.152.0/24 IPv4 /24 not checked
45.150.153.0/24 IPv4 /24 not checked
45.150.154.0/24 IPv4 /24 RPKI valid
45.150.155.0/24 IPv4 /24 RPKI valid
2a0f:d600::/30 IPv6 /30 RPKI valid
2a0f:d606::/32 IPv6 /32 RPKI valid
2a0f:d600::/48 IPv6 /48 not checked
2a0f:d600:ffff::/48 IPv6 /48 RPKI valid
2a0f:d604:153::/48 IPv6 /48 RPKI valid
2a0f:d604:154::/48 IPv6 /48 RPKI valid
2a0f:d604:155::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS208236
Address families
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

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 AS208236 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS208236 in AS paths

Observed upstreams
Families
AS56382 VSERVERLTD 263 1,202
v4 v6
AS8881 VERSATEL 360 1,108
v4 v6
AS30823 AUROLOGIC 367 722
v4 v6
AS206499 LOCIX 136 667
v4 v6
AS6939 HURRICANE 17 33
v4
AS25091 IP-Max 3 26
v4 v6
AS14840 ASN14840 2 10
v4
AS401753 BIXCE 1 6
v4 v6
AS48646 STEFAN6 1 4
v6
AS263444 ASN263444 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS208236 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

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.