Skip to main content

AS60362

alwaysdata

alwaysdata SARL

Registry

Authoritative registration data

AS number
60362
Name
alwaysdata
Organisation
alwaysdata SARL
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

3

Total announced

6

Announced prefixes

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

Prefixes announced by AS60362
185.31.40.0/22 IPv4 /22 not checked
188.72.70.0/24 IPv4 /24 not checked
78.142.219.0/24 IPv4 /24 not checked
2a00:b6e0:1::/48 IPv6 /48 not checked
2a00:b6e0:2::/48 IPv6 /48 not checked
2a00:b6e0:cdcd::/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 AS60362
Address families
Equinix Paris: Equinix IX - PA Metro 10,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 AS60362 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS60362 in AS paths

Observed upstreams
Families
AS174 COGENT-174 109 338
v4 v6
AS29075 IELO 79 268
v4 v6
AS8218 NEO-ASN 73 138
v4 v6
AS6939 HURRICANE 38 108
v4 v6
AS3257 GTT-BACKBONE 25 86
v4 v6
AS14840 ASN14840 2 16
v4 v6
AS6696 VERIXI 1 2
v4
AS7713 telkomnet-as-ap 1 2
v4
AS9009 M247 1 2
v4
AS34177 CELESTE-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS60362 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
AS24482 SGGS-AS-AP 1 12
v4 v6
AS34019 HIVANE 1 4
v4 v6
AS35280 F5 1 4
v4 v6
AS49544 i3Dnet 1 4
v4 v6
AS15547 NETPLUS 1 2
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.