DNS response history for ns2.redvulpine.com

ns2.redvulpine.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-27. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 362 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.redvulpine.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

362 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.85.47.62

Most recently resolved hosting IP on selected date

Successful Responses

31

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

Showing DNS history for 2026-08-27 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
31 2026-08-27 10:07 639234212558002823
311 ms 66.85.47.62
30 2026-08-27 09:50 639234202117531850
304 ms 66.85.47.62
29 2026-08-27 09:33 639234191649612722
900 ms 66.85.47.62
28 2026-08-27 09:15 639234181105879568
298 ms 66.85.47.62
27 2026-08-27 08:58 639234170713214496
153 ms 66.85.47.62
26 2026-08-27 08:40 639234160341037652
159 ms 66.85.47.62
25 2026-08-27 08:23 639234149799404224
307 ms 66.85.47.62
24 2026-08-27 08:05 639234139553286469
653 ms 66.85.47.62
23 2026-08-27 07:12 639234107183588293
291 ms 66.85.47.62
22 2026-08-27 06:55 639234096905435724
282 ms 66.85.47.62
21 2026-08-27 06:37 639234086579410775
139 ms 66.85.47.62
20 2026-08-27 06:20 639234076291157956
227 ms 66.85.47.62
19 2026-08-27 06:03 639234065981939454
228 ms 66.85.47.62
18 2026-08-27 05:46 639234055548642997
118 ms 66.85.47.62
17 2026-08-27 05:28 639234045267979603
1679 ms 66.85.47.62
16 2026-08-27 05:11 639234034999717463
230 ms 66.85.47.62
15 2026-08-27 04:54 639234024739225358
9 ms 66.85.47.62
14 2026-08-27 04:37 639234014311170162
244 ms 66.85.47.62
13 2026-08-27 04:20 639234003806017640
230 ms 66.85.47.62
12 2026-08-27 04:02 639233993356203030
235 ms 66.85.47.62
11 2026-08-27 03:09 639233961301716608
227 ms 66.85.47.62
10 2026-08-27 02:51 639233950834200647
229 ms 66.85.47.62
9 2026-08-27 02:34 639233940431849026
1231 ms 66.85.47.62
8 2026-08-27 02:17 639233930110596398
1635 ms 66.85.47.62
7 2026-08-27 01:59 639233919705434540
114 ms 66.85.47.62
6 2026-08-27 01:42 639233909452807845
115 ms 66.85.47.62
5 2026-08-27 01:25 639233899096420820
37 ms 66.85.47.62
4 2026-08-27 01:08 639233888707824939
116 ms 66.85.47.62
3 2026-08-27 00:50 639233878461203802
163 ms 66.85.47.62
2 2026-08-27 00:33 639233868060868209
229 ms 66.85.47.62
1 2026-08-27 00:16 639233857450922991
115 ms 66.85.47.62