DNS response history for ns2.thai-bcc.com

ns2.thai-bcc.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 429 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.thai-bcc.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

429 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

160.16.236.233

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.thai-bcc.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
537 ms 160.16.236.233
34 2026-08-26 10:44 639233370841350248
551 ms 160.16.236.233
33 2026-08-26 10:27 639233360361507238
542 ms 160.16.236.233
32 2026-08-26 10:10 639233350067824371
574 ms 160.16.236.233
31 2026-08-26 09:53 639233339545274518
525 ms 160.16.236.233
30 2026-08-26 09:35 639233329214918079
540 ms 160.16.236.233
29 2026-08-26 09:18 639233318749762337
274 ms 160.16.236.233
28 2026-08-26 09:00 639233308387917838
541 ms 160.16.236.233
27 2026-08-26 08:43 639233297961740122
550 ms 160.16.236.233
26 2026-08-26 08:26 639233287487159094
544 ms 160.16.236.233
25 2026-08-26 08:08 639233276995531707
559 ms 160.16.236.233
24 2026-08-26 07:51 639233266521568229
657 ms 160.16.236.233
23 2026-08-26 07:33 639233256081047431
554 ms 160.16.236.233
22 2026-08-26 06:39 639233223620132921
566 ms 160.16.236.233
21 2026-08-26 06:22 639233213287814244
571 ms 160.16.236.233
20 2026-08-26 06:05 639233202925983161
567 ms 160.16.236.233
19 2026-08-26 05:47 639233192644780696
565 ms 160.16.236.233
18 2026-08-26 05:30 639233182401183833
4 ms 160.16.236.233
17 2026-08-26 05:13 639233172074181051
553 ms 160.16.236.233
16 2026-08-26 04:56 639233161808421455
6 ms 160.16.236.233
15 2026-08-26 04:39 639233151357344052
547 ms 160.16.236.233
14 2026-08-26 04:21 639233141034116946
3 ms 160.16.236.233
13 2026-08-26 04:04 639233130828334142
540 ms 160.16.236.233
12 2026-08-26 03:47 639233120373450007
552 ms 160.16.236.233
11 2026-08-26 03:30 639233110066216193
4 ms 160.16.236.233
10 2026-08-26 02:37 639233078065410564
547 ms 160.16.236.233
9 2026-08-26 02:19 639233067787457832
533 ms 160.16.236.233
8 2026-08-26 02:02 639233057501801162
3 ms 160.16.236.233
7 2026-08-26 01:45 639233047089431703
305 ms 160.16.236.233
6 2026-08-26 01:28 639233036754790688
555 ms 160.16.236.233
5 2026-08-26 01:11 639233026412602472
554 ms 160.16.236.233
4 2026-08-26 00:53 639233016064066127
2 ms 160.16.236.233
3 2026-08-26 00:36 639233005922655772
537 ms 160.16.236.233
2 2026-08-26 00:19 639232995672256907
5 ms 160.16.236.233
1 2026-08-26 00:02 639232985300872416
539 ms 160.16.236.233