DNS response history for ns1.go3d.com

ns1.go3d.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 37 DNS check records, 37 successful responses, 0 failed responses, and 235 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 ns1.go3d.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

235 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.125.179.23

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns1.go3d.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
37 2026-08-25 12:56 639232587225721862
297 ms 96.125.179.23
36 2026-08-25 12:38 639232576780683689
298 ms 96.125.179.23
35 2026-08-25 12:21 639232566381512620
181 ms 96.125.179.23
34 2026-08-25 12:04 639232556111768563
290 ms 96.125.179.23
33 2026-08-25 11:47 639232545839529039
141 ms 96.125.179.23
32 2026-08-25 11:29 639232535349285207
292 ms 96.125.179.23
31 2026-08-25 11:12 639232524938080723
193 ms 96.125.179.23
30 2026-08-25 10:18 639232492740373468
291 ms 96.125.179.23
29 2026-08-25 10:01 639232482235303141
291 ms 96.125.179.23
28 2026-08-25 09:44 639232471861770303
143 ms 96.125.179.23
27 2026-08-25 09:26 639232461630217327
150 ms 96.125.179.23
26 2026-08-25 09:09 639232451282965990
287 ms 96.125.179.23
25 2026-08-25 08:52 639232440814614938
288 ms 96.125.179.23
24 2026-08-25 08:34 639232430410720425
289 ms 96.125.179.23
23 2026-08-25 08:17 639232420003096185
292 ms 96.125.179.23
22 2026-08-25 08:00 639232409467287444
142 ms 96.125.179.23
21 2026-08-25 07:42 639232399077195997
288 ms 96.125.179.23
20 2026-08-25 07:25 639232388731528337
207 ms 96.125.179.23
19 2026-08-25 07:08 639232378288598612
147 ms 96.125.179.23
18 2026-08-25 06:14 639232346196373643
294 ms 96.125.179.23
17 2026-08-25 05:57 639232336112370741
152 ms 96.125.179.23
16 2026-08-25 05:41 639232326146508970
140 ms 96.125.179.23
15 2026-08-25 05:24 639232316189381720
283 ms 96.125.179.23
14 2026-08-25 05:07 639232306217998913
144 ms 96.125.179.23
13 2026-08-25 04:51 639232296255744174
283 ms 96.125.179.23
12 2026-08-25 04:34 639232286095760789
289 ms 96.125.179.23
11 2026-08-25 04:17 639232276086186273
131 ms 96.125.179.23
10 2026-08-25 04:00 639232265900986425
291 ms 96.125.179.23
9 2026-08-25 03:43 639232255723518075
288 ms 96.125.179.23
8 2026-08-25 03:26 639232245484452890
145 ms 96.125.179.23
7 2026-08-25 03:09 639232235157175331
288 ms 96.125.179.23
6 2026-08-25 02:16 639232203197189095
289 ms 96.125.179.23
5 2026-08-25 01:59 639232192844564298
292 ms 96.125.179.23
4 2026-08-25 01:41 639232182496008942
140 ms 96.125.179.23
3 2026-08-25 01:24 639232172197053132
290 ms 96.125.179.23
2 2026-08-25 00:31 639232140250307418
145 ms 96.125.179.23
1 2026-08-25 00:14 639232129927860324
288 ms 96.125.179.23