DNS response history for ns2.yenidostlar.com

ns2.yenidostlar.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 34 DNS check records, 31 successful responses, 3 failed responses, and 524 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.yenidostlar.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

524 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.162.124.118

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

3

Checks with no response or no returned latency

Failure Rate

9%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.yenidostlar.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
34 2026-08-25 12:07 639232556111768563
473 ms 69.162.124.118
33 2026-08-25 11:50 639232545839529039
2331 ms 69.162.124.118
32 2026-08-25 11:33 639232535349285207
317 ms 69.162.124.118
31 2026-08-25 11:15 639232524938080723
487 ms 69.162.124.118
30 2026-08-25 10:22 639232492740373468
-
29 2026-08-25 10:04 639232482235303141
-
28 2026-08-25 09:47 639232471861770303
-
27 2026-08-25 09:30 639232461630217327
1182 ms 69.162.124.118
26 2026-08-25 09:12 639232451282965990
474 ms 69.162.124.118
25 2026-08-25 08:55 639232440814614938
459 ms 69.162.124.118
24 2026-08-25 08:38 639232430410720425
301 ms 69.162.124.118
23 2026-08-25 08:20 639232420003096185
461 ms 69.162.124.118
22 2026-08-25 08:03 639232409467287444
308 ms 69.162.124.118
21 2026-08-25 07:45 639232399077195997
469 ms 69.162.124.118
20 2026-08-25 07:28 639232388731528337
313 ms 69.162.124.118
19 2026-08-25 07:11 639232378288598612
315 ms 69.162.124.118
18 2026-08-25 06:17 639232346196373643
464 ms 69.162.124.118
17 2026-08-25 06:00 639232336112370741
461 ms 69.162.124.118
16 2026-08-25 05:43 639232326146508970
341 ms 69.162.124.118
15 2026-08-25 05:27 639232316189381720
307 ms 69.162.124.118
14 2026-08-25 05:10 639232306217998913
472 ms 69.162.124.118
13 2026-08-25 04:54 639232296255744174
462 ms 69.162.124.118
12 2026-08-25 04:37 639232286095760789
2171 ms 69.162.124.118
11 2026-08-25 04:20 639232276086186273
479 ms 69.162.124.118
10 2026-08-25 04:03 639232265900986425
307 ms 69.162.124.118
9 2026-08-25 03:46 639232255723518075
396 ms 69.162.124.118
8 2026-08-25 03:29 639232245484452890
471 ms 69.162.124.118
7 2026-08-25 03:12 639232235157175331
311 ms 69.162.124.118
6 2026-08-25 02:19 639232203197189095
2 ms 69.162.124.118
5 2026-08-25 02:02 639232192844564298
475 ms 69.162.124.118
4 2026-08-25 01:44 639232182496008942
460 ms 69.162.124.118
3 2026-08-25 01:27 639232172197053132
472 ms 69.162.124.118
2 2026-08-25 00:34 639232140250307418
3 ms 69.162.124.118
1 2026-08-25 00:17 639232129927860324
313 ms 69.162.124.118