Skip to main content

AS206720

Airbus_Transit

Airbus

Registry

Authoritative registration data

AS number
206720
Name
Airbus_Transit
Organisation
Airbus
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

0

Total announced

11

Announced prefixes

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

Prefixes announced by AS206720
140.94.0.0/16 IPv4 /16 RPKI valid
185.187.244.0/24 IPv4 /24 not checked
185.187.245.0/24 IPv4 /24 not checked
185.187.246.0/24 IPv4 /24 not checked
185.187.247.0/24 IPv4 /24 not checked
193.56.32.0/24 IPv4 /24 RPKI valid
193.56.35.0/24 IPv4 /24 not checked
193.56.36.0/24 IPv4 /24 RPKI valid
193.56.39.0/24 IPv4 /24 RPKI valid
193.56.40.0/24 IPv4 /24 not checked
193.56.45.0/24 IPv4 /24 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 AS206720
Address families
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 AS206720 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS206720 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS206720 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.