DNS response history for ns10.travelsky.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

453 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

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

31

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

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
31 2026-08-25 10:22 639232492740373468
1737 ms 122.119.14.233
30 2026-08-25 10:05 639232482235303141
253 ms 122.119.14.233
29 2026-08-25 09:47 639232471861770303
5 ms 122.119.14.233
28 2026-08-25 09:30 639232461630217327
490 ms 122.119.14.233
27 2026-08-25 09:13 639232451282965990
1252 ms 122.119.14.233
26 2026-08-25 08:56 639232440814614938
260 ms 122.119.14.233
25 2026-08-25 08:38 639232430410720425
595 ms 122.119.14.233
24 2026-08-25 08:21 639232420003096185
2510 ms 122.119.14.233
23 2026-08-25 08:03 639232409467287444
668 ms 122.119.14.233
22 2026-08-25 07:46 639232399077195997
240 ms 122.119.14.233
21 2026-08-25 07:29 639232388731528337
159 ms 122.119.14.233
20 2026-08-25 07:11 639232378288598612
239 ms 122.119.14.233
19 2026-08-25 06:17 639232346196373643
11 ms 122.119.14.233
18 2026-08-25 06:01 639232336112370741
780 ms 122.119.14.233
17 2026-08-25 05:44 639232326146508970
1147 ms 122.119.14.233
16 2026-08-25 05:27 639232316189381720
514 ms 122.119.14.233
15 2026-08-25 05:11 639232306217998913
2 ms 122.119.14.233
14 2026-08-25 04:54 639232296255744174
2 ms 122.119.14.233
13 2026-08-25 04:37 639232286095760789
3 ms 122.119.14.233
12 2026-08-25 04:20 639232276086186273
159 ms 122.119.14.233
11 2026-08-25 04:04 639232265900986425
609 ms 122.119.14.233
10 2026-08-25 03:47 639232255723518075
582 ms 122.119.14.233
9 2026-08-25 03:30 639232245484452890
476 ms 122.119.14.233
8 2026-08-25 03:13 639232235157175331
157 ms 122.119.14.233
7 2026-08-25 02:19 639232203197189095
155 ms 122.119.14.233
6 2026-08-25 02:02 639232192844564298
231 ms 122.119.14.233
5 2026-08-25 01:45 639232182496008942
469 ms 122.119.14.233
4 2026-08-25 01:28 639232172197053132
159 ms 122.119.14.233
3 2026-08-25 00:34 639232140250307418
3 ms 122.119.14.233
2 2026-08-25 00:17 639232129927860324
164 ms 122.119.14.233
1 2026-08-25 00:00 639232119551972438
3 ms 122.119.14.233