DNS response history for ns2.yazilimer.com

ns2.yazilimer.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-25. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 218 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.yazilimer.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

218 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

193.111.73.167

Most recently resolved hosting IP on selected date

Successful Responses

32

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.yazilimer.com

Showing DNS history for 2026-08-25 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
32 2026-08-25 11:23 639232535349285207
148 ms 193.111.73.167
31 2026-08-25 11:05 639232524938080723
69 ms 193.111.73.167
30 2026-08-25 10:12 639232492740373468
2058 ms 193.111.73.167
29 2026-08-25 09:54 639232482235303141
133 ms 193.111.73.167
28 2026-08-25 09:37 639232471861770303
16 ms 193.111.73.167
27 2026-08-25 09:20 639232461630217327
115 ms 193.111.73.167
26 2026-08-25 09:03 639232451282965990
123 ms 193.111.73.167
25 2026-08-25 08:45 639232440814614938
131 ms 193.111.73.167
24 2026-08-25 08:28 639232430410720425
136 ms 193.111.73.167
23 2026-08-25 08:11 639232420003096185
125 ms 193.111.73.167
22 2026-08-25 07:53 639232409467287444
151 ms 193.111.73.167
21 2026-08-25 07:36 639232399077195997
17 ms 193.111.73.167
20 2026-08-25 07:18 639232388731528337
126 ms 193.111.73.167
19 2026-08-25 07:01 639232378288598612
123 ms 193.111.73.167
18 2026-08-25 06:07 639232346196373643
140 ms 193.111.73.167
17 2026-08-25 05:51 639232336112370741
3 ms 193.111.73.167
16 2026-08-25 05:34 639232326146508970
2047 ms 193.111.73.167
15 2026-08-25 05:17 639232316189381720
24 ms 193.111.73.167
14 2026-08-25 05:01 639232306217998913
34 ms 193.111.73.167
13 2026-08-25 04:44 639232296255744174
136 ms 193.111.73.167
12 2026-08-25 04:27 639232286095760789
21 ms 193.111.73.167
11 2026-08-25 04:11 639232276086186273
142 ms 193.111.73.167
10 2026-08-25 03:54 639232265900986425
132 ms 193.111.73.167
9 2026-08-25 03:37 639232255723518075
127 ms 193.111.73.167
8 2026-08-25 03:20 639232245484452890
106 ms 193.111.73.167
7 2026-08-25 03:02 639232235157175331
8 ms 193.111.73.167
6 2026-08-25 02:09 639232203197189095
126 ms 193.111.73.167
5 2026-08-25 01:52 639232192844564298
124 ms 193.111.73.167
4 2026-08-25 01:35 639232182496008942
15 ms 193.111.73.167
3 2026-08-25 01:17 639232172197053132
122 ms 193.111.73.167
2 2026-08-25 00:24 639232140250307418
76 ms 193.111.73.167
1 2026-08-25 00:07 639232129927860324
134 ms 193.111.73.167