Skip to main content

AS209591

FLYNETWORK

Fly Network Srl

Registry

Authoritative registration data

AS number
209591
Name
FLYNETWORK
Organisation
Fly Network Srl
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS209591
141.98.124.0/22 IPv4 /22 not checked
141.98.124.0/24 IPv4 /24 not checked
141.98.125.0/24 IPv4 /24 not checked
141.98.126.0/24 IPv4 /24 not checked
141.98.127.0/24 IPv4 /24 not checked
149.7.214.0/24 IPv4 /24 not checked
149.7.215.0/24 IPv4 /24 not checked
2a10:2980::/29 IPv6 /29 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 AS209591
Address families
MIX-IT 10,000 Mbps IPv4 · IPv6
Namex Rome: VLAN Peering 20,000 Mbps IPv4 · IPv6
PCIX 10,000 Mbps IPv4 · IPv6
VSIX: Primary 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 AS209591 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS209591 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS209591 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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