| Prefix | Company | Number of IPs |
|---|---|---|
| 62.221.32.0/23 | Farlep-Nikolaev ISP, | 512 |
| 62.221.35.0/24 | VEGA TG | 256 |
| 62.221.50.0/23 | Infra | 512 |
| 62.221.52.0/24 | Farlep-Lviv-Telecom, a subprovider | 256 |
| 62.221.53.0/24 | Farlep-Lviv-Telecom, a subprovider | 256 |
| 62.221.56.0/24 | Farlep Lviv branch Office | 256 |
| 62.221.58.0/24 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 256 |
| 62.221.60.0/24 | FLP PPPOE MK | 256 |
| 62.221.61.0/24 | VEGA in Nikolaev | 256 |
| 62.221.62.0/24 | DHCP for Lviv customers | 256 |
| 62.221.63.0/24 | DHCP for Lviv customers | 256 |
| 78.25.16.0/21 | Alkar Teleport | 2,048 |
| 78.25.24.0/22 | Alkar Teleport | 1,024 |
| 78.25.28.0/23 | Alkar Teleport | 512 |
| 78.25.30.0/24 | Alkar Teleport | 256 |
| 78.25.31.0/24 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 256 |
| 78.25.32.0/21 | Alkar Teleport | 2,048 |
| 78.25.43.0/24 | FLPI WIFI | 256 |
| 78.25.44.0/23 | Alkar Teleport | 512 |
| 78.25.46.0/23 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 512 |
| 78.25.48.0/23 | Alkar Teleport | 512 |
| 78.25.52.0/23 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 512 |
| 78.25.54.0/23 | Kyiv Public WI-Fi | 512 |
| 78.25.54.0/24 | Kyiv Public WI-Fi | 256 |
| 78.25.55.0/24 | Kyiv Public WI-Fi | 256 |
| 78.25.56.0/23 | Farmlogistic | 512 |
| 78.25.58.0/23 | Vega Telecom | 512 |
| 78.25.60.0/22 | VEGA TG | 1,024 |
| 78.111.16.0/21 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 2,048 |
| 78.111.24.0/24 | ISP "Vilcom" NET | 256 |
| 78.111.25.0/24 | ISP "Vilcom" NET | 256 |
| 78.111.26.0/23 | Kharkov | 512 |
| 78.111.28.0/22 | ISP "Vilcom" NET | 1,024 |
| 78.111.208.0/22 | VEGA PPPOE ZHYTOMYR | 1,024 |
| 78.111.212.0/23 | VEGA Zhytomyr | 512 |
| 78.111.218.0/23 | Farlep-Lviv-Telecom | 512 |
| 78.111.218.0/24 | Farlep-Lviv-Telecom | 256 |
| 78.111.219.0/24 | Farlep-Lviv-Telecom | 256 |
| 83.143.232.0/21 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 2,048 |
| 83.218.224.0/19 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 8,192 |
| 83.218.224.0/24 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 256 |
| 83.218.225.0/24 | Kiev | 256 |
| 83.218.230.0/23 | Dhcp Chernigov | 512 |
| 83.218.232.0/23 | CS Kiev | 512 |
| 83.218.245.0/24 | DHCP for Borispol | 256 |
| 83.218.246.0/23 | Kiev | 512 |
| 83.218.254.0/23 | VEGA FTTx DESNA | 512 |
| 93.127.4.0/22 | CS Vega Odessa | 1,024 |
| 93.127.8.0/22 | CS Vega Odessa | 1,024 |
| 93.127.12.0/22 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 1,024 |
| 93.127.16.0/20 | VEGA GPON DNIPRO | 4,096 |
| 93.127.32.0/21 | Vega Telecom | 2,048 |
| 93.127.40.0/22 | Vega Telecom | 1,024 |
| 93.127.44.0/23 | Vega Telecom | 512 |
| 93.127.46.0/23 | Vega Telecom | 512 |
| 93.127.48.0/21 | VEGA GPON DNIPRO | 2,048 |
| 93.127.60.0/23 | Vega Telecom | 512 |
| 93.127.62.0/23 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 512 |
| 93.178.200.0/23 | FLP CORE | 512 |
| 93.178.200.0/24 | FLP CORE | 256 |
| 93.178.244.0/24 | VEGA LVIV | 256 |
| 93.178.245.0/24 | VEGA LVIV | 256 |
| 93.178.246.0/24 | VEGA LVIV | 256 |
| 93.178.247.0/24 | VEGA LVIV | 256 |
| 93.178.252.0/22 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 1,024 |
| 178.136.0.0/24 | Vega Telecom | 256 |
| 178.136.2.0/24 | Kiev | 256 |
| 178.136.4.0/22 | Kiev | 1,024 |
| 178.136.4.0/23 | Kiev | 512 |
| 178.136.4.0/24 | Kiev | 256 |
| 178.136.6.0/24 | ML Zhitomir | 256 |
| 178.136.8.0/21 | CS Kiev PPPoE | 2,048 |
| 178.136.8.0/22 | CS Kiev PPPoE | 1,024 |
| 178.136.48.0/21 | Odessa | 2,048 |
| 178.136.56.0/21 | CS Vega Odessa | 2,048 |
| 178.136.76.0/22 | CS Odessa | 1,024 |
| 178.136.80.0/21 | VEGA GPON ODESSA | 2,048 |
| 178.136.116.0/22 | CS Odessa | 1,024 |
| 178.136.120.0/24 | For Lviv' DHCP | 256 |
| 178.136.121.0/24 | For Lviv' DHCP | 256 |
| 178.136.122.0/24 | For Lviv' DHCP | 256 |
| 178.136.123.0/24 | For Lviv' DHCP | 256 |
| 178.136.124.0/24 | Vega Lviv | 256 |
| 178.136.125.0/24 | DHCP for Lviv | 256 |
| 178.136.126.0/24 | DHCP for Lviv | 256 |
| 178.136.127.0/24 | DHCP pool for Lviv customers | 256 |
| 178.136.128.0/23 | VEGA TG | 512 |
| 178.136.144.0/20 | PRIVATE JOINT-STOCK COMPANY FARLEP-INVEST | 4,096 |
| 178.136.160.0/20 | VEGA GPON DNIPRO | 4,096 |
| 178.136.176.0/22 | VEGA GPON DNIPRO | 1,024 |
| 178.136.180.0/23 | FLP DHCP ZP | 512 |
| 178.136.182.0/24 | FLP DHCP ZP | 256 |
| 178.136.184.0/22 | VEGA TG | 1,024 |
| 178.136.188.0/22 | VEGA TG | 1,024 |
| 178.136.192.0/19 | Vega Telecom | 8,192 |
| 178.136.224.0/23 | Kharkov | 512 |
| 178.136.226.0/23 | for VEGA customers in Kharkov | 512 |
| 178.136.230.0/24 | PPPoE for Lviv customers | 256 |
| 178.136.231.0/24 | DHCP Lviv | 256 |
| 178.136.232.0/24 | Vega Telecom | 256 |
This table only shows the first 100 of the set of IPv4 and IPv6 prefixes. All data is available via our IP data API.
IP ranges are the different blocks of IP addresses advertised by an Autonomous System (AS). These ranges can be used by the same organization operating the AS, or by different organizations.
AS6703 has no peers recorded.
Peering is a direct, often free, traffic exchange between Autonomous Systems (ASNs). They share routes only to their own networks and customers, making connections faster and cheaper for that specific traffic, without providing full internet access to each other.
AS6703 provides internet connectivity to these downstream Autonomous Systems.
A downstream is a customer Autonomous System that pays another AS (its provider) for internet access. The provider AS carries the downstream's traffic and makes its network reachable.
Discover your public IP address and detailed information about your connection.
Convert CIDR notation to IP address ranges and vice versa. Useful for network configuration and security.
Perform a reverse DNS (rDNS) lookup to get the hostname for an IP address.
Expand or collapse IPv6 addresses to their full or shortened forms for better readability and usage.
We think you’re in ...
Did we get it right?
Waiting for location...
Our policy for safe geolocation means we don’t identify specific individuals or households. When you submit your location here, we only keep a lower-accuracy version for a limited amount of time, without any other identifying data.
Read how this works in our privacy policy