DNS response history for ns2.good4me.info

ns2.good4me.info 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 35 DNS check records, 35 successful responses, 0 failed responses, and 276 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.good4me.info.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

276 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

77.68.21.33

Most recently resolved hosting IP on selected date

Successful Responses

35

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.good4me.info

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
35 2026-08-25 12:16 639232566381512620
304 ms 77.68.21.33
34 2026-08-25 11:58 639232556111768563
85 ms 77.68.21.33
33 2026-08-25 11:41 639232545839529039
30 ms 77.68.21.33
32 2026-08-25 11:24 639232535349285207
82 ms 77.68.21.33
31 2026-08-25 11:06 639232524938080723
33 ms 77.68.21.33
30 2026-08-25 10:13 639232492740373468
83 ms 77.68.21.33
29 2026-08-25 09:55 639232482235303141
86 ms 77.68.21.33
28 2026-08-25 09:38 639232471861770303
30 ms 77.68.21.33
27 2026-08-25 09:21 639232461630217327
130 ms 77.68.21.33
26 2026-08-25 09:04 639232451282965990
86 ms 77.68.21.33
25 2026-08-25 08:46 639232440814614938
36 ms 77.68.21.33
24 2026-08-25 08:29 639232430410720425
2014 ms 77.68.21.33
23 2026-08-25 08:12 639232420003096185
285 ms 77.68.21.33
22 2026-08-25 07:54 639232409467287444
82 ms 77.68.21.33
21 2026-08-25 07:37 639232399077195997
178 ms 77.68.21.33
20 2026-08-25 07:19 639232388731528337
11 ms 77.68.21.33
19 2026-08-25 07:02 639232378288598612
11 ms 77.68.21.33
18 2026-08-25 06:09 639232346196373643
2030 ms 77.68.21.33
17 2026-08-25 05:52 639232336112370741
73 ms 77.68.21.33
16 2026-08-25 05:35 639232326146508970
118 ms 77.68.21.33
15 2026-08-25 05:19 639232316189381720
210 ms 77.68.21.33
14 2026-08-25 05:02 639232306217998913
2111 ms 77.68.21.33
13 2026-08-25 04:45 639232296255744174
129 ms 77.68.21.33
12 2026-08-25 04:28 639232286095760789
20 ms 77.68.21.33
11 2026-08-25 04:12 639232276086186273
79 ms 77.68.21.33
10 2026-08-25 03:55 639232265900986425
32 ms 77.68.21.33
9 2026-08-25 03:38 639232255723518075
33 ms 77.68.21.33
8 2026-08-25 03:21 639232245484452890
66 ms 77.68.21.33
7 2026-08-25 03:04 639232235157175331
78 ms 77.68.21.33
6 2026-08-25 02:10 639232203197189095
204 ms 77.68.21.33
5 2026-08-25 01:53 639232192844564298
398 ms 77.68.21.33
4 2026-08-25 01:36 639232182496008942
58 ms 77.68.21.33
3 2026-08-25 01:19 639232172197053132
433 ms 77.68.21.33
2 2026-08-25 00:25 639232140250307418
13 ms 77.68.21.33
1 2026-08-25 00:08 639232129927860324
9 ms 77.68.21.33