DNS response history for ns2.tmcode.com

ns2.tmcode.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 521 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.tmcode.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

521 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

144.202.13.110

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.tmcode.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:06 639231765923559455
158 ms 144.202.13.110
33 2026-08-24 13:49 639231755868832964
1622 ms 144.202.13.110
32 2026-08-24 13:32 639231745628278877
156 ms 144.202.13.110
31 2026-08-24 13:15 639231735407682062
136 ms 144.202.13.110
30 2026-08-24 12:22 639231703815441688
258 ms 144.202.13.110
29 2026-08-24 12:06 639231693747052549
2136 ms 144.202.13.110
28 2026-08-24 11:49 639231683712487276
110 ms 144.202.13.110
27 2026-08-24 11:32 639231673513573868
266 ms 144.202.13.110
26 2026-08-24 10:39 639231641791249939
134 ms 144.202.13.110
25 2026-08-24 10:22 639231631866211033
2242 ms 144.202.13.110
24 2026-08-24 10:06 639231621644955316
138 ms 144.202.13.110
23 2026-08-24 09:49 639231611478799259
120 ms 144.202.13.110
22 2026-08-24 08:56 639231579923718211
222 ms 144.202.13.110
21 2026-08-24 08:39 639231569810702936
226 ms 144.202.13.110
20 2026-08-24 08:22 639231559762411619
118 ms 144.202.13.110
19 2026-08-24 08:05 639231549663595407
225 ms 144.202.13.110
18 2026-08-24 07:13 639231518076817246
111 ms 144.202.13.110
17 2026-08-24 06:56 639231508078650885
2273 ms 144.202.13.110
16 2026-08-24 06:40 639231498210697093
113 ms 144.202.13.110
15 2026-08-24 06:23 639231488109699360
119 ms 144.202.13.110
14 2026-08-24 05:31 639231456772510692
112 ms 144.202.13.110
13 2026-08-24 05:15 639231447084631185
129 ms 144.202.13.110
12 2026-08-24 04:58 639231437208519473
237 ms 144.202.13.110
11 2026-08-24 04:41 639231427209627490
2234 ms 144.202.13.110
10 2026-08-24 03:49 639231395791246644
247 ms 144.202.13.110
9 2026-08-24 03:33 639231386075551458
263 ms 144.202.13.110
8 2026-08-24 03:16 639231376208713791
154 ms 144.202.13.110
7 2026-08-24 03:00 639231366170589276
244 ms 144.202.13.110
6 2026-08-24 02:07 639231334732159368
2224 ms 144.202.13.110
5 2026-08-24 01:51 639231325035670078
254 ms 144.202.13.110
4 2026-08-24 01:35 639231315132253837
112 ms 144.202.13.110
3 2026-08-24 01:18 639231305014280808
242 ms 144.202.13.110
2 2026-08-24 00:26 639231273779380675
218 ms 144.202.13.110
1 2026-08-24 00:10 639231264180839154
153 ms 144.202.13.110