Skip to main content

AS43566

tyntec

tyntec GmbH

Registry

Authoritative registration data

AS number
43566
Name
tyntec
Organisation
tyntec GmbH
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

3

Total announced

14

Announced prefixes

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

Prefixes announced by AS43566
78.110.224.0/20 IPv4 /20 not checked
178.23.24.0/21 IPv4 /21 not checked
78.110.224.0/21 IPv4 /21 not checked
78.110.232.0/21 IPv4 /21 not checked
178.23.24.0/22 IPv4 /22 not checked
178.23.28.0/22 IPv4 /22 not checked
78.110.236.0/22 IPv4 /22 not checked
78.110.232.0/24 IPv4 /24 not checked
78.110.233.0/24 IPv4 /24 not checked
78.110.234.0/24 IPv4 /24 not checked
78.110.235.0/24 IPv4 /24 not checked
2a11:7f80::/32 IPv6 /32 not checked
2a11:7f80:8000::/33 IPv6 /33 not checked
2a11:7f80::/33 IPv6 /33 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 AS43566
Address families
CNX: Internet Peering 1,000 Mbps IPv4
DE-CIX Dusseldorf: DE-CIX Dusseldorf Peering LAN 2,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 2,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 AS43566 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

49 networks seen before AS43566 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS43566 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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