DNS response history for ns2.gohearst.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

317 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.220.199.6

Most recently resolved hosting IP on selected date

Successful Responses

29

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.gohearst.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
29 2026-08-25 09:59 639232482235303141
269 ms 74.220.199.6
28 2026-08-25 09:41 639232471861770303
2167 ms 74.220.199.6
27 2026-08-25 09:24 639232461630217327
2131 ms 74.220.199.6
26 2026-08-25 09:07 639232451282965990
125 ms 74.220.199.6
25 2026-08-25 08:50 639232440814614938
263 ms 74.220.199.6
24 2026-08-25 08:32 639232430410720425
152 ms 74.220.199.6
23 2026-08-25 08:15 639232420003096185
235 ms 74.220.199.6
22 2026-08-25 07:58 639232409467287444
275 ms 74.220.199.6
21 2026-08-25 07:40 639232399077195997
133 ms 74.220.199.6
20 2026-08-25 07:23 639232388731528337
130 ms 74.220.199.6
19 2026-08-25 07:05 639232378288598612
242 ms 74.220.199.6
18 2026-08-25 06:12 639232346196373643
154 ms 74.220.199.6
17 2026-08-25 05:55 639232336112370741
170 ms 74.220.199.6
16 2026-08-25 05:38 639232326146508970
130 ms 74.220.199.6
15 2026-08-25 05:22 639232316189381720
128 ms 74.220.199.6
14 2026-08-25 05:05 639232306217998913
131 ms 74.220.199.6
13 2026-08-25 04:49 639232296255744174
254 ms 74.220.199.6
12 2026-08-25 04:32 639232286095760789
135 ms 74.220.199.6
11 2026-08-25 04:15 639232276086186273
132 ms 74.220.199.6
10 2026-08-25 03:58 639232265900986425
239 ms 74.220.199.6
9 2026-08-25 03:41 639232255723518075
126 ms 74.220.199.6
8 2026-08-25 03:24 639232245484452890
149 ms 74.220.199.6
7 2026-08-25 03:07 639232235157175331
253 ms 74.220.199.6
6 2026-08-25 02:14 639232203197189095
246 ms 74.220.199.6
5 2026-08-25 01:56 639232192844564298
137 ms 74.220.199.6
4 2026-08-25 01:39 639232182496008942
154 ms 74.220.199.6
3 2026-08-25 01:22 639232172197053132
139 ms 74.220.199.6
2 2026-08-25 00:28 639232140250307418
127 ms 74.220.199.6
1 2026-08-25 00:11 639232129927860324
261 ms 74.220.199.6