AS43939
Netia SA — inetia.pl
Summary
Country |
![]() |
Organization | Netia SA |
Domain | inetia.pl |
Number of IPv4 | 266,240 |
Number of IPv6 | 2.5254× 1029 |
AS Type | ISP |
Registry | RIPE NCC |
Allocated | October 23, 2007 (about 17 years ago) |
Updated | May 25, 2021 (about 3 years ago) |
IP Ranges
AS43939 announces 52 IPv4 ranges and 6 IPv6 ranges.
That's a total of 266,240 IPv4 addresses and 2.5254× 1029 IPv6 addresses.
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
5.57.128.0/18 |
![]() |
16,384 | RIPE NCC | ALLOCATED PA |
62.69.192.0/18 |
![]() |
16,384 | RIPE NCC | ASSIGNED PA |
77.87.136.0/21 |
![]() |
2,048 | RIPE NCC | ASSIGNED PA |
77.88.128.0/18 |
![]() |
16,384 | RIPE NCC | ASSIGNED PA |
78.31.166.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PI |
80.238.64.0/19 |
![]() |
8,192 | RIPE NCC | ASSIGNED PA |
83.142.56.0/21 |
![]() |
2,048 | RIPE NCC | ASSIGNED PA |
83.143.96.0/21 |
![]() |
2,048 | RIPE NCC | ASSIGNED PI |
84.38.96.0/20 |
![]() |
4,096 | RIPE NCC | ASSIGNED PA |
84.234.0.0/20 |
![]() |
4,096 | RIPE NCC | ASSIGNED PA |
84.234.32.0/20 |
![]() |
4,096 | RIPE NCC | ASSIGNED PA |
85.202.208.0/20 |
![]() |
4,096 | RIPE NCC | ASSIGNED PA |
87.99.0.0/18 |
![]() |
16,384 | RIPE NCC | ASSIGNED PA |
87.239.72.0/21 |
![]() |
2,048 | RIPE NCC | ASSIGNED PA |
89.187.224.0/19 |
![]() |
8,192 | RIPE NCC | ASSIGNED PA |
89.200.152.0/21 |
![]() |
2,048 | RIPE NCC | ASSIGNED PA |
90.156.0.0/17 |
![]() |
32,768 | RIPE NCC | ASSIGNED PA |
91.142.192.0/20 |
![]() |
4,096 | RIPE NCC | ASSIGNED PA |
91.145.128.0/18 |
![]() |
16,384 | RIPE NCC | ASSIGNED PA |
91.146.192.0/18 |
![]() |
16,384 | RIPE NCC | ASSIGNED PA |
91.150.128.0/19 |
![]() |
8,192 | RIPE NCC | ASSIGNED PA |
91.195.232.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PI |
91.202.172.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
91.215.228.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PI |
91.220.225.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
93.181.128.0/18 |
![]() |
16,384 | RIPE NCC | ASSIGNED PA |
95.155.64.0/18 |
![]() |
16,384 | RIPE NCC | ASSIGNED PA |
178.214.128.0/19 |
![]() |
8,192 | RIPE NCC | ALLOCATED PA |
178.252.0.0/18 |
![]() |
16,384 | RIPE NCC | ASSIGNED PA |
185.2.36.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
188.114.95.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
193.19.122.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PI |
193.58.232.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
193.105.180.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
193.107.196.0/22 |
![]() |
1,024 | RIPE NCC | ALLOCATED PA |
193.138.140.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PI |
193.151.64.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
193.151.64.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PA |
193.227.100.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
193.238.40.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
193.239.224.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PI |
194.6.204.0/22 |
![]() |
1,024 | RIPE NCC | ALLOCATED PA |
194.33.185.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
194.146.128.0/22 |
![]() |
1,024 | RIPE NCC | ALLOCATED PA |
194.150.238.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PI |
194.187.180.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
194.242.0.0/23 |
![]() |
512 | RIPE NCC | ASSIGNED PI |
195.74.56.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
195.222.100.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PI |
195.225.248.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
217.197.64.0/21 |
![]() |
2,048 | RIPE NCC | ASSIGNED PA |
217.197.72.0/21 |
![]() |
2,048 | RIPE NCC | ASSIGNED PA |
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
2a00:1d18::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-RIR |
2a00:7340::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-RIR |
2a02:2270::/32 |
![]() |
7.9228× 1028 | RIPE NCC | ALLOCATED-BY-RIR |
2a02:2270:2000::/36 |
![]() |
4.9518× 1027 | RIPE NCC | ALLOCATED-BY-RIR |
2a02:2270:4000::/36 |
![]() |
4.9518× 1027 | RIPE NCC | ALLOCATED-BY-RIR |
2a02:2270:5000::/36 |
![]() |
4.9518× 1027 | RIPE NCC | ALLOCATED-BY-RIR |
Peers
AS43939 does not have any direct peering agreements. Instead, its global connectivity is achieved through transit providers. While this setup ensures comprehensive reach, future peering could reduce latency and optimize route efficiency.
Upstreams
AS43939 connects to the global Internet via at least 1 upstream provider. In this setup, AS43939 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS43939 currently has no downstream networks, meaning it does not serve as a transit provider to customer networks.