DNS response history for ns2.tp.edu.tw

ns2.tp.edu.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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 559 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.tp.edu.tw.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

559 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

163.21.249.158

Most recently resolved hosting IP on selected date

Successful Responses

36

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.tp.edu.tw

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
36 2026-08-26 11:58 639233414056832719
1318 ms 163.21.249.158
35 2026-08-26 11:41 639233403515141099
314 ms 163.21.249.158
34 2026-08-26 10:46 639233370841350248
894 ms 163.21.249.158
33 2026-08-26 10:29 639233360361507238
1236 ms 163.21.249.158
32 2026-08-26 10:11 639233350067824371
315 ms 163.21.249.158
31 2026-08-26 09:54 639233339545274518
274 ms 163.21.249.158
30 2026-08-26 09:36 639233329214918079
311 ms 163.21.249.158
29 2026-08-26 09:19 639233318749762337
351 ms 163.21.249.158
28 2026-08-26 09:02 639233308387917838
320 ms 163.21.249.158
27 2026-08-26 08:45 639233297961740122
1270 ms 163.21.249.158
26 2026-08-26 08:27 639233287487159094
2444 ms 163.21.249.158
25 2026-08-26 08:10 639233276995531707
304 ms 163.21.249.158
24 2026-08-26 07:52 639233266521568229
274 ms 163.21.249.158
23 2026-08-26 07:35 639233256081047431
806 ms 163.21.249.158
22 2026-08-26 06:41 639233223620132921
314 ms 163.21.249.158
21 2026-08-26 06:23 639233213287814244
3 ms 163.21.249.158
20 2026-08-26 06:06 639233202925983161
3 ms 163.21.249.158
19 2026-08-26 05:49 639233192644780696
1338 ms 163.21.249.158
18 2026-08-26 05:32 639233182401183833
3 ms 163.21.249.158
17 2026-08-26 05:15 639233172074181051
274 ms 163.21.249.158
16 2026-08-26 04:57 639233161808421455
4 ms 163.21.249.158
15 2026-08-26 04:40 639233151357344052
845 ms 163.21.249.158
14 2026-08-26 04:23 639233141034116946
304 ms 163.21.249.158
13 2026-08-26 04:06 639233130828334142
1691 ms 163.21.249.158
12 2026-08-26 03:49 639233120373450007
3 ms 163.21.249.158
11 2026-08-26 03:31 639233110066216193
807 ms 163.21.249.158
10 2026-08-26 02:38 639233078065410564
988 ms 163.21.249.158
9 2026-08-26 02:21 639233067787457832
2 ms 163.21.249.158
8 2026-08-26 02:04 639233057501801162
4 ms 163.21.249.158
7 2026-08-26 01:47 639233047089431703
1892 ms 163.21.249.158
6 2026-08-26 01:29 639233036754790688
8 ms 163.21.249.158
5 2026-08-26 01:12 639233026412602472
3 ms 163.21.249.158
4 2026-08-26 00:55 639233016064066127
846 ms 163.21.249.158
3 2026-08-26 00:37 639233005922655772
366 ms 163.21.249.158
2 2026-08-26 00:20 639232995672256907
3 ms 163.21.249.158
1 2026-08-26 00:03 639232985300872416
3 ms 163.21.249.158