95.58.128.0/19
AS9198 · JSC Kazakhtelecom
Need more data or want to access it via API or data downloads? Sign up to get free access
Sign up for free ›Summary
| Country |
Kazakhstan
|
| Domain | telecom.kz |
| ASN | AS9198 |
| Parent Range | 95.56.0.0/14 |
| Registry | RIPE |
| ID | PVLMETRO |
WHOIS Details
inetnum: 95.58.132.0 - 95.58.135.255 netname: PVLMETRO descr: JSC Kazakhtelecom, Pavlodar Affiliate descr: Metro Ethernet Network country: KZ remarks: INFRA-AW admin-c: KNIC1-RIPE tech-c: KNIC1-RIPE status: ASSIGNED PA mnt-by: KNIC-MNT created: 2008-11-24T16:15:04Z last-modified: 2015-02-06T05:31:40Z source: RIPE abuse-email: abuse@telecom.kz abuse-c: KNIC1-RIPE abuse-org: ORG-KDNA1-RIPE role: Kazakhtelecom Network Information Center address: Kazakhtelecom Corporate sales administration address: 129 Panfilov address: Almaty 050000 address: Kazakhstan mnt-by: KNIC-MNT phone: +7 727 2588254 phone: +7 727 2587977 fax-no: +7 727 2585855 e-mail: nic@telecom.kz abuse-mailbox: abuse@telecom.kz remarks: trouble:Questions and bug reports ... mailto: nic@online.kz tech-c: DZ810-RIPE nic-hdl: KNIC1-RIPE remarks: Please call us 09:00 - 12:00 UTC only created: 1970-01-01T00:00:00Z last-modified: 2024-02-28T11:18:08Z source: RIPE route: 95.58.128.0/19 descr: Kazakhtelecom Data Network Administration origin: AS9198 mnt-by: KNIC-MNT created: 2009-04-02T11:07:12Z last-modified: 2009-04-02T11:07:12Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 95.58.128.0/19
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 95.56.0.0/14 | AS9198 | JSC Kazakhtelecom | 262,144 |
BGP prefixes that are contained by 95.58.128.0/19
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 95.58.148.0/22 | AS9198 | JSC Kazakhtelecom | 1,024 |
| 95.58.152.0/22 | AS9198 | JSC Kazakhtelecom | 1,024 |
Hosted domains
There is 1 domain name hosted across 1 IP address on this ASN. Checkout our API to access full domain hosting information.
| IP Address | Domain | Domains on this IP |
|---|
Hosted domains API
Pingable IPs
5,972 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 95.58.152.151 |
28.91ms from Karagandy,
KZ
|
|
| 95.58.151.110 |
1.09ms from Pavlodar,
KZ
|
|
| 95.58.137.239 |
1.22ms from Pavlodar,
KZ
|
|
| 95.58.155.0 |
29.17ms from Karagandy,
KZ
|
|
| 95.58.141.226 |
1.19ms from Pavlodar,
KZ
|
|
| 95.58.133.107 |
1.10ms from Pavlodar,
KZ
|
|
| 95.58.129.239 |
1.05ms from Pavlodar,
KZ
|
|
| 95.58.146.1 |
0.70ms from Pavlodar,
KZ
|
|
| 95.58.134.2 |
1.09ms from Pavlodar,
KZ
|
|
| 95.58.132.28 |
0.98ms from Pavlodar,
KZ
|
|
| 95.58.147.1 |
17.88ms from Astana,
KZ
|
|
| 95.58.128.1 |
0.78ms from Pavlodar,
KZ
|
|
| 95.58.135.155 |
1.18ms from Pavlodar,
KZ
|
|
| 95.58.131.187 |
0.98ms from Pavlodar,
KZ
|
|
| 95.58.158.1 |
0.46ms from Pavlodar,
KZ
|
|
| 95.58.138.114 |
1.13ms from Pavlodar,
KZ
|
|
| 95.58.136.5 |
1.31ms from Pavlodar,
KZ
|
|
| 95.58.148.1 |
0.55ms from Pavlodar,
KZ
|
|
| 95.58.154.55 |
29.01ms from Karagandy,
KZ
|
|
| 95.58.139.102 |
0.97ms from Pavlodar,
KZ
|
|
| 95.58.153.44 |
29.20ms from Karagandy,
KZ
|
|
| 95.58.159.44 |
0.17ms from Pavlodar,
KZ
|
|
| 95.58.140.229 |
0.90ms from Pavlodar,
KZ
|
|
| 95.58.145.105 |
6.67ms from Astana,
KZ
|
|
| 95.58.149.44 |
0.90ms from Pavlodar,
KZ
|
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
| IP Address | ASN | Details |
|---|---|---|
| 174.75.228.243 |
13.63ms from Dallas,
US
|
|
| 98.20.84.3 |
2.58ms from Dallas,
US
|
|
| 141.88.213.243 |
1.63ms from Duesseldorf,
DE
|
|
| 83.192.107.163 |
7.42ms from Frankfurt am Main,
DE
|
|
| 187.246.149.3 |
0.74ms from Guadalajara,
MX
|
|
| 8.215.5.147 |
0.70ms from Jakarta,
ID
|
|
| 195.123.122.115 |
0.33ms from Kyiv,
UA
|
|
| 86.165.177.67 |
3.07ms from London,
GB
|
|
| 195.99.211.195 |
3.08ms from London,
GB
|
|
| 81.158.235.51 |
7.77ms from London,
GB
|
|
| 149.154.6.131 |
6.02ms from Minneapolis,
US
|
|
| 47.18.119.131 |
9.29ms from New York City,
US
|
|
| 124.103.17.51 |
6.56ms from Osaka,
JP
|
|
| 72.81.239.243 |
4.52ms from Philadelphia,
US
|
|
| 20.98.88.19 |
0.31ms from Quincy,
US
|
|
| 129.211.157.243 |
1.09ms from Shanghai,
CN
|
|
| 40.121.3.131 |
0.46ms from Ashburn,
US
|
|
| 24.63.29.19 |
5.80ms from Boston,
US
|
|
| 14.233.33.35 |
7.04ms from Da Nang,
VN
|
|
| 20.46.157.227 |
1.30ms from Dubai,
AE
|
|
| 5.138.75.147 |
6.25ms from Krasnodar,
RU
|
|
| 122.52.199.227 |
1.58ms from Manila,
PH
|
|
| 68.196.53.83 |
6.08ms from New York City,
US
|
|
| 103.112.180.35 |
1.48ms from Osaka,
JP
|
|
| 58.183.69.115 |
6.76ms from Osaka,
JP
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Pavlodar, KZ
What are IP address ranges?
IP address ranges, or netblocks, are groups of related IP addresses. They are usually represented as a base IP address, followed by a slash, and then a netmask which represents how many IP addresses are contained within the netblock. This format is known as CIDR. You'll also sometimes see netblocks given as a start ip address, and an end ip address, or an ip address range.
Traffic works its way around the internet based on the routing table, which contains a list of networks and their associated netblocks.
An API built with users in mind: reliable, accurate, and easy-to-use
Discover why industry-leading companies around the globe love our data. IPinfo's accurate insights fuel use cases from cybersecurity, data enrichment, web personalization, and much more.
Our IP tools
Explore all tools
Summarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs