DNS response history for ns2.wdbhst.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

407 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.225.188.222

Most recently resolved hosting IP on selected date

Successful Responses

34

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.wdbhst.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
34 2026-08-25 12:06 639232556111768563
240 ms 67.225.188.222
33 2026-08-25 11:49 639232545839529039
138 ms 67.225.188.222
32 2026-08-25 11:31 639232535349285207
116 ms 67.225.188.222
31 2026-08-25 11:14 639232524938080723
231 ms 67.225.188.222
30 2026-08-25 10:20 639232492740373468
2123 ms 67.225.188.222
29 2026-08-25 10:03 639232482235303141
124 ms 67.225.188.222
28 2026-08-25 09:45 639232471861770303
232 ms 67.225.188.222
27 2026-08-25 09:28 639232461630217327
118 ms 67.225.188.222
26 2026-08-25 09:11 639232451282965990
117 ms 67.225.188.222
25 2026-08-25 08:54 639232440814614938
246 ms 67.225.188.222
24 2026-08-25 08:36 639232430410720425
112 ms 67.225.188.222
23 2026-08-25 08:19 639232420003096185
229 ms 67.225.188.222
22 2026-08-25 08:02 639232409467287444
233 ms 67.225.188.222
21 2026-08-25 07:44 639232399077195997
3758 ms 67.225.188.222
20 2026-08-25 07:27 639232388731528337
232 ms 67.225.188.222
19 2026-08-25 07:09 639232378288598612
242 ms 67.225.188.222
18 2026-08-25 06:16 639232346196373643
238 ms 67.225.188.222
17 2026-08-25 05:59 639232336112370741
114 ms 67.225.188.222
16 2026-08-25 05:42 639232326146508970
116 ms 67.225.188.222
15 2026-08-25 05:26 639232316189381720
136 ms 67.225.188.222
14 2026-08-25 05:09 639232306217998913
224 ms 67.225.188.222
13 2026-08-25 04:52 639232296255744174
229 ms 67.225.188.222
12 2026-08-25 04:36 639232286095760789
222 ms 67.225.188.222
11 2026-08-25 04:19 639232276086186273
121 ms 67.225.188.222
10 2026-08-25 04:02 639232265900986425
226 ms 67.225.188.222
9 2026-08-25 03:45 639232255723518075
126 ms 67.225.188.222
8 2026-08-25 03:28 639232245484452890
816 ms 67.225.188.222
7 2026-08-25 03:11 639232235157175331
126 ms 67.225.188.222
6 2026-08-25 02:18 639232203197189095
223 ms 67.225.188.222
5 2026-08-25 02:01 639232192844564298
1632 ms 67.225.188.222
4 2026-08-25 01:43 639232182496008942
125 ms 67.225.188.222
3 2026-08-25 01:26 639232172197053132
221 ms 67.225.188.222
2 2026-08-25 00:33 639232140250307418
234 ms 67.225.188.222
1 2026-08-25 00:16 639232129927860324
223 ms 67.225.188.222