Skip to main content

AS218835

Dreher

Yannick Dreher

Registry

Authoritative registration data

AS number
218835
Name
Dreher
Organisation
Yannick Dreher
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 AS218835
2a0c:9a40:e100::/48 IPv6 /48 not checked
2a0c:9a40:e101::/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 AS218835 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS218835 in AS paths

Observed upstreams
Families
AS34927 iFog-GmbH 229 625
v6
AS34872 Servperso_Systems 32 81
v6
AS39351 ESAB-AS 2 4
v6
AS47498 FogIXP 2 4
v6
AS205794 RTTW-AS 1 2
v6
AS209022 Tschajera-Limited 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS218835 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8298 IPNG 1 2
v6
AS41666 PYRO-AS 1 2
v6
AS58299 OPENFACTORY-AS 1 2
v6
AS60326 DEADBEEF-AS 1 2
v6
AS209823 ENKI-AS 1 2
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.