Skip to main content

AS25532

MASTERHOST-AS

Moscow, Russia

Registry

Authoritative registration data

AS number
25532
Name
MASTERHOST-AS
Organisation
Moscow, Russia
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

34

IPv6 prefixes

6

Total announced

40

Announced prefixes

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

Prefixes announced by AS25532
90.156.128.0/20 IPv4 /20 not checked
90.156.200.0/21 IPv4 /21 not checked
83.222.12.0/22 IPv4 /22 not checked
87.242.68.0/22 IPv4 /22 not checked
87.242.72.0/22 IPv4 /22 not checked
87.242.80.0/22 IPv4 /22 not checked
90.156.204.0/22 IPv4 /22 not checked
90.156.240.0/22 IPv4 /22 not checked
83.222.4.0/23 IPv4 /23 not checked
87.242.64.0/23 IPv4 /23 not checked
83.222.12.0/24 IPv4 /24 not checked
83.222.13.0/24 IPv4 /24 not checked
83.222.14.0/24 IPv4 /24 not checked
83.222.15.0/24 IPv4 /24 not checked
83.222.4.0/24 IPv4 /24 not checked
83.222.5.0/24 IPv4 /24 not checked
87.242.65.0/24 IPv4 /24 not checked
87.242.67.0/24 IPv4 /24 not checked
87.242.72.0/24 IPv4 /24 not checked
87.242.73.0/24 IPv4 /24 not checked
87.242.74.0/24 IPv4 /24 not checked
87.242.75.0/24 IPv4 /24 not checked
87.242.80.0/24 IPv4 /24 not checked
87.242.81.0/24 IPv4 /24 not checked
87.242.82.0/24 IPv4 /24 not checked
87.242.83.0/24 IPv4 /24 not checked
90.156.128.0/24 IPv4 /24 not checked
90.156.129.0/24 IPv4 /24 not checked
90.156.132.0/24 IPv4 /24 not checked
90.156.139.0/24 IPv4 /24 not checked
90.156.140.0/24 IPv4 /24 not checked
90.156.141.0/24 IPv4 /24 not checked
90.156.200.0/24 IPv4 /24 not checked
90.156.201.0/24 IPv4 /24 not checked
2a00:15f8::/32 IPv6 /32 not checked
2a00:15f8:a000::/48 IPv6 /48 not checked
2a00:15f8:a002::/48 IPv6 /48 not checked
2a00:15f8:a003::/48 IPv6 /48 not checked
2a00:15f8:c::/48 IPv6 /48 not checked
2a00:15f8:d::/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 AS25532
Address families
CLOUD-IX MSK 10,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4 · IPv6
PITER-IX Riga: RIX_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Rostov 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4 · IPv6
PITER-IX Tallinn: TLL_PEERING VLAN 10,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 AS25532 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS25532 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 355 7,048
v4 v6
AS50509 368 2,653
v4 v6
AS57304 45 691
v4 v6
AS6939 HURRICANE 70 652
v4 v6
AS59692 313 626
v4
AS25091 IP-Max 9 328
v4 v6
AS24482 SGGS-AS-AP 2 297
v4 v6
AS14840 ASN14840 2 110
v4
AS34927 iFog-GmbH 2 66
v4
AS49434 2 60
v4
AS41327 FIBERTELECOM-AS 2 53
v4 v6
AS57724 DDOS-GUARD 25 49
v4
AS61049 2 44
v4
AS137409 GSLNETWORKS-AS-AP 3 36
v4
AS9198 1 36
v4 v6
AS50629 LWLCOM 3 31
v4
AS13194 1 22
v4
AS263444 1 22
v4
AS22356 4 9
v4
AS39120 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS25532 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

15 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS212483 level86 1 44
v4
AS28910 1 36
v4 v6
AS41722 1 36
v4 v6
AS28917 1 32
v4 v6
AS36236 NETACTUATE 1 31
v4 v6
AS29049 1 30
v4
AS35598 1 30
v4
AS37721 ORG-VTS1-AFRINIC 1 30
v4
AS44901 1 30
v4
AS49673 TRUENETWORK 1 30
v4
AS205112 PHILUNET 1 30
v4
AS209823 1 30
v4
AS20764 RASCOM-AS 1 22
v4
AS198150 SIACOM-AS 1 22
v4
AS199524 GCORE 1 22
v4

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.