DNS response history for ns2.thailuxe.com

ns2.thailuxe.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 548 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 ns2.thailuxe.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

548 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

203.78.103.118

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 ns2.thailuxe.com

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
350 ms 203.78.103.118
34 2026-08-26 10:44 639233370841350248
735 ms 203.78.103.118
33 2026-08-26 10:27 639233360361507238
364 ms 203.78.103.118
32 2026-08-26 10:10 639233350067824371
2696 ms 203.78.103.118
31 2026-08-26 09:52 639233339545274518
373 ms 203.78.103.118
30 2026-08-26 09:35 639233329214918079
347 ms 203.78.103.118
29 2026-08-26 09:18 639233318749762337
2701 ms 203.78.103.118
28 2026-08-26 09:00 639233308387917838
378 ms 203.78.103.118
27 2026-08-26 08:43 639233297961740122
344 ms 203.78.103.118
26 2026-08-26 08:25 639233287487159094
347 ms 203.78.103.118
25 2026-08-26 08:08 639233276995531707
346 ms 203.78.103.118
24 2026-08-26 07:51 639233266521568229
346 ms 203.78.103.118
23 2026-08-26 07:33 639233256081047431
741 ms 203.78.103.118
22 2026-08-26 06:39 639233223620132921
694 ms 203.78.103.118
21 2026-08-26 06:22 639233213287814244
378 ms 203.78.103.118
20 2026-08-26 06:04 639233202925983161
367 ms 203.78.103.118
19 2026-08-26 05:47 639233192644780696
396 ms 203.78.103.118
18 2026-08-26 05:30 639233182401183833
381 ms 203.78.103.118
17 2026-08-26 05:13 639233172074181051
364 ms 203.78.103.118
16 2026-08-26 04:56 639233161808421455
435 ms 203.78.103.118
15 2026-08-26 04:39 639233151357344052
361 ms 203.78.103.118
14 2026-08-26 04:21 639233141034116946
349 ms 203.78.103.118
13 2026-08-26 04:04 639233130828334142
352 ms 203.78.103.118
12 2026-08-26 03:47 639233120373450007
380 ms 203.78.103.118
11 2026-08-26 03:30 639233110066216193
354 ms 203.78.103.118
10 2026-08-26 02:36 639233078065410564
738 ms 203.78.103.118
9 2026-08-26 02:19 639233067787457832
364 ms 203.78.103.118
8 2026-08-26 02:02 639233057501801162
238 ms 203.78.103.118
7 2026-08-26 01:45 639233047089431703
384 ms 203.78.103.118
6 2026-08-26 01:28 639233036754790688
768 ms 203.78.103.118
5 2026-08-26 01:10 639233026412602472
349 ms 203.78.103.118
4 2026-08-26 00:53 639233016064066127
364 ms 203.78.103.118
3 2026-08-26 00:36 639233005922655772
361 ms 203.78.103.118
2 2026-08-26 00:19 639232995672256907
365 ms 203.78.103.118
1 2026-08-26 00:02 639232985300872416
363 ms 203.78.103.118