DNS response history for ns2.nintech.my

ns2.nintech.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 492 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.nintech.my.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

492 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

113.23.169.119

Most recently resolved hosting IP on selected date

Successful Responses

36

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

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
36 2026-08-24 15:20 639231807961539652
165 ms 113.23.169.119
35 2026-08-24 15:03 639231797631669865
647 ms 113.23.169.119
34 2026-08-24 14:10 639231765923559455
487 ms 113.23.169.119
33 2026-08-24 13:53 639231755868832964
480 ms 113.23.169.119
32 2026-08-24 13:36 639231745628278877
164 ms 113.23.169.119
31 2026-08-24 13:19 639231735407682062
646 ms 113.23.169.119
30 2026-08-24 12:26 639231703815441688
4 ms 113.23.169.119
29 2026-08-24 12:10 639231693747052549
642 ms 113.23.169.119
28 2026-08-24 11:53 639231683712487276
161 ms 113.23.169.119
27 2026-08-24 11:36 639231673513573868
4 ms 113.23.169.119
26 2026-08-24 10:43 639231641791249939
644 ms 113.23.169.119
25 2026-08-24 10:26 639231631866211033
649 ms 113.23.169.119
24 2026-08-24 10:10 639231621644955316
2952 ms 113.23.169.119
23 2026-08-24 09:53 639231611478799259
7 ms 113.23.169.119
22 2026-08-24 09:00 639231579923718211
642 ms 113.23.169.119
21 2026-08-24 08:43 639231569810702936
550 ms 113.23.169.119
20 2026-08-24 08:26 639231559762411619
649 ms 113.23.169.119
19 2026-08-24 08:10 639231549663595407
4 ms 113.23.169.119
18 2026-08-24 07:17 639231518076817246
1498 ms 113.23.169.119
17 2026-08-24 07:00 639231508078650885
721 ms 113.23.169.119
16 2026-08-24 06:44 639231498210697093
735 ms 113.23.169.119
15 2026-08-24 06:27 639231488109699360
174 ms 113.23.169.119
14 2026-08-24 05:35 639231456772510692
666 ms 113.23.169.119
13 2026-08-24 05:18 639231447084631185
2 ms 113.23.169.119
12 2026-08-24 05:02 639231437208519473
9 ms 113.23.169.119
11 2026-08-24 04:45 639231427209627490
3 ms 113.23.169.119
10 2026-08-24 03:53 639231395791246644
652 ms 113.23.169.119
9 2026-08-24 03:37 639231386075551458
667 ms 113.23.169.119
8 2026-08-24 03:20 639231376208713791
3 ms 113.23.169.119
7 2026-08-24 03:04 639231366170589276
2 ms 113.23.169.119
6 2026-08-24 02:11 639231334732159368
3 ms 113.23.169.119
5 2026-08-24 01:55 639231325035670078
1166 ms 113.23.169.119
4 2026-08-24 01:39 639231315132253837
3 ms 113.23.169.119
3 2026-08-24 01:22 639231305014280808
696 ms 113.23.169.119
2 2026-08-24 00:29 639231273779380675
647 ms 113.23.169.119
1 2026-08-24 00:14 639231264180839154
553 ms 113.23.169.119