DNS response history for ns2.thaidatadive.com

ns2.thaidatadive.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.thaidatadive.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:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

3.3.3.101

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.thaidatadive.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:38 639233403515141099
475 ms 3.3.3.101
34 2026-08-26 10:43 639233370841350248
494 ms 3.3.3.101
33 2026-08-26 10:26 639233360361507238
492 ms 3.3.3.101
32 2026-08-26 10:09 639233350067824371
328 ms 3.3.3.101
31 2026-08-26 09:51 639233339545274518
493 ms 3.3.3.101
30 2026-08-26 09:34 639233329214918079
328 ms 3.3.3.101
29 2026-08-26 09:17 639233318749762337
493 ms 3.3.3.101
28 2026-08-26 08:59 639233308387917838
491 ms 3.3.3.101
27 2026-08-26 08:42 639233297961740122
498 ms 3.3.3.101
26 2026-08-26 08:24 639233287487159094
345 ms 3.3.3.101
25 2026-08-26 08:07 639233276995531707
513 ms 3.3.3.101
24 2026-08-26 07:50 639233266521568229
345 ms 3.3.3.101
23 2026-08-26 07:32 639233256081047431
350 ms 3.3.3.101
22 2026-08-26 06:38 639233223620132921
490 ms 3.3.3.101
21 2026-08-26 06:21 639233213287814244
2013 ms 3.3.3.101
20 2026-08-26 06:04 639233202925983161
385 ms 3.3.3.101
19 2026-08-26 05:46 639233192644780696
490 ms 3.3.3.101
18 2026-08-26 05:29 639233182401183833
491 ms 3.3.3.101
17 2026-08-26 05:12 639233172074181051
492 ms 3.3.3.101
16 2026-08-26 04:55 639233161808421455
333 ms 3.3.3.101
15 2026-08-26 04:38 639233151357344052
489 ms 3.3.3.101
14 2026-08-26 04:20 639233141034116946
493 ms 3.3.3.101
13 2026-08-26 04:03 639233130828334142
2012 ms 3.3.3.101
12 2026-08-26 03:46 639233120373450007
501 ms 3.3.3.101
11 2026-08-26 03:29 639233110066216193
490 ms 3.3.3.101
10 2026-08-26 02:35 639233078065410564
499 ms 3.3.3.101
9 2026-08-26 02:18 639233067787457832
340 ms 3.3.3.101
8 2026-08-26 02:01 639233057501801162
489 ms 3.3.3.101
7 2026-08-26 01:44 639233047089431703
494 ms 3.3.3.101
6 2026-08-26 01:27 639233036754790688
518 ms 3.3.3.101
5 2026-08-26 01:09 639233026412602472
505 ms 3.3.3.101
4 2026-08-26 00:52 639233016064066127
504 ms 3.3.3.101
3 2026-08-26 00:35 639233005922655772
495 ms 3.3.3.101
2 2026-08-26 00:18 639232995672256907
522 ms 3.3.3.101
1 2026-08-26 00:01 639232985300872416
502 ms 3.3.3.101