DNS response history for ns2.highmarkmachine.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

405 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.69.79.186

Most recently resolved hosting IP on selected date

Successful Responses

35

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.highmarkmachine.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
35 2026-08-27 11:10 639234253963286387
111 ms 208.69.79.186
34 2026-08-27 10:53 639234243654907465
221 ms 208.69.79.186
33 2026-08-27 10:36 639234233269654413
126 ms 208.69.79.186
32 2026-08-27 10:18 639234222943951923
229 ms 208.69.79.186
31 2026-08-27 10:01 639234212558002823
241 ms 208.69.79.186
30 2026-08-27 09:44 639234202117531850
119 ms 208.69.79.186
29 2026-08-27 09:26 639234191649612722
216 ms 208.69.79.186
28 2026-08-27 09:09 639234181105879568
225 ms 208.69.79.186
27 2026-08-27 08:51 639234170713214496
214 ms 208.69.79.186
26 2026-08-27 08:34 639234160341037652
227 ms 208.69.79.186
25 2026-08-27 08:17 639234149799404224
215 ms 208.69.79.186
24 2026-08-27 07:59 639234139553286469
236 ms 208.69.79.186
23 2026-08-27 07:06 639234107183588293
227 ms 208.69.79.186
22 2026-08-27 06:48 639234096905435724
2222 ms 208.69.79.186
21 2026-08-27 06:31 639234086579410775
224 ms 208.69.79.186
20 2026-08-27 06:14 639234076291157956
102 ms 208.69.79.186
19 2026-08-27 05:57 639234065981939454
225 ms 208.69.79.186
18 2026-08-27 05:40 639234055548642997
126 ms 208.69.79.186
17 2026-08-27 05:22 639234045267979603
2111 ms 208.69.79.186
16 2026-08-27 05:05 639234034999717463
259 ms 208.69.79.186
15 2026-08-27 04:48 639234024739225358
155 ms 208.69.79.186
14 2026-08-27 04:31 639234014311170162
223 ms 208.69.79.186
13 2026-08-27 04:13 639234003806017640
116 ms 208.69.79.186
12 2026-08-27 03:56 639233993356203030
221 ms 208.69.79.186
11 2026-08-27 03:03 639233961301716608
2115 ms 208.69.79.186
10 2026-08-27 02:45 639233950834200647
132 ms 208.69.79.186
9 2026-08-27 02:28 639233940431849026
107 ms 208.69.79.186
8 2026-08-27 02:10 639233930110596398
122 ms 208.69.79.186
7 2026-08-27 01:53 639233919705434540
215 ms 208.69.79.186
6 2026-08-27 01:36 639233909452807845
104 ms 208.69.79.186
5 2026-08-27 01:19 639233899096420820
214 ms 208.69.79.186
4 2026-08-27 01:01 639233888707824939
213 ms 208.69.79.186
3 2026-08-27 00:44 639233878461203802
118 ms 208.69.79.186
2 2026-08-27 00:27 639233868060868209
106 ms 208.69.79.186
1 2026-08-27 00:09 639233857450922991
2133 ms 208.69.79.186