DNS response history for ns1.twdaily.com

ns1.twdaily.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 400 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 ns1.twdaily.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

400 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.72.215.58

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns1.twdaily.com

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
28 2026-08-25 09:30 639232461630217327
596 ms 211.72.215.58
27 2026-08-25 09:13 639232451282965990
616 ms 211.72.215.58
26 2026-08-25 08:55 639232440814614938
613 ms 211.72.215.58
25 2026-08-25 08:38 639232430410720425
314 ms 211.72.215.58
24 2026-08-25 08:20 639232420003096185
611 ms 211.72.215.58
23 2026-08-25 08:03 639232409467287444
295 ms 211.72.215.58
22 2026-08-25 07:46 639232399077195997
617 ms 211.72.215.58
21 2026-08-25 07:28 639232388731528337
305 ms 211.72.215.58
20 2026-08-25 07:11 639232378288598612
295 ms 211.72.215.58
19 2026-08-25 06:17 639232346196373643
304 ms 211.72.215.58
18 2026-08-25 06:00 639232336112370741
296 ms 211.72.215.58
17 2026-08-25 05:44 639232326146508970
595 ms 211.72.215.58
16 2026-08-25 05:27 639232316189381720
2 ms 211.72.215.58
15 2026-08-25 05:11 639232306217998913
8 ms 211.72.215.58
14 2026-08-25 04:54 639232296255744174
2 ms 211.72.215.58
13 2026-08-25 04:37 639232286095760789
607 ms 211.72.215.58
12 2026-08-25 04:20 639232276086186273
603 ms 211.72.215.58
11 2026-08-25 04:03 639232265900986425
4 ms 211.72.215.58
10 2026-08-25 03:47 639232255723518075
595 ms 211.72.215.58
9 2026-08-25 03:29 639232245484452890
6 ms 211.72.215.58
8 2026-08-25 03:12 639232235157175331
594 ms 211.72.215.58
7 2026-08-25 02:19 639232203197189095
612 ms 211.72.215.58
6 2026-08-25 02:02 639232192844564298
287 ms 211.72.215.58
5 2026-08-25 01:45 639232182496008942
297 ms 211.72.215.58
4 2026-08-25 01:27 639232172197053132
294 ms 211.72.215.58
3 2026-08-25 00:34 639232140250307418
605 ms 211.72.215.58
2 2026-08-25 00:17 639232129927860324
605 ms 211.72.215.58
1 2026-08-25 00:00 639232119551972438
609 ms 211.72.215.58