DNS response history for ns2.triotek.com.tw

ns2.triotek.com.tw 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 29 DNS check records, 29 successful responses, 0 failed responses, and 606 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.triotek.com.tw.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

606 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

123.252.118.5

Most recently resolved hosting IP on selected date

Successful Responses

29

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.triotek.com.tw

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
29 2026-08-25 10:04 639232482235303141
505 ms 123.252.118.5
28 2026-08-25 09:46 639232471861770303
250 ms 123.252.118.5
27 2026-08-25 09:29 639232461630217327
510 ms 123.252.118.5
26 2026-08-25 09:12 639232451282965990
262 ms 123.252.118.5
25 2026-08-25 08:55 639232440814614938
540 ms 123.252.118.5
24 2026-08-25 08:37 639232430410720425
256 ms 123.252.118.5
23 2026-08-25 08:20 639232420003096185
2808 ms 123.252.118.5
22 2026-08-25 08:02 639232409467287444
506 ms 123.252.118.5
21 2026-08-25 07:45 639232399077195997
545 ms 123.252.118.5
20 2026-08-25 07:28 639232388731528337
492 ms 123.252.118.5
19 2026-08-25 07:10 639232378288598612
251 ms 123.252.118.5
18 2026-08-25 06:16 639232346196373643
490 ms 123.252.118.5
17 2026-08-25 06:00 639232336112370741
623 ms 123.252.118.5
16 2026-08-25 05:43 639232326146508970
2519 ms 123.252.118.5
15 2026-08-25 05:26 639232316189381720
488 ms 123.252.118.5
14 2026-08-25 05:10 639232306217998913
9 ms 123.252.118.5
13 2026-08-25 04:53 639232296255744174
501 ms 123.252.118.5
12 2026-08-25 04:36 639232286095760789
493 ms 123.252.118.5
11 2026-08-25 04:19 639232276086186273
554 ms 123.252.118.5
10 2026-08-25 04:03 639232265900986425
506 ms 123.252.118.5
9 2026-08-25 03:46 639232255723518075
500 ms 123.252.118.5
8 2026-08-25 03:29 639232245484452890
251 ms 123.252.118.5
7 2026-08-25 03:12 639232235157175331
627 ms 123.252.118.5
6 2026-08-25 02:18 639232203197189095
523 ms 123.252.118.5
5 2026-08-25 02:01 639232192844564298
280 ms 123.252.118.5
4 2026-08-25 01:44 639232182496008942
765 ms 123.252.118.5
3 2026-08-25 01:27 639232172197053132
514 ms 123.252.118.5
2 2026-08-25 00:33 639232140250307418
509 ms 123.252.118.5
1 2026-08-25 00:16 639232129927860324
499 ms 123.252.118.5