DNS response history for ns2.catched.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

293 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.203.26.124

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.catched.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
38 2026-08-24 15:40 639231828211839931
23 ms 116.203.26.124
37 2026-08-24 15:23 639231818080917481
36 ms 116.203.26.124
36 2026-08-24 15:06 639231807961539652
45 ms 116.203.26.124
35 2026-08-24 14:49 639231797631669865
23 ms 116.203.26.124
34 2026-08-24 13:56 639231765923559455
33 ms 116.203.26.124
33 2026-08-24 13:39 639231755868832964
54 ms 116.203.26.124
32 2026-08-24 13:22 639231745628278877
21 ms 116.203.26.124
31 2026-08-24 13:05 639231735407682062
48 ms 116.203.26.124
30 2026-08-24 12:13 639231703815441688
8 ms 116.203.26.124
29 2026-08-24 11:56 639231693747052549
42 ms 116.203.26.124
28 2026-08-24 11:39 639231683712487276
20 ms 116.203.26.124
27 2026-08-24 11:22 639231673513573868
36 ms 116.203.26.124
26 2026-08-24 10:29 639231641791249939
6 ms 116.203.26.124
25 2026-08-24 10:13 639231631866211033
105 ms 116.203.26.124
24 2026-08-24 09:56 639231621644955316
2036 ms 116.203.26.124
23 2026-08-24 09:39 639231611478799259
9 ms 116.203.26.124
22 2026-08-24 08:46 639231579923718211
37 ms 116.203.26.124
21 2026-08-24 08:29 639231569810702936
136 ms 116.203.26.124
20 2026-08-24 08:13 639231559762411619
6 ms 116.203.26.124
19 2026-08-24 07:56 639231549663595407
16 ms 116.203.26.124
18 2026-08-24 07:03 639231518076817246
18 ms 116.203.26.124
17 2026-08-24 06:46 639231508078650885
2053 ms 116.203.26.124
16 2026-08-24 06:30 639231498210697093
2019 ms 116.203.26.124
15 2026-08-24 06:13 639231488109699360
27 ms 116.203.26.124
14 2026-08-24 05:21 639231456772510692
46 ms 116.203.26.124
13 2026-08-24 05:05 639231447084631185
2020 ms 116.203.26.124
12 2026-08-24 04:48 639231437208519473
37 ms 116.203.26.124
11 2026-08-24 04:32 639231427209627490
6 ms 116.203.26.124
10 2026-08-24 03:39 639231395791246644
30 ms 116.203.26.124
9 2026-08-24 03:23 639231386075551458
23 ms 116.203.26.124
8 2026-08-24 03:07 639231376208713791
18 ms 116.203.26.124
7 2026-08-24 02:50 639231366170589276
9 ms 116.203.26.124
6 2026-08-24 01:58 639231334732159368
27 ms 116.203.26.124
5 2026-08-24 01:41 639231325035670078
6 ms 116.203.26.124
4 2026-08-24 01:25 639231315132253837
2019 ms 116.203.26.124
3 2026-08-24 01:08 639231305014280808
26 ms 116.203.26.124
2 2026-08-24 00:16 639231273779380675
6 ms 116.203.26.124
1 2026-08-24 00:00 639231264180839154
5 ms 116.203.26.124