Skip to main content

AS205638

TM-AS-MSK

"TBANK" JSC

Registry

Authoritative registration data

AS number
205638
Name
TM-AS-MSK
Organisation
"TBANK" JSC
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

23

IPv6 prefixes

0

Total announced

23

Announced prefixes

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

Prefixes announced by AS205638
185.211.156.0/22 IPv4 /22 not checked
185.211.158.0/23 IPv4 /23 not checked
212.233.84.0/23 IPv4 /23 not checked
212.233.86.0/23 IPv4 /23 not checked
45.137.112.0/23 IPv4 /23 not checked
157.22.224.0/24 IPv4 /24 not checked
157.22.225.0/24 IPv4 /24 not checked
157.22.226.0/24 IPv4 /24 not checked
157.22.227.0/24 IPv4 /24 not checked
185.211.156.0/24 IPv4 /24 not checked
185.211.158.0/24 IPv4 /24 not checked
185.211.159.0/24 IPv4 /24 not checked
193.143.64.0/24 IPv4 /24 not checked
193.143.65.0/24 IPv4 /24 not checked
193.143.66.0/24 IPv4 /24 not checked
193.143.67.0/24 IPv4 /24 not checked
212.233.84.0/24 IPv4 /24 not checked
212.233.85.0/24 IPv4 /24 not checked
212.233.86.0/24 IPv4 /24 not checked
212.233.87.0/24 IPv4 /24 not checked
45.137.112.0/24 IPv4 /24 not checked
45.137.113.0/24 IPv4 /24 not checked
45.137.115.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 AS205638
Address families
GNM-IX 200,000 Mbps IPv4
Global-IX 100,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 100,000 Mbps IPv4
MSK-IX Saint-Petersburg: MSK-IX Saint-Petersburg peering network 50,000 Mbps IPv4
MegaFon-IX: Main 180,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 100,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 100,000 Mbps IPv4
W-IX: vlan800 200,000 Mbps IPv4

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 AS205638 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

28 networks seen before AS205638 in AS paths

Observed upstreams
Families
AS29076 382 1,717
v4
AS12389 370 1,443
v4
AS31133 248 1,411
v4
AS31500 173 1,107
v4
AS20764 RASCOM-AS 131 720
v4
AS1299 TWELVE99 106 448
v4
AS8359 63 175
v4
AS3216 SOVAM-AS 66 161
v4
AS9049 21 121
v4
AS28917 Fiord-AS 23 100
v4
AS6939 HURRICANE 18 97
v4
AS50384 W-IX_LTD 21 95
v4
AS8218 NEO-ASN 3 64
v4
AS25091 IP-Max 7 62
v4
AS47692 NESSUS 2 32
v4
AS41327 FIBERTELECOM-AS 3 21
v4
AS25478 7 18
v4
AS50509 7 18
v4
AS49434 FBWNETWORKS 2 16
v4
AS6204 1 8
v4
AS6663 TTI-NET 1 8
v4
AS9198 KAZTELECOM-AS 1 8
v4
AS15958 1 8
v4
AS42295 TBISS-AS 1 8
v4
AS62000 1 8
v4
AS50673 Serverius-as 2 6
v4
AS56655 GIGAHOST 1 6
v4
AS60171 AFRIX-AS 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS205638 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.