Skip to main content

AS49120

GORSET-AS

Gorset Ltd.

Registry

Authoritative registration data

AS number
49120
Name
GORSET-AS
Organisation
Gorset Ltd.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS49120
46.173.32.0/19 IPv4 /19 not checked
109.197.136.0/21 IPv4 /21 not checked
109.95.96.0/21 IPv4 /21 not checked
62.122.176.0/21 IPv4 /21 not checked
192.162.124.0/22 IPv4 /22 not checked
193.107.148.0/22 IPv4 /22 not checked
2001:67c:215c::/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 AS49120
Address families
MSK-IX Moscow: MSK-IX peering network 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 AS49120 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS49120 in AS paths

Observed upstreams
Families
AS35598 378 3,140
v4
AS31133 129 1,021
v4
AS62255 BEMYLINK 73 636
v4
AS6939 HURRICANE 118 157
v6
AS25091 IP-Max 11 77
v4 v6
AS9198 1 1
v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS49120 in AS paths

Observed downstreams
Families
AS51070 302 2,702
v4

No rows match “”.

Showing of

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 42
v4 v6
AS49544 i3Dnet 2 26
v4
AS28917 2 15
v4 v6
AS36236 NETACTUATE 2 14
v4 v6
AS41327 FIBERTELECOM-AS 2 14
v4 v6
AS41722 2 14
v4 v6
AS29049 2 13
v4
AS49673 TRUENETWORK 2 13
v4
AS199524 GCORE 2 13
v4
AS20764 RASCOM-AS 1 1
v6
AS28910 1 1
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.