Skip to main content

AS199669

ATLEX-AS

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

Registry

Authoritative registration data

AS number
199669
Name
ATLEX-AS
Organisation
-----------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

6

Total announced

16

Announced prefixes

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

Prefixes announced by AS199669
91.109.200.0/21 IPv4 /21 not checked
185.10.44.0/22 IPv4 /22 not checked
185.71.196.0/22 IPv4 /22 not checked
185.195.170.0/23 IPv4 /23 not checked
46.29.118.0/23 IPv4 /23 not checked
109.196.166.0/24 IPv4 /24 not checked
170.168.21.0/24 IPv4 /24 not checked
185.10.44.0/24 IPv4 /24 not checked
194.38.10.0/24 IPv4 /24 not checked
194.38.11.0/24 IPv4 /24 not checked
2a11:2084::/32 IPv6 /32 not checked
2a11:8305::/32 IPv6 /32 not checked
2a11:aac4::/32 IPv6 /32 not checked
2a11:c107::/32 IPv6 /32 not checked
2a03:ec0:1::/48 IPv6 /48 not checked
2a03:ec0::/48 IPv6 /48 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 AS199669
Address families
GNM-IX 10,000 Mbps IPv4 · IPv6
Global-IX 10,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4 · IPv6
MSK-IX Saint-Petersburg: MSK-IX Saint-Petersburg peering network 20,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 AS199669 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

23 networks seen before AS199669 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 214 1,820
v4 v6
AS31500 149 1,073
v4 v6
AS29076 159 794
v4 v6
AS199599 170 355
v4 v6
AS6939 HURRICANE 49 343
v4 v6
AS51248 HOST-TELECOM 259 337
v4
AS57304 34 239
v4 v6
AS8218 NEO-ASN 3 126
v4 v6
AS25091 IP-Max 3 90
v4 v6
AS1299 TWELVE99 19 52
v6
AS47692 2 36
v4 v6
AS39351 ESAB-AS 2 24
v4 v6
AS41327 FIBERTELECOM-AS 2 23
v4 v6
AS49434 2 17
v4 v6
AS9198 1 15
v4 v6
AS60171 1 15
v4 v6
AS6663 1 14
v4 v6
AS56655 GIGAHOST 1 12
v4 v6
AS15958 1 9
v4
AS42295 TBISS-AS 1 9
v4
AS50673 3 3
v4
AS33891 CORE-BACKBONE 2 2
v4
AS62000 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS199669 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 82
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 17
v4 v6
AS3170 1 15
v4 v6
AS28910 1 15
v4 v6
AS36236 NETACTUATE 1 15
v4 v6
AS41722 1 15
v4 v6
AS205112 PHILUNET 1 15
v4 v6
AS209823 1 15
v4 v6
AS44901 1 13
v4 v6
AS13004 1 9
v4
AS28917 1 9
v4 v6
AS29049 1 9
v4
AS35598 1 9
v4
AS49673 TRUENETWORK 1 9
v4
AS51185 MAINSTREAMING-AS 1 9
v4
AS200612 GulfBridgeInternational 1 9
v4
AS208972 1 9
v4
AS199524 GCORE 1 6
v4 v6

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.