Skip to main content

AS208674

TEKITUP

==================================================

Registry

Authoritative registration data

AS number
208674
Name
TEKITUP
Organisation
==================================================
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

5

Total announced

6

Announced prefixes

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

Prefixes announced by AS208674
191.96.88.0/24 IPv4 /24 not checked
2a0c:b641:890::/44 IPv6 /44 not checked
2a0c:b641:890::/48 IPv6 /48 not checked
2a0c:b641:891::/48 IPv6 /48 not checked
2a0c:b641:899::/48 IPv6 /48 not checked
2a0c:b641:89b::/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 AS208674
Address families
BGP.Exchange - Dusseldorf 1,000 Mbps IPv6
BGP.Exchange - Paris 1,000 Mbps IPv6
LOCIX DUSSELDORF: 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 AS208674 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS208674 in AS paths

Observed upstreams
Families
AS34872 Servperso_Systems 519 1,978
v4 v6
AS211448 87 123
v4 v6
AS25091 IP-Max 5 45
v4 v6
AS8298 IPNG 2 12
v4 v6
AS34927 iFog-GmbH 2 10
v6
AS401753 1 6
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS208674 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS56662 1 5
v6
AS199854 1 5
v6
AS3214 XTOM 1 4
v6
AS34549 MEER-AS 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.