DNS response history for ns2.sharkschoice.com.tw

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

36

Historical checks stored for this nameserver on selected date

Average Latency

430 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.207.150.170

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.sharkschoice.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
36 2026-08-25 12:41 639232576780683689
358 ms 104.207.150.170
35 2026-08-25 12:23 639232566381512620
339 ms 104.207.150.170
34 2026-08-25 12:06 639232556111768563
353 ms 104.207.150.170
33 2026-08-25 11:49 639232545839529039
1305 ms 104.207.150.170
32 2026-08-25 11:32 639232535349285207
548 ms 104.207.150.170
31 2026-08-25 11:14 639232524938080723
554 ms 104.207.150.170
30 2026-08-25 10:21 639232492740373468
166 ms 104.207.150.170
29 2026-08-25 10:03 639232482235303141
167 ms 104.207.150.170
28 2026-08-25 09:46 639232471861770303
190 ms 104.207.150.170
27 2026-08-25 09:29 639232461630217327
329 ms 104.207.150.170
26 2026-08-25 09:12 639232451282965990
189 ms 104.207.150.170
25 2026-08-25 08:54 639232440814614938
362 ms 104.207.150.170
24 2026-08-25 08:37 639232430410720425
197 ms 104.207.150.170
23 2026-08-25 08:20 639232420003096185
2199 ms 104.207.150.170
22 2026-08-25 08:02 639232409467287444
344 ms 104.207.150.170
21 2026-08-25 07:45 639232399077195997
557 ms 104.207.150.170
20 2026-08-25 07:27 639232388731528337
163 ms 104.207.150.170
19 2026-08-25 07:10 639232378288598612
387 ms 104.207.150.170
18 2026-08-25 06:16 639232346196373643
447 ms 104.207.150.170
17 2026-08-25 05:59 639232336112370741
464 ms 104.207.150.170
16 2026-08-25 05:43 639232326146508970
174 ms 104.207.150.170
15 2026-08-25 05:26 639232316189381720
344 ms 104.207.150.170
14 2026-08-25 05:10 639232306217998913
190 ms 104.207.150.170
13 2026-08-25 04:53 639232296255744174
356 ms 104.207.150.170
12 2026-08-25 04:36 639232286095760789
334 ms 104.207.150.170
11 2026-08-25 04:19 639232276086186273
342 ms 104.207.150.170
10 2026-08-25 04:03 639232265900986425
735 ms 104.207.150.170
9 2026-08-25 03:46 639232255723518075
464 ms 104.207.150.170
8 2026-08-25 03:29 639232245484452890
360 ms 104.207.150.170
7 2026-08-25 03:11 639232235157175331
504 ms 104.207.150.170
6 2026-08-25 02:18 639232203197189095
338 ms 104.207.150.170
5 2026-08-25 02:01 639232192844564298
349 ms 104.207.150.170
4 2026-08-25 01:44 639232182496008942
472 ms 104.207.150.170
3 2026-08-25 01:26 639232172197053132
174 ms 104.207.150.170
2 2026-08-25 00:33 639232140250307418
387 ms 104.207.150.170
1 2026-08-25 00:16 639232129927860324
323 ms 104.207.150.170