DNS response history for ns2.aliyilmaz.com

ns2.aliyilmaz.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 402 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.aliyilmaz.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

402 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.173.177.167

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.aliyilmaz.com

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
29 2026-08-26 09:26 639233329214918079
43 ms 95.173.177.167
28 2026-08-26 09:08 639233318749762337
23 ms 95.173.177.167
27 2026-08-26 08:51 639233308387917838
44 ms 95.173.177.167
26 2026-08-26 08:34 639233297961740122
58 ms 95.173.177.167
25 2026-08-26 08:16 639233287487159094
130 ms 95.173.177.167
24 2026-08-26 07:59 639233276995531707
38 ms 95.173.177.167
23 2026-08-26 07:41 639233266521568229
49 ms 95.173.177.167
22 2026-08-26 07:24 639233256081047431
2032 ms 95.173.177.167
21 2026-08-26 06:30 639233223620132921
51 ms 95.173.177.167
20 2026-08-26 06:13 639233213287814244
134 ms 95.173.177.167
19 2026-08-26 05:55 639233202925983161
2041 ms 95.173.177.167
18 2026-08-26 05:38 639233192644780696
45 ms 95.173.177.167
17 2026-08-26 05:21 639233182401183833
69 ms 95.173.177.167
16 2026-08-26 05:04 639233172074181051
37 ms 95.173.177.167
15 2026-08-26 04:47 639233161808421455
21 ms 95.173.177.167
14 2026-08-26 04:29 639233151357344052
21 ms 95.173.177.167
13 2026-08-26 04:12 639233141034116946
43 ms 95.173.177.167
12 2026-08-26 03:55 639233130828334142
42 ms 95.173.177.167
11 2026-08-26 03:38 639233120373450007
103 ms 95.173.177.167
10 2026-08-26 03:20 639233110066216193
73 ms 95.173.177.167
9 2026-08-26 02:27 639233078065410564
73 ms 95.173.177.167
8 2026-08-26 02:10 639233067787457832
2011 ms 95.173.177.167
7 2026-08-26 01:53 639233057501801162
83 ms 95.173.177.167
6 2026-08-26 01:36 639233047089431703
2059 ms 95.173.177.167
5 2026-08-26 01:18 639233036754790688
88 ms 95.173.177.167
4 2026-08-26 01:01 639233026412602472
24 ms 95.173.177.167
3 2026-08-26 00:44 639233016064066127
49 ms 95.173.177.167
2 2026-08-26 00:27 639233005922655772
2152 ms 94.140.14.33
1 2026-08-26 00:10 639232995672256907
35 ms 95.173.177.167