Skip to main content

AS8554

ATSAT

ATSAT Autonomous System

Registry

Authoritative registration data

AS number
8554
Name
ATSAT
Organisation
ATSAT Autonomous System
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

1

Total announced

10

Announced prefixes

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

Prefixes announced by AS8554
82.97.0.0/18 IPv4 /18 not checked
82.97.0.0/19 IPv4 /19 not checked
185.52.32.0/22 IPv4 /22 not checked
193.41.72.0/22 IPv4 /22 not checked
82.97.32.0/22 IPv4 /22 not checked
82.97.36.0/22 IPv4 /22 not checked
194.103.215.0/24 IPv4 /24 not checked
195.234.46.0/24 IPv4 /24 not checked
91.223.22.0/24 IPv4 /24 not checked
2001:1b38::/32 IPv6 /32 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 AS8554
Address families
Equinix Paris: Equinix IX - PA Metro 1,000 Mbps IPv4 · IPv6
France-IX Paris 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 AS8554 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

33 networks seen before AS8554 in AS paths

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS8554 in AS paths

Observed downstreams
Families
AS204818 HOSTEUR-NET-CORE 264 333
v4
AS200435 7 19
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

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