Skip to main content

AS49136

TELECOM-NETWORKS-AS

Peer MSK-IX

Registry

Authoritative registration data

AS number
49136
Name
TELECOM-NETWORKS-AS
Organisation
Peer MSK-IX
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS49136
109.229.96.0/19 IPv4 /19 not checked
81.162.32.0/20 IPv4 /20 not checked
94.231.128.0/20 IPv4 /20 not checked
94.231.133.0/24 IPv4 /24 not checked
94.231.135.0/24 IPv4 /24 not checked
94.231.136.0/24 IPv4 /24 not checked
94.231.139.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 AS49136
Address families
GNM-IX 10,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network IPv4
MSK-IX Samara 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 AS49136 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

16 networks seen before AS49136 in AS paths

No rows match “”.

Showing of

Observed downstreams

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

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.