Skip to main content

AS21140

FLY-TELECOM-AS

---------------------------------------------------

Registry

Authoritative registration data

AS number
21140
Name
FLY-TELECOM-AS
Organisation
---------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS21140
185.212.88.0/23 IPv4 /23 not checked
185.212.90.0/24 IPv4 /24 not checked
185.212.91.0/24 IPv4 /24 not checked
2a0b:7540::/29 IPv6 /29 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 AS21140
Address families
GNM-IX 10,000 Mbps IPv4 · IPv6
PITER-IX Moscow: MSK_PEERING_VLAN 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 AS21140 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS21140 in AS paths

Observed upstreams
Families
AS57304 RETNRU-AS 176 629
v4 v6
AS8641 NAUKANET-AS 137 487
v4 v6
AS35598 INETCOM 148 267
v4 v6
AS25091 IP-Max 2 15
v4 v6
AS62255 BEMYLINK 5 12
v4 v6
AS9198 KAZTELECOM-AS 2 6
v4 v6
AS50673 Serverius-as 2 6
v4
AS6204 ZET-NET 1 3
v4
AS6663 TTI-NET 1 3
v4
AS15958 CETIN_doo_AS 1 3
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS21140 in AS paths

Observed downstreams
Families
AS43228 simple-tel-as 33 71
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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