DNS response history for ns2.goodsignproduction.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

338 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

147.50.254.109

Most recently resolved hosting IP on selected date

Successful Responses

36

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.goodsignproduction.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
36 2026-08-25 12:40 639232576780683689
382 ms 147.50.254.109
35 2026-08-25 12:23 639232566381512620
376 ms 147.50.254.109
34 2026-08-25 12:06 639232556111768563
295 ms 147.50.254.109
33 2026-08-25 11:49 639232545839529039
436 ms 147.50.254.109
32 2026-08-25 11:31 639232535349285207
386 ms 147.50.254.109
31 2026-08-25 11:14 639232524938080723
384 ms 147.50.254.109
30 2026-08-25 10:20 639232492740373468
371 ms 147.50.254.109
29 2026-08-25 10:03 639232482235303141
187 ms 147.50.254.109
28 2026-08-25 09:45 639232471861770303
230 ms 147.50.254.109
27 2026-08-25 09:28 639232461630217327
387 ms 147.50.254.109
26 2026-08-25 09:11 639232451282965990
313 ms 147.50.254.109
25 2026-08-25 08:54 639232440814614938
191 ms 147.50.254.109
24 2026-08-25 08:36 639232430410720425
380 ms 147.50.254.109
23 2026-08-25 08:19 639232420003096185
394 ms 147.50.254.109
22 2026-08-25 08:02 639232409467287444
379 ms 147.50.254.109
21 2026-08-25 07:44 639232399077195997
415 ms 147.50.254.109
20 2026-08-25 07:27 639232388731528337
368 ms 147.50.254.109
19 2026-08-25 07:09 639232378288598612
412 ms 147.50.254.109
18 2026-08-25 06:16 639232346196373643
372 ms 147.50.254.109
17 2026-08-25 05:59 639232336112370741
199 ms 147.50.254.109
16 2026-08-25 05:42 639232326146508970
374 ms 147.50.254.109
15 2026-08-25 05:26 639232316189381720
398 ms 147.50.254.109
14 2026-08-25 05:09 639232306217998913
214 ms 147.50.254.109
13 2026-08-25 04:52 639232296255744174
4 ms 147.50.254.109
12 2026-08-25 04:36 639232286095760789
387 ms 147.50.254.109
11 2026-08-25 04:19 639232276086186273
208 ms 147.50.254.109
10 2026-08-25 04:02 639232265900986425
380 ms 147.50.254.109
9 2026-08-25 03:45 639232255723518075
375 ms 147.50.254.109
8 2026-08-25 03:28 639232245484452890
377 ms 147.50.254.109
7 2026-08-25 03:11 639232235157175331
245 ms 147.50.254.109
6 2026-08-25 02:18 639232203197189095
388 ms 147.50.254.109
5 2026-08-25 02:01 639232192844564298
381 ms 147.50.254.109
4 2026-08-25 01:43 639232182496008942
390 ms 147.50.254.109
3 2026-08-25 01:26 639232172197053132
372 ms 147.50.254.109
2 2026-08-25 00:33 639232140250307418
367 ms 147.50.254.109
1 2026-08-25 00:16 639232129927860324
438 ms 147.50.254.109