Skip to main content

AS15969

Systemia-AS

Systemia.pl Sp. z o.o.

Registry

Authoritative registration data

AS number
15969
Name
Systemia-AS
Organisation
Systemia.pl Sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

2

Total announced

12

Announced prefixes

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

Prefixes announced by AS15969
194.187.72.0/22 IPv4 /22 not checked
45.86.212.0/22 IPv4 /22 RPKI valid
185.7.168.0/23 IPv4 /23 RPKI valid
185.7.170.0/23 IPv4 /23 RPKI valid
195.110.48.0/23 IPv4 /23 not checked
46.227.240.0/23 IPv4 /23 RPKI valid
46.227.242.0/23 IPv4 /23 RPKI valid
46.227.246.0/23 IPv4 /23 RPKI valid
46.227.244.0/24 IPv4 /24 RPKI valid
46.227.245.0/24 IPv4 /24 not checked
2a01:5e00::/29 IPv6 /29 RPKI valid
2a01:7600::/29 IPv6 /29 RPKI valid

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 AS15969
Address families
EPIX.Katowice 20,000 Mbps IPv4
EPIX.Poznan 80,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 AS15969 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS15969 in AS paths

Observed upstreams
Families
AS60695 NETRONIK-AS 490 3,914
v4 v6
AS212261 EPIX-POZ-GlobalMix 88 648
v4 v6
AS44033 Komster-AS 2 20
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS15969 in AS paths

Observed downstreams
Families
AS44033 Komster-AS 2 2
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

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