DNS response history for ns2.oncomarks.com

ns2.oncomarks.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-24. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 167 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.oncomarks.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

167 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.8.173.170

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

Showing DNS history for 2026-08-24 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-24 14:59 639231797631669865
100 ms 185.8.173.170
34 2026-08-24 14:06 639231765923559455
3 ms 185.8.173.170
33 2026-08-24 13:49 639231755868832964
170 ms 185.8.173.170
32 2026-08-24 13:32 639231745628278877
178 ms 185.8.173.170
31 2026-08-24 13:15 639231735407682062
214 ms 185.8.173.170
30 2026-08-24 12:22 639231703815441688
177 ms 185.8.173.170
29 2026-08-24 12:06 639231693747052549
15 ms 185.8.173.170
28 2026-08-24 11:49 639231683712487276
181 ms 185.8.173.170
27 2026-08-24 11:32 639231673513573868
4 ms 185.8.173.170
26 2026-08-24 10:39 639231641791249939
84 ms 185.8.173.170
25 2026-08-24 10:23 639231631866211033
176 ms 185.8.173.170
24 2026-08-24 10:06 639231621644955316
204 ms 185.8.173.170
23 2026-08-24 09:49 639231611478799259
190 ms 185.8.173.170
22 2026-08-24 08:56 639231579923718211
31 ms 185.8.173.170
21 2026-08-24 08:39 639231569810702936
2 ms 185.8.173.170
20 2026-08-24 08:22 639231559762411619
4 ms 185.8.173.170
19 2026-08-24 08:06 639231549663595407
189 ms 185.8.173.170
18 2026-08-24 07:13 639231518076817246
173 ms 185.8.173.170
17 2026-08-24 06:57 639231508078650885
156 ms 185.8.173.170
16 2026-08-24 06:40 639231498210697093
117 ms 185.8.173.170
15 2026-08-24 06:23 639231488109699360
8 ms 185.8.173.170
14 2026-08-24 05:31 639231456772510692
175 ms 185.8.173.170
13 2026-08-24 05:15 639231447084631185
175 ms 185.8.173.170
12 2026-08-24 04:58 639231437208519473
6 ms 185.8.173.170
11 2026-08-24 04:42 639231427209627490
193 ms 185.8.173.170
10 2026-08-24 03:49 639231395791246644
5 ms 185.8.173.170
9 2026-08-24 03:33 639231386075551458
3 ms 185.8.173.170
8 2026-08-24 03:17 639231376208713791
176 ms 185.8.173.170
7 2026-08-24 03:00 639231366170589276
165 ms 185.8.173.170
6 2026-08-24 02:08 639231334732159368
2 ms 185.8.173.170
5 2026-08-24 01:51 639231325035670078
22 ms 185.8.173.170
4 2026-08-24 01:35 639231315132253837
2168 ms 185.8.173.170
3 2026-08-24 01:18 639231305014280808
185 ms 185.8.173.170
2 2026-08-24 00:26 639231273779380675
175 ms 185.8.173.170
1 2026-08-24 00:10 639231264180839154
3 ms 185.8.173.170