Skip to main content

AS47321

IIF-AS

Last update: 12.04.2018

Registry

Authoritative registration data

AS number
47321
Name
IIF-AS
Organisation
Last update: 12.04.2018
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

0

Total announced

14

Announced prefixes

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

Prefixes announced by AS47321
185.6.124.0/22 IPv4 /22 not checked
185.9.72.0/22 IPv4 /22 not checked
185.6.124.0/23 IPv4 /23 not checked
185.6.126.0/23 IPv4 /23 not checked
185.9.72.0/23 IPv4 /23 not checked
185.9.74.0/23 IPv4 /23 not checked
185.6.124.0/24 IPv4 /24 not checked
185.6.125.0/24 IPv4 /24 not checked
185.6.126.0/24 IPv4 /24 not checked
185.6.127.0/24 IPv4 /24 not checked
185.9.72.0/24 IPv4 /24 not checked
185.9.73.0/24 IPv4 /24 not checked
185.9.74.0/24 IPv4 /24 not checked
185.9.75.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 AS47321
Address families
GNM-IX 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_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 AS47321 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS47321 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS47321 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

17 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.