DNS response history for ns1.trackmy.games

ns1.trackmy.games 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 30 DNS check records, 30 successful responses, 0 failed responses, and 204 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 ns1.trackmy.games.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

204 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

170.205.38.127

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns1.trackmy.games

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
30 2026-08-24 12:24 639231703815441688
18 ms 170.205.38.127
29 2026-08-24 12:07 639231693747052549
5 ms 170.205.38.127
28 2026-08-24 11:50 639231683712487276
170 ms 170.205.38.127
27 2026-08-24 11:33 639231673513573868
315 ms 170.205.38.127
26 2026-08-24 10:40 639231641791249939
319 ms 170.205.38.127
25 2026-08-24 10:24 639231631866211033
21 ms 170.205.38.127
24 2026-08-24 10:07 639231621644955316
4 ms 170.205.38.127
23 2026-08-24 09:50 639231611478799259
12 ms 170.205.38.127
22 2026-08-24 08:58 639231579923718211
8 ms 170.205.38.127
21 2026-08-24 08:41 639231569810702936
167 ms 170.205.38.127
20 2026-08-24 08:24 639231559762411619
328 ms 170.205.38.127
19 2026-08-24 08:07 639231549663595407
325 ms 170.205.38.127
18 2026-08-24 07:14 639231518076817246
160 ms 170.205.38.127
17 2026-08-24 06:58 639231508078650885
162 ms 170.205.38.127
16 2026-08-24 06:41 639231498210697093
322 ms 170.205.38.127
15 2026-08-24 06:25 639231488109699360
436 ms 170.205.38.127
14 2026-08-24 05:32 639231456772510692
3 ms 170.205.38.127
13 2026-08-24 05:16 639231447084631185
3 ms 170.205.38.127
12 2026-08-24 04:59 639231437208519473
332 ms 170.205.38.127
11 2026-08-24 04:43 639231427209627490
3 ms 170.205.38.127
10 2026-08-24 03:50 639231395791246644
160 ms 170.205.38.127
9 2026-08-24 03:34 639231386075551458
327 ms 170.205.38.127
8 2026-08-24 03:18 639231376208713791
31 ms 170.205.38.127
7 2026-08-24 03:01 639231366170589276
149 ms 170.205.38.127
6 2026-08-24 02:09 639231334732159368
5 ms 170.205.38.127
5 2026-08-24 01:52 639231325035670078
38 ms 170.205.38.127
4 2026-08-24 01:36 639231315132253837
8 ms 170.205.38.127
3 2026-08-24 01:19 639231305014280808
4 ms 170.205.38.127
2 2026-08-24 00:27 639231273779380675
3 ms 170.205.38.127
1 2026-08-24 00:11 639231264180839154
2276 ms 170.205.38.127