DNS response history for ns312.tvmserver.com

ns312.tvmserver.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 29 DNS check records, 29 successful responses, 0 failed responses, and 297 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 ns312.tvmserver.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

297 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

43.254.29.101

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns312.tvmserver.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
29 2026-08-24 11:57 639231693747052549
84 ms 43.254.29.101
28 2026-08-24 11:41 639231683712487276
17 ms 43.254.29.101
27 2026-08-24 11:24 639231673513573868
22 ms 43.254.29.101
26 2026-08-24 10:31 639231641791249939
40 ms 43.254.29.101
25 2026-08-24 10:14 639231631866211033
25 ms 43.254.29.101
24 2026-08-24 09:57 639231621644955316
8 ms 43.254.29.101
23 2026-08-24 09:40 639231611478799259
2028 ms 43.254.29.101
22 2026-08-24 08:48 639231579923718211
45 ms 43.254.29.101
21 2026-08-24 08:31 639231569810702936
29 ms 43.254.29.101
20 2026-08-24 08:14 639231559762411619
15 ms 43.254.29.101
19 2026-08-24 07:57 639231549663595407
25 ms 43.254.29.101
18 2026-08-24 07:05 639231518076817246
13 ms 43.254.29.101
17 2026-08-24 06:48 639231508078650885
37 ms 43.254.29.101
16 2026-08-24 06:31 639231498210697093
14 ms 43.254.29.101
15 2026-08-24 06:15 639231488109699360
25 ms 43.254.29.101
14 2026-08-24 05:22 639231456772510692
22 ms 43.254.29.101
13 2026-08-24 05:06 639231447084631185
7 ms 43.254.29.101
12 2026-08-24 04:50 639231437208519473
9 ms 43.254.29.101
11 2026-08-24 04:33 639231427209627490
4 ms 43.254.29.101
10 2026-08-24 03:41 639231395791246644
4034 ms 43.254.29.101
9 2026-08-24 03:25 639231386075551458
19 ms 43.254.29.101
8 2026-08-24 03:08 639231376208713791
4 ms 43.254.29.101
7 2026-08-24 02:51 639231366170589276
45 ms 43.254.29.101
6 2026-08-24 01:59 639231334732159368
2020 ms 43.254.29.101
5 2026-08-24 01:43 639231325035670078
5 ms 43.254.29.101
4 2026-08-24 01:26 639231315132253837
5 ms 43.254.29.101
3 2026-08-24 01:10 639231305014280808
3 ms 43.254.29.101
2 2026-08-24 00:17 639231273779380675
13 ms 43.254.29.101
1 2026-08-24 00:01 639231264180839154
4 ms 43.254.29.101