Skip to main content

AS36817

MCSNET

MCSNet

Registry

Authoritative registration data

AS number
36817
Name
MCSNET
Organisation
MCSNet
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

0

Total announced

11

Announced prefixes

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

Prefixes announced by AS36817
170.253.96.0/19 IPv4 /19 not checked
72.172.96.0/19 IPv4 /19 not checked
173.209.112.0/20 IPv4 /20 not checked
66.112.176.0/20 IPv4 /20 not checked
74.214.128.0/20 IPv4 /20 not checked
74.214.144.0/20 IPv4 /20 not checked
162.248.152.0/21 IPv4 /21 not checked
162.208.36.0/22 IPv4 /22 not checked
162.220.36.0/22 IPv4 /22 not checked
192.40.136.0/22 IPv4 /22 not checked
64.187.210.0/23 IPv4 /23 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 AS36817
Address families
SIX Seattle: MTU 1500 100,000 Mbps IPv4
YEGIX 10,000 Mbps IPv4
YYCIX 100,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 AS36817 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS36817 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 256 3,891
v4
AS577 BACOM 15 134
v4
AS852 ASN852 5 56
v4
AS394256 CLOUDSINGULARITY 1 11
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS36817 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 33
v4
AS49544 i3Dnet 1 22
v4
AS9002 RETN-AS 1 11
v4
AS35280 F5 1 11
v4
AS36236 NETACTUATE 1 11
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.