DNS response history for ns2.good-day4play.com

ns2.good-day4play.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 33 DNS check records, 33 successful responses, 0 failed responses, and 401 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.good-day4play.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

401 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.180.157.160

Most recently resolved hosting IP on selected date

Successful Responses

33

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.good-day4play.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
33 2026-08-25 11:38 639232545839529039
33 ms 38.180.157.160
32 2026-08-25 11:20 639232535349285207
113 ms 38.180.157.160
31 2026-08-25 11:03 639232524938080723
2037 ms 38.180.157.160
30 2026-08-25 10:09 639232492740373468
1556 ms 38.180.157.160
29 2026-08-25 09:52 639232482235303141
53 ms 38.180.157.160
28 2026-08-25 09:34 639232471861770303
48 ms 38.180.157.160
27 2026-08-25 09:17 639232461630217327
40 ms 38.180.157.160
26 2026-08-25 09:00 639232451282965990
36 ms 38.180.157.160
25 2026-08-25 08:43 639232440814614938
36 ms 38.180.157.160
24 2026-08-25 08:25 639232430410720425
92 ms 38.180.157.160
23 2026-08-25 08:08 639232420003096185
50 ms 38.180.157.160
22 2026-08-25 07:51 639232409467287444
4027 ms 38.180.157.160
21 2026-08-25 07:33 639232399077195997
88 ms 38.180.157.160
20 2026-08-25 07:16 639232388731528337
47 ms 38.180.157.160
19 2026-08-25 06:59 639232378288598612
67 ms 38.180.157.160
18 2026-08-25 06:05 639232346196373643
47 ms 38.180.157.160
17 2026-08-25 05:48 639232336112370741
78 ms 38.180.157.160
16 2026-08-25 05:32 639232326146508970
2049 ms 38.180.157.160
15 2026-08-25 05:15 639232316189381720
2086 ms 38.180.157.160
14 2026-08-25 04:58 639232306217998913
41 ms 38.180.157.160
13 2026-08-25 04:42 639232296255744174
50 ms 38.180.157.160
12 2026-08-25 04:25 639232286095760789
22 ms 38.180.157.160
11 2026-08-25 04:08 639232276086186273
48 ms 38.180.157.160
10 2026-08-25 03:51 639232265900986425
52 ms 38.180.157.160
9 2026-08-25 03:34 639232255723518075
49 ms 38.180.157.160
8 2026-08-25 03:17 639232245484452890
23 ms 38.180.157.160
7 2026-08-25 03:00 639232235157175331
41 ms 38.180.157.160
6 2026-08-25 02:07 639232203197189095
58 ms 38.180.157.160
5 2026-08-25 01:49 639232192844564298
44 ms 38.180.157.160
4 2026-08-25 01:32 639232182496008942
58 ms 38.180.157.160
3 2026-08-25 01:15 639232172197053132
48 ms 38.180.157.160
2 2026-08-25 00:22 639232140250307418
41 ms 38.180.157.160
1 2026-08-25 00:05 639232129927860324
73 ms 38.180.157.160