Skip to main content

AS206589

NSIX-Data-Center

NSIX Data Center sp. z o.o.

Registry

Authoritative registration data

AS number
206589
Name
NSIX-Data-Center
Organisation
NSIX Data Center sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS206589
185.182.96.0/22 IPv4 /22 not checked
2a0a:ea80::/29 IPv6 /29 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 AS206589
Address families
EPIX.Katowice 10,000 Mbps IPv4 · IPv6
TPIX PL 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 AS206589 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS206589 in AS paths

Observed upstreams
Families
AS20804 ASN-TELENERGO 275 440
v4 v6
AS29535 MIX2_OpenPeering 139 184
v4
AS12741 AS-NETIA 95 117
v4
AS6204 ZET-NET 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS206589 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 2
v4
AS24482 SGGS-AS-AP 1 1
v4
AS28917 Fiord-AS 1 1
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.