DNS response history for ns3.jp10.tmd.cloud

ns3.jp10.tmd.cloud 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 26 DNS check records, 26 successful responses, 0 failed responses, and 328 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 ns3.jp10.tmd.cloud.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

328 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.182.124.118

Most recently resolved hosting IP on selected date

Successful Responses

26

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 ns3.jp10.tmd.cloud

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
26 2026-08-24 10:33 639231641791249939
21 ms 202.182.124.118
25 2026-08-24 10:17 639231631866211033
9 ms 202.182.124.118
24 2026-08-24 10:00 639231621644955316
24 ms 202.182.124.118
23 2026-08-24 09:43 639231611478799259
9 ms 202.182.124.118
22 2026-08-24 08:50 639231579923718211
48 ms 202.182.124.118
21 2026-08-24 08:33 639231569810702936
6 ms 202.182.124.118
20 2026-08-24 08:16 639231559762411619
8 ms 202.182.124.118
19 2026-08-24 08:00 639231549663595407
48 ms 202.182.124.118
18 2026-08-24 07:07 639231518076817246
27 ms 202.182.124.118
17 2026-08-24 06:51 639231508078650885
9 ms 202.182.124.118
16 2026-08-24 06:34 639231498210697093
18 ms 202.182.124.118
15 2026-08-24 06:17 639231488109699360
5 ms 202.182.124.118
14 2026-08-24 05:25 639231456772510692
32 ms 202.182.124.118
13 2026-08-24 05:09 639231447084631185
4 ms 202.182.124.118
12 2026-08-24 04:52 639231437208519473
2027 ms 202.182.124.118
11 2026-08-24 04:36 639231427209627490
6 ms 202.182.124.118
10 2026-08-24 03:43 639231395791246644
4046 ms 202.182.124.118
9 2026-08-24 03:27 639231386075551458
29 ms 202.182.124.118
8 2026-08-24 03:11 639231376208713791
5 ms 202.182.124.118
7 2026-08-24 02:54 639231366170589276
14 ms 202.182.124.118
6 2026-08-24 02:02 639231334732159368
30 ms 202.182.124.118
5 2026-08-24 01:45 639231325035670078
36 ms 202.182.124.118
4 2026-08-24 01:29 639231315132253837
2017 ms 202.182.124.118
3 2026-08-24 01:12 639231305014280808
6 ms 202.182.124.118
2 2026-08-24 00:20 639231273779380675
23 ms 202.182.124.118
1 2026-08-24 00:04 639231264180839154
25 ms 202.182.124.118