DNS response history for ns2.go3d.com

ns2.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-28. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 524 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.go3d.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

524 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:22

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

32

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.go3d.com

Showing DNS history for 2026-08-28 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
32 2026-08-28 13:22 639235195230848570
287 ms 96.125.179.23
31 2026-08-28 13:05 639235184840503274
295 ms 96.125.179.23
30 2026-08-28 12:47 639235174453894956
306 ms 96.125.179.23
29 2026-08-28 12:30 639235163898672622
298 ms 96.125.179.23
28 2026-08-28 11:37 639235132147470568
307 ms 96.125.179.23
27 2026-08-28 11:20 639235121907744088
302 ms 96.125.179.23
26 2026-08-28 11:03 639235111428014262
2131 ms 96.125.179.23
25 2026-08-28 10:45 639235100921813626
2181 ms 96.125.179.23
24 2026-08-28 09:51 639235068670703481
288 ms 96.125.179.23
23 2026-08-28 09:34 639235058337459445
305 ms 96.125.179.23
22 2026-08-28 09:17 639235047825109146
299 ms 96.125.179.23
21 2026-08-28 08:59 639235037383229033
285 ms 96.125.179.23
20 2026-08-28 08:06 639235005619242711
290 ms 96.125.179.23
19 2026-08-28 07:49 639234995310346584
2146 ms 96.125.179.23
18 2026-08-28 07:32 639234984946548933
294 ms 96.125.179.23
17 2026-08-28 07:14 639234974608077290
289 ms 96.125.179.23
16 2026-08-28 06:21 639234942529845595
294 ms 96.125.179.23
15 2026-08-28 06:04 639234932259126627
308 ms 96.125.179.23
14 2026-08-28 05:47 639234921916735988
286 ms 96.125.179.23
13 2026-08-28 05:29 639234911470038027
294 ms 96.125.179.23
12 2026-08-28 04:36 639234879588411654
287 ms 96.125.179.23
11 2026-08-28 04:19 639234869341589104
293 ms 96.125.179.23
10 2026-08-28 04:02 639234859012216675
142 ms 96.125.179.23
9 2026-08-28 03:44 639234848695364934
289 ms 96.125.179.23
8 2026-08-28 02:52 639234816952458162
288 ms 96.125.179.23
7 2026-08-28 02:35 639234806773081598
290 ms 96.125.179.23
6 2026-08-28 02:17 639234796382955255
289 ms 96.125.179.23
5 2026-08-28 02:00 639234786015782563
285 ms 96.125.179.23
4 2026-08-28 01:06 639234753811917646
2266 ms 96.125.179.23
3 2026-08-28 00:49 639234743739767811
286 ms 96.125.179.23
2 2026-08-28 00:32 639234733372362811
288 ms 96.125.179.23
1 2026-08-28 00:15 639234723048550337
290 ms 96.125.179.23