DNS response history for ns2.trinity.co.th

ns2.trinity.co.th 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 285 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.trinity.co.th.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

285 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.170.190.164

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 ns2.trinity.co.th

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 11:14 639232524938080723
387 ms 203.170.190.164
30 2026-08-25 10:20 639232492740373468
188 ms 203.170.190.164
29 2026-08-25 10:03 639232482235303141
191 ms 203.170.190.164
28 2026-08-25 09:45 639232471861770303
5 ms 203.170.190.164
27 2026-08-25 09:28 639232461630217327
17 ms 203.170.190.164
26 2026-08-25 09:11 639232451282965990
373 ms 203.170.190.164
25 2026-08-25 08:54 639232440814614938
381 ms 203.170.190.164
24 2026-08-25 08:36 639232430410720425
14 ms 203.170.190.164
23 2026-08-25 08:19 639232420003096185
381 ms 203.170.190.164
22 2026-08-25 08:02 639232409467287444
371 ms 203.170.190.164
21 2026-08-25 07:44 639232399077195997
410 ms 203.170.190.164
20 2026-08-25 07:27 639232388731528337
367 ms 203.170.190.164
19 2026-08-25 07:09 639232378288598612
371 ms 203.170.190.164
18 2026-08-25 06:16 639232346196373643
366 ms 203.170.190.164
17 2026-08-25 05:59 639232336112370741
231 ms 203.170.190.164
16 2026-08-25 05:42 639232326146508970
396 ms 203.170.190.164
15 2026-08-25 05:26 639232316189381720
397 ms 203.170.190.164
14 2026-08-25 05:09 639232306217998913
26 ms 203.170.190.164
13 2026-08-25 04:52 639232296255744174
544 ms 203.170.190.164
12 2026-08-25 04:36 639232286095760789
188 ms 203.170.190.164
11 2026-08-25 04:19 639232276086186273
226 ms 203.170.190.164
10 2026-08-25 04:02 639232265900986425
191 ms 203.170.190.164
9 2026-08-25 03:45 639232255723518075
380 ms 203.170.190.164
8 2026-08-25 03:28 639232245484452890
543 ms 203.170.190.164
7 2026-08-25 03:11 639232235157175331
370 ms 203.170.190.164
6 2026-08-25 02:18 639232203197189095
378 ms 203.170.190.164
5 2026-08-25 02:01 639232192844564298
9 ms 203.170.190.164
4 2026-08-25 01:43 639232182496008942
189 ms 203.170.190.164
3 2026-08-25 01:26 639232172197053132
189 ms 203.170.190.164
2 2026-08-25 00:33 639232140250307418
197 ms 203.170.190.164
1 2026-08-25 00:16 639232129927860324
558 ms 203.170.190.164