DNS response history for ns2.ambermarks.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

118 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

184.94.217.135

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.ambermarks.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
34 2026-08-24 14:11 639231765923559455
229 ms 184.94.217.135
33 2026-08-24 13:55 639231755868832964
230 ms 184.94.217.135
32 2026-08-24 13:38 639231745628278877
3 ms 184.94.217.135
31 2026-08-24 13:21 639231735407682062
4 ms 184.94.217.135
30 2026-08-24 12:28 639231703815441688
226 ms 184.94.217.135
29 2026-08-24 12:11 639231693747052549
223 ms 184.94.217.135
28 2026-08-24 11:55 639231683712487276
3 ms 184.94.217.135
27 2026-08-24 11:38 639231673513573868
229 ms 184.94.217.135
26 2026-08-24 10:44 639231641791249939
228 ms 184.94.217.135
25 2026-08-24 10:28 639231631866211033
227 ms 184.94.217.135
24 2026-08-24 10:11 639231621644955316
227 ms 184.94.217.135
23 2026-08-24 09:54 639231611478799259
4 ms 184.94.217.135
22 2026-08-24 09:01 639231579923718211
4 ms 184.94.217.135
21 2026-08-24 08:45 639231569810702936
220 ms 184.94.217.135
20 2026-08-24 08:28 639231559762411619
225 ms 184.94.217.135
19 2026-08-24 08:11 639231549663595407
4 ms 184.94.217.135
18 2026-08-24 07:18 639231518076817246
227 ms 184.94.217.135
17 2026-08-24 07:02 639231508078650885
2 ms 184.94.217.135
16 2026-08-24 06:45 639231498210697093
239 ms 184.94.217.135
15 2026-08-24 06:29 639231488109699360
222 ms 184.94.217.135
14 2026-08-24 05:36 639231456772510692
2 ms 184.94.217.135
13 2026-08-24 05:20 639231447084631185
2 ms 184.94.217.135
12 2026-08-24 05:03 639231437208519473
226 ms 184.94.217.135
11 2026-08-24 04:47 639231427209627490
2 ms 184.94.217.135
10 2026-08-24 03:54 639231395791246644
115 ms 184.94.217.135
9 2026-08-24 03:38 639231386075551458
3 ms 184.94.217.135
8 2026-08-24 03:22 639231376208713791
229 ms 184.94.217.135
7 2026-08-24 03:05 639231366170589276
2 ms 184.94.217.135
6 2026-08-24 02:13 639231334732159368
227 ms 184.94.217.135
5 2026-08-24 01:56 639231325035670078
3 ms 184.94.217.135
4 2026-08-24 01:40 639231315132253837
2 ms 184.94.217.135
3 2026-08-24 01:24 639231305014280808
3 ms 184.94.217.135
2 2026-08-24 00:31 639231273779380675
4 ms 184.94.217.135
1 2026-08-24 00:15 639231264180839154
225 ms 184.94.217.135