DNS response history for ns5.dns2go.com

ns5.dns2go.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-24. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 429 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 ns5.dns2go.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

429 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.217.38.38

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 ns5.dns2go.com

Showing DNS history for 2026-08-24 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-24 14:57 639231797631669865
2121 ms 67.217.38.38
34 2026-08-24 14:04 639231765923559455
12 ms 67.217.38.38
33 2026-08-24 13:47 639231755868832964
232 ms 67.217.38.38
32 2026-08-24 13:30 639231745628278877
230 ms 67.217.38.38
31 2026-08-24 13:13 639231735407682062
133 ms 67.217.38.38
30 2026-08-24 12:20 639231703815441688
121 ms 67.217.38.38
29 2026-08-24 12:03 639231693747052549
115 ms 67.217.38.38
28 2026-08-24 11:47 639231683712487276
113 ms 67.217.38.38
27 2026-08-24 11:30 639231673513573868
236 ms 67.217.38.38
26 2026-08-24 10:37 639231641791249939
225 ms 67.217.38.38
25 2026-08-24 10:20 639231631866211033
280 ms 67.217.38.38
24 2026-08-24 10:03 639231621644955316
2131 ms 67.217.38.38
23 2026-08-24 09:46 639231611478799259
44 ms 67.217.38.38
22 2026-08-24 08:54 639231579923718211
222 ms 67.217.38.38
21 2026-08-24 08:37 639231569810702936
31 ms 67.217.38.38
20 2026-08-24 08:20 639231559762411619
17 ms 67.217.38.38
19 2026-08-24 08:03 639231549663595407
116 ms 67.217.38.38
18 2026-08-24 07:11 639231518076817246
229 ms 67.217.38.38
17 2026-08-24 06:54 639231508078650885
258 ms 67.217.38.38
16 2026-08-24 06:38 639231498210697093
229 ms 67.217.38.38
15 2026-08-24 06:21 639231488109699360
231 ms 67.217.38.38
14 2026-08-24 05:29 639231456772510692
4005 ms 67.217.38.38
13 2026-08-24 05:13 639231447084631185
186 ms 67.217.38.38
12 2026-08-24 04:56 639231437208519473
222 ms 67.217.38.38
11 2026-08-24 04:39 639231427209627490
37 ms 67.217.38.38
10 2026-08-24 03:47 639231395791246644
5 ms 67.217.38.38
9 2026-08-24 03:31 639231386075551458
128 ms 67.217.38.38
8 2026-08-24 03:14 639231376208713791
228 ms 67.217.38.38
7 2026-08-24 02:58 639231366170589276
128 ms 67.217.38.38
6 2026-08-24 02:05 639231334732159368
124 ms 67.217.38.38
5 2026-08-24 01:49 639231325035670078
233 ms 67.217.38.38
4 2026-08-24 01:32 639231315132253837
241 ms 67.217.38.38
3 2026-08-24 01:16 639231305014280808
143 ms 67.217.38.38
2 2026-08-24 00:24 639231273779380675
2007 ms 67.217.38.38
1 2026-08-24 00:08 639231264180839154
6 ms 67.217.38.38