DNS response history for ns2.goodwebple.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

604 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.145.65.144

Most recently resolved hosting IP on selected date

Successful Responses

28

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.goodwebple.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
28 2026-08-25 09:46 639232471861770303
589 ms 218.145.65.144
27 2026-08-25 09:29 639232461630217327
585 ms 218.145.65.144
26 2026-08-25 09:12 639232451282965990
575 ms 218.145.65.144
25 2026-08-25 08:55 639232440814614938
319 ms 218.145.65.144
24 2026-08-25 08:37 639232430410720425
271 ms 218.145.65.144
23 2026-08-25 08:20 639232420003096185
580 ms 218.145.65.144
22 2026-08-25 08:03 639232409467287444
574 ms 218.145.65.144
21 2026-08-25 07:45 639232399077195997
603 ms 218.145.65.144
20 2026-08-25 07:28 639232388731528337
584 ms 218.145.65.144
19 2026-08-25 07:10 639232378288598612
574 ms 218.145.65.144
18 2026-08-25 06:17 639232346196373643
3 ms 218.145.65.144
17 2026-08-25 06:00 639232336112370741
600 ms 218.145.65.144
16 2026-08-25 05:43 639232326146508970
584 ms 218.145.65.144
15 2026-08-25 05:27 639232316189381720
583 ms 218.145.65.144
14 2026-08-25 05:10 639232306217998913
584 ms 218.145.65.144
13 2026-08-25 04:53 639232296255744174
585 ms 218.145.65.144
12 2026-08-25 04:37 639232286095760789
588 ms 218.145.65.144
11 2026-08-25 04:20 639232276086186273
570 ms 218.145.65.144
10 2026-08-25 04:03 639232265900986425
578 ms 218.145.65.144
9 2026-08-25 03:46 639232255723518075
579 ms 218.145.65.144
8 2026-08-25 03:29 639232245484452890
586 ms 218.145.65.144
7 2026-08-25 03:12 639232235157175331
575 ms 218.145.65.144
6 2026-08-25 02:19 639232203197189095
587 ms 218.145.65.144
5 2026-08-25 02:02 639232192844564298
573 ms 218.145.65.144
4 2026-08-25 01:44 639232182496008942
565 ms 218.145.65.144
3 2026-08-25 01:27 639232172197053132
2290 ms 218.145.65.144
2 2026-08-25 00:33 639232140250307418
602 ms 218.145.65.144
1 2026-08-25 00:17 639232129927860324
618 ms 218.145.65.144