DNS response history for ns2.y32wr7.com

ns2.y32wr7.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 36 DNS check records, 36 successful responses, 0 failed responses, and 418 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.y32wr7.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

418 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.106.223.61

Most recently resolved hosting IP on selected date

Successful Responses

36

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.y32wr7.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
36 2026-08-25 12:40 639232576780683689
353 ms 59.106.223.61
35 2026-08-25 12:22 639232566381512620
17 ms 59.106.223.61
34 2026-08-25 12:05 639232556111768563
4 ms 59.106.223.61
33 2026-08-25 11:48 639232545839529039
420 ms 59.106.223.61
32 2026-08-25 11:31 639232535349285207
428 ms 59.106.223.61
31 2026-08-25 11:13 639232524938080723
440 ms 59.106.223.61
30 2026-08-25 10:20 639232492740373468
248 ms 59.106.223.61
29 2026-08-25 10:02 639232482235303141
257 ms 59.106.223.61
28 2026-08-25 09:45 639232471861770303
4 ms 59.106.223.61
27 2026-08-25 09:28 639232461630217327
4 ms 59.106.223.61
26 2026-08-25 09:11 639232451282965990
432 ms 59.106.223.61
25 2026-08-25 08:53 639232440814614938
441 ms 59.106.223.61
24 2026-08-25 08:36 639232430410720425
5 ms 59.106.223.61
23 2026-08-25 08:19 639232420003096185
439 ms 59.106.223.61
22 2026-08-25 08:01 639232409467287444
480 ms 59.106.223.61
21 2026-08-25 07:44 639232399077195997
430 ms 59.106.223.61
20 2026-08-25 07:26 639232388731528337
2339 ms 59.106.223.61
19 2026-08-25 07:09 639232378288598612
432 ms 59.106.223.61
18 2026-08-25 06:15 639232346196373643
375 ms 59.106.223.61
17 2026-08-25 05:58 639232336112370741
4 ms 59.106.223.61
16 2026-08-25 05:42 639232326146508970
524 ms 59.106.223.61
15 2026-08-25 05:25 639232316189381720
4 ms 59.106.223.61
14 2026-08-25 05:09 639232306217998913
2003 ms 59.106.223.61
13 2026-08-25 04:52 639232296255744174
436 ms 59.106.223.61
12 2026-08-25 04:35 639232286095760789
489 ms 59.106.223.61
11 2026-08-25 04:18 639232276086186273
437 ms 59.106.223.61
10 2026-08-25 04:02 639232265900986425
2 ms 59.106.223.61
9 2026-08-25 03:45 639232255723518075
444 ms 59.106.223.61
8 2026-08-25 03:28 639232245484452890
429 ms 59.106.223.61
7 2026-08-25 03:10 639232235157175331
521 ms 59.106.223.61
6 2026-08-25 02:17 639232203197189095
3 ms 59.106.223.61
5 2026-08-25 02:00 639232192844564298
491 ms 59.106.223.61
4 2026-08-25 01:43 639232182496008942
340 ms 59.106.223.61
3 2026-08-25 01:25 639232172197053132
518 ms 59.106.223.61
2 2026-08-25 00:32 639232140250307418
437 ms 59.106.223.61
1 2026-08-25 00:15 639232129927860324
436 ms 59.106.223.61