DNS response history for ns10.travelsky.com.cn

ns10.travelsky.com.cn 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-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 520 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 ns10.travelsky.com.cn.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

520 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

122.119.14.233

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns10.travelsky.com.cn

Showing DNS history for 2026-08-25 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
33 2026-08-25 11:50 639232545839529039
321 ms 122.119.14.233
32 2026-08-25 11:33 639232535349285207
1090 ms 122.119.14.233
31 2026-08-25 11:15 639232524938080723
723 ms 122.119.14.233
30 2026-08-25 10:21 639232492740373468
1545 ms 122.119.14.233
29 2026-08-25 10:04 639232482235303141
493 ms 122.119.14.233
28 2026-08-25 09:47 639232471861770303
418 ms 122.119.14.233
27 2026-08-25 09:30 639232461630217327
364 ms 122.119.14.233
26 2026-08-25 09:12 639232451282965990
511 ms 122.119.14.233
25 2026-08-25 08:55 639232440814614938
516 ms 122.119.14.233
24 2026-08-25 08:38 639232430410720425
160 ms 122.119.14.233
23 2026-08-25 08:20 639232420003096185
368 ms 122.119.14.233
22 2026-08-25 08:03 639232409467287444
525 ms 122.119.14.233
21 2026-08-25 07:45 639232399077195997
320 ms 122.119.14.233
20 2026-08-25 07:28 639232388731528337
484 ms 122.119.14.233
19 2026-08-25 07:11 639232378288598612
268 ms 122.119.14.233
18 2026-08-25 06:17 639232346196373643
248 ms 122.119.14.233
17 2026-08-25 06:00 639232336112370741
505 ms 122.119.14.233
16 2026-08-25 05:43 639232326146508970
480 ms 122.119.14.233
15 2026-08-25 05:27 639232316189381720
264 ms 122.119.14.233
14 2026-08-25 05:10 639232306217998913
475 ms 122.119.14.233
13 2026-08-25 04:54 639232296255744174
479 ms 122.119.14.233
12 2026-08-25 04:37 639232286095760789
1746 ms 122.119.14.233
11 2026-08-25 04:20 639232276086186273
379 ms 122.119.14.233
10 2026-08-25 04:03 639232265900986425
354 ms 122.119.14.233
9 2026-08-25 03:46 639232255723518075
281 ms 122.119.14.233
8 2026-08-25 03:29 639232245484452890
505 ms 122.119.14.233
7 2026-08-25 03:12 639232235157175331
530 ms 122.119.14.233
6 2026-08-25 02:19 639232203197189095
344 ms 122.119.14.233
5 2026-08-25 02:02 639232192844564298
483 ms 122.119.14.233
4 2026-08-25 01:44 639232182496008942
789 ms 122.119.14.233
3 2026-08-25 01:27 639232172197053132
503 ms 122.119.14.233
2 2026-08-25 00:34 639232140250307418
348 ms 122.119.14.233
1 2026-08-25 00:17 639232129927860324
356 ms 122.119.14.233