Skip to main content

AS56522

ASNARISHKIN

3NET

Registry

Authoritative registration data

AS number
56522
Name
ASNARISHKIN
Organisation
3NET
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS56522
176.121.72.0/21 IPv4 /21 not checked
91.224.200.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 AS56522
Address families
DTEL-IX: PUBLIC 10,000 Mbps IPv4
Giganet IXN: Global exchange 10,000 Mbps IPv4
KM-IX 1,000 Mbps IPv4
UA-IX 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 AS56522 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS56522 in AS paths

Observed upstreams
Families
AS28773 AS-MASTER 148 398
v4
AS21497 100 252
v4
AS50263 26 62
v4
AS8218 NEO-ASN 5 24
v4
AS34840 2 4
v4
AS49434 2 4
v4
AS6204 1 2
v4
AS6663 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS56522 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 14
v4
AS49544 i3Dnet 1 4
v4
AS48919 1 2
v4
AS59514 1 2
v4
AS209823 1 2
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.