Skip to main content

AS28768

XSALTO-AS

Alpilink Cloud S.A.S.

Registry

Authoritative registration data

AS number
28768
Name
XSALTO-AS
Organisation
Alpilink Cloud S.A.S.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS28768
81.200.32.0/21 IPv4 /21 not checked
81.200.40.0/21 IPv4 /21 not checked
185.124.216.0/22 IPv4 /22 RPKI valid
2a00:1bb0::/32 IPv6 /32 RPKI valid
2a03:9060::/32 IPv6 /32 RPKI valid

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 AS28768
Address families
France-IX AURA: lyonix-peering 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 AS28768 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS28768 in AS paths

Observed upstreams
Families
AS30781 JAGUAR-AS 616 1,848
v4 v6
AS39801 FRANCE-IX-L3P 68 217
v4
AS3215 AS3215 17 47
v4 v6
AS6939 HURRICANE 26 27
v4
AS34019 HIVANE 6 20
v4
AS43100 FRANCE-IX-LYN-RS 9 18
v4
AS174 COGENT-174 8 16
v4
AS35625 EUROFIBER-FRANCE 2 4
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS28768 in AS paths

Observed downstreams
Families
AS35667 XSALTO35667 269 340
v4
AS3215 AS3215 44 177
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS2027 MilkyWan 2 4
v4
AS29075 IELO 2 4
v4
AS56987 AS-ABACLOUDA 2 4
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.