Skip to main content

AS62269

LUKAS-SCHAUER

Lukas Schauer

Registry

Authoritative registration data

AS number
62269
Name
LUKAS-SCHAUER
Organisation
Lukas Schauer
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS62269
193.56.133.0/24 IPv4 /24 not checked
2a11:5b00::/32 IPv6 /32 not checked

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 AS62269
Address families
DE-CIX Dusseldorf: DE-CIX Dusseldorf Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX DUSSELDORF: Peering LAN 10,000 Mbps IPv4 · IPv6
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 AS62269 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS62269 in AS paths

Observed upstreams
Families
AS24961 MYLOC-AS 243 370
v4 v6
AS6939 HURRICANE 196 286
v4 v6
AS25091 IP-Max 3 8
v4 v6
AS5405 INTERDOTLINK 3 4
v4 v6
AS34927 iFog-GmbH 2 4
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 3
v4
AS401753 BIXCE 1 2
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS62269 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

13 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.