Skip to main content

AS209652

tzepesh

Upstreams:

Registry

Authoritative registration data

AS number
209652
Name
tzepesh
Organisation
Upstreams:
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

4

Total announced

4

Announced prefixes

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

Prefixes announced by AS209652
2a0a:6040:2400::/40 IPv6 /40 RPKI valid
2a06:a005:2ad0::/44 IPv6 /44 not checked
2a06:a005:b61::/48 IPv6 /48 not checked
2a0c:9a40:85a0::/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

Internet Exchange memberships listed for AS209652
Address families
4b42 Internet Exchange Point: Switzerland — IPv6
FogIXP 1,000 Mbps IPv6
ixFabric - Amsterdam 1,000 Mbps IPv6
ixFabric - Barcelona 1,000 Mbps IPv6
ixFabric - Rio de Janeiro 1,000 Mbps 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 AS209652 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS209652 in AS paths

Observed upstreams
Families
AS34927 iFog-GmbH 141 694
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS209652 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35708 ASN-4IXP 1 4
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.