DNS response history for gtm2.skcdn.net

gtm2.skcdn.net 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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 440 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 gtm2.skcdn.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

440 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

58.225.225.107

Most recently resolved hosting IP on selected date

Successful Responses

35

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 gtm2.skcdn.net

Showing DNS history for 2026-08-26 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
35 2026-08-26 11:39 639233403515141099
311 ms 58.225.225.107
34 2026-08-26 10:44 639233370841350248
2278 ms 58.225.225.107
33 2026-08-26 10:27 639233360361507238
303 ms 58.225.225.107
32 2026-08-26 10:09 639233350067824371
307 ms 58.225.225.107
31 2026-08-26 09:52 639233339545274518
597 ms 58.225.225.107
30 2026-08-26 09:35 639233329214918079
306 ms 58.225.225.107
29 2026-08-26 09:18 639233318749762337
609 ms 58.225.225.107
28 2026-08-26 09:00 639233308387917838
292 ms 58.225.225.107
27 2026-08-26 08:43 639233297961740122
285 ms 58.225.225.107
26 2026-08-26 08:25 639233287487159094
298 ms 58.225.225.107
25 2026-08-26 08:08 639233276995531707
310 ms 58.225.225.107
24 2026-08-26 07:50 639233266521568229
300 ms 58.225.225.107
23 2026-08-26 07:33 639233256081047431
293 ms 58.225.225.107
22 2026-08-26 06:39 639233223620132921
291 ms 58.225.225.107
21 2026-08-26 06:22 639233213287814244
286 ms 58.225.225.107
20 2026-08-26 06:04 639233202925983161
308 ms 58.225.225.107
19 2026-08-26 05:47 639233192644780696
599 ms 58.225.225.107
18 2026-08-26 05:30 639233182401183833
286 ms 58.225.225.107
17 2026-08-26 05:13 639233172074181051
592 ms 58.225.225.107
16 2026-08-26 04:56 639233161808421455
288 ms 58.225.225.107
15 2026-08-26 04:39 639233151357344052
609 ms 58.225.225.107
14 2026-08-26 04:21 639233141034116946
303 ms 58.225.225.107
13 2026-08-26 04:04 639233130828334142
598 ms 58.225.225.107
12 2026-08-26 03:47 639233120373450007
591 ms 58.225.225.107
11 2026-08-26 03:29 639233110066216193
594 ms 58.225.225.107
10 2026-08-26 02:36 639233078065410564
305 ms 58.225.225.107
9 2026-08-26 02:19 639233067787457832
577 ms 58.225.225.107
8 2026-08-26 02:02 639233057501801162
9 ms 58.225.225.107
7 2026-08-26 01:45 639233047089431703
290 ms 58.225.225.107
6 2026-08-26 01:27 639233036754790688
312 ms 58.225.225.107
5 2026-08-26 01:10 639233026412602472
292 ms 58.225.225.107
4 2026-08-26 00:53 639233016064066127
588 ms 58.225.225.107
3 2026-08-26 00:36 639233005922655772
301 ms 58.225.225.107
2 2026-08-26 00:19 639232995672256907
298 ms 58.225.225.107
1 2026-08-26 00:02 639232985300872416
592 ms 58.225.225.107