DNS response history for ns2.ared.my

ns2.ared.my 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-25. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 366 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.ared.my.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

366 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

101.99.84.132

Most recently resolved hosting IP on selected date

Successful Responses

38

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.ared.my

Showing DNS history for 2026-08-25 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
38 2026-08-25 13:15 639232597643611557
185 ms 101.99.84.132
37 2026-08-25 12:58 639232587225721862
517 ms 101.99.84.132
36 2026-08-25 12:41 639232576780683689
365 ms 101.99.84.132
35 2026-08-25 12:23 639232566381512620
263 ms 101.99.84.132
34 2026-08-25 12:06 639232556111768563
2195 ms 101.99.84.132
33 2026-08-25 11:49 639232545839529039
374 ms 101.99.84.132
32 2026-08-25 11:32 639232535349285207
525 ms 101.99.84.132
31 2026-08-25 11:14 639232524938080723
523 ms 101.99.84.132
30 2026-08-25 10:20 639232492740373468
208 ms 101.99.84.132
29 2026-08-25 10:03 639232482235303141
529 ms 101.99.84.132
28 2026-08-25 09:46 639232471861770303
179 ms 101.99.84.132
27 2026-08-25 09:28 639232461630217327
183 ms 101.99.84.132
26 2026-08-25 09:11 639232451282965990
522 ms 101.99.84.132
25 2026-08-25 08:54 639232440814614938
196 ms 101.99.84.132
24 2026-08-25 08:37 639232430410720425
192 ms 101.99.84.132
23 2026-08-25 08:19 639232420003096185
183 ms 101.99.84.132
22 2026-08-25 08:02 639232409467287444
180 ms 101.99.84.132
21 2026-08-25 07:44 639232399077195997
180 ms 101.99.84.132
20 2026-08-25 07:27 639232388731528337
366 ms 101.99.84.132
19 2026-08-25 07:10 639232378288598612
369 ms 101.99.84.132
18 2026-08-25 06:16 639232346196373643
515 ms 101.99.84.132
17 2026-08-25 05:59 639232336112370741
364 ms 101.99.84.132
16 2026-08-25 05:42 639232326146508970
179 ms 101.99.84.132
15 2026-08-25 05:26 639232316189381720
369 ms 101.99.84.132
14 2026-08-25 05:09 639232306217998913
2 ms 101.99.84.132
13 2026-08-25 04:53 639232296255744174
262 ms 101.99.84.132
12 2026-08-25 04:36 639232286095760789
523 ms 101.99.84.132
11 2026-08-25 04:19 639232276086186273
264 ms 101.99.84.132
10 2026-08-25 04:02 639232265900986425
3 ms 101.99.84.132
9 2026-08-25 03:45 639232255723518075
362 ms 101.99.84.132
8 2026-08-25 03:28 639232245484452890
257 ms 101.99.84.132
7 2026-08-25 03:11 639232235157175331
254 ms 101.99.84.132
6 2026-08-25 02:18 639232203197189095
523 ms 101.99.84.132
5 2026-08-25 02:01 639232192844564298
207 ms 101.99.84.132
4 2026-08-25 01:43 639232182496008942
363 ms 101.99.84.132
3 2026-08-25 01:26 639232172197053132
512 ms 101.99.84.132
2 2026-08-25 00:33 639232140250307418
206 ms 101.99.84.132
1 2026-08-25 00:16 639232129927860324
519 ms 101.99.84.132