Skip to main content

AS209915

TRIVAGO-IDC

trivago N.V.

Registry

Authoritative registration data

AS number
209915
Name
TRIVAGO-IDC
Organisation
trivago N.V.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

2

Total announced

3

Announced prefixes

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

Prefixes announced by AS209915
212.119.5.0/24 IPv4 /24 not checked
2a0b:1300:81dc::/48 IPv6 /48 not checked
2a0b:1306:1dc::/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 AS209915 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS209915 in AS paths

Observed upstreams
Families
AS2914 NTT-DATA-2914 201 548
v4 v6
AS35548 SMARTTERRA-AS 146 431
v4 v6
AS24482 SGGS-AS-AP 2 26
v4 v6
AS24961 MYLOC-AS 2 6
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS209915 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
AS25220 GLOBALNOC-AS 1 3
v4 v6
AS50629 LWLCOM 1 3
v4 v6
AS51185 MAINSTREAMING-AS 1 3
v4 v6
AS205112 PHILUNET 1 3
v4 v6
AS1828 UNITAS 1 1
v4

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.