DNS response history for ns2.amarscales.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

400 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.50.160.20

Most recently resolved hosting IP on selected date

Successful Responses

30

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.amarscales.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
30 2026-08-24 12:23 639231703815441688
3 ms 103.50.160.20
29 2026-08-24 12:06 639231693747052549
317 ms 103.50.160.20
28 2026-08-24 11:49 639231683712487276
3 ms 103.50.160.20
27 2026-08-24 11:32 639231673513573868
2008 ms 103.50.160.20
26 2026-08-24 10:39 639231641791249939
306 ms 103.50.160.20
25 2026-08-24 10:23 639231631866211033
294 ms 103.50.160.20
24 2026-08-24 10:06 639231621644955316
3 ms 103.50.160.20
23 2026-08-24 09:49 639231611478799259
5 ms 103.50.160.20
22 2026-08-24 08:56 639231579923718211
4 ms 103.50.160.20
21 2026-08-24 08:40 639231569810702936
5 ms 103.50.160.20
20 2026-08-24 08:22 639231559762411619
3 ms 103.50.160.20
19 2026-08-24 08:06 639231549663595407
163 ms 103.50.160.20
18 2026-08-24 07:13 639231518076817246
305 ms 103.50.160.20
17 2026-08-24 06:57 639231508078650885
144 ms 103.50.160.20
16 2026-08-24 06:40 639231498210697093
2207 ms 103.50.160.20
15 2026-08-24 06:23 639231488109699360
295 ms 103.50.160.20
14 2026-08-24 05:31 639231456772510692
5 ms 103.50.160.20
13 2026-08-24 05:15 639231447084631185
3 ms 103.50.160.20
12 2026-08-24 04:58 639231437208519473
4008 ms 103.50.160.20
11 2026-08-24 04:42 639231427209627490
4 ms 103.50.160.20
10 2026-08-24 03:49 639231395791246644
270 ms 103.50.160.20
9 2026-08-24 03:33 639231386075551458
388 ms 103.50.160.20
8 2026-08-24 03:17 639231376208713791
294 ms 103.50.160.20
7 2026-08-24 03:00 639231366170589276
209 ms 103.50.160.20
6 2026-08-24 02:08 639231334732159368
29 ms 103.50.160.20
5 2026-08-24 01:51 639231325035670078
163 ms 103.50.160.20
4 2026-08-24 01:35 639231315132253837
369 ms 103.50.160.20
3 2026-08-24 01:18 639231305014280808
4 ms 103.50.160.20
2 2026-08-24 00:26 639231273779380675
193 ms 103.50.160.20
1 2026-08-24 00:10 639231264180839154
3 ms 103.50.160.20