DNS response history for ns5.jimvaughan.com

ns5.jimvaughan.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 438 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 ns5.jimvaughan.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

438 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.64.137.150

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 ns5.jimvaughan.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:37 639232576780683689
239 ms 64.64.137.150
35 2026-08-25 12:19 639232566381512620
240 ms 64.64.137.150
34 2026-08-25 12:02 639232556111768563
253 ms 64.64.137.150
33 2026-08-25 11:45 639232545839529039
243 ms 64.64.137.150
32 2026-08-25 11:28 639232535349285207
247 ms 64.64.137.150
31 2026-08-25 11:10 639232524938080723
2131 ms 64.64.137.150
30 2026-08-25 10:17 639232492740373468
258 ms 64.64.137.150
29 2026-08-25 10:00 639232482235303141
6 ms 64.64.137.150
28 2026-08-25 09:42 639232471861770303
262 ms 64.64.137.150
27 2026-08-25 09:25 639232461630217327
257 ms 64.64.137.150
26 2026-08-25 09:08 639232451282965990
15 ms 64.64.137.150
25 2026-08-25 08:50 639232440814614938
261 ms 64.64.137.150
24 2026-08-25 08:33 639232430410720425
261 ms 64.64.137.150
23 2026-08-25 08:16 639232420003096185
251 ms 64.64.137.150
22 2026-08-25 07:58 639232409467287444
252 ms 64.64.137.150
21 2026-08-25 07:41 639232399077195997
240 ms 64.64.137.150
20 2026-08-25 07:23 639232388731528337
256 ms 64.64.137.150
19 2026-08-25 07:06 639232378288598612
269 ms 64.64.137.150
18 2026-08-25 06:12 639232346196373643
240 ms 64.64.137.150
17 2026-08-25 05:56 639232336112370741
129 ms 64.64.137.150
16 2026-08-25 05:39 639232326146508970
249 ms 64.64.137.150
15 2026-08-25 05:22 639232316189381720
2163 ms 64.64.137.150
14 2026-08-25 05:06 639232306217998913
257 ms 64.64.137.150
13 2026-08-25 04:49 639232296255744174
250 ms 64.64.137.150
12 2026-08-25 04:32 639232286095760789
259 ms 64.64.137.150
11 2026-08-25 04:15 639232276086186273
126 ms 64.64.137.150
10 2026-08-25 03:59 639232265900986425
248 ms 64.64.137.150
9 2026-08-25 03:42 639232255723518075
254 ms 64.64.137.150
8 2026-08-25 03:25 639232245484452890
243 ms 64.64.137.150
7 2026-08-25 03:07 639232235157175331
255 ms 64.64.137.150
6 2026-08-25 02:14 639232203197189095
240 ms 64.64.137.150
5 2026-08-25 01:57 639232192844564298
2136 ms 64.64.137.150
4 2026-08-25 01:40 639232182496008942
131 ms 64.64.137.150
3 2026-08-25 01:22 639232172197053132
242 ms 64.64.137.150
2 2026-08-25 00:29 639232140250307418
130 ms 64.64.137.150
1 2026-08-25 00:12 639232129927860324
2265 ms 64.64.137.150