DNS response history for ns2.3366.tw

ns2.3366.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 34 DNS check records, 34 successful responses, 0 failed responses, and 3556 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.3366.tw.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

3556 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

125.227.6.187

Most recently resolved hosting IP on selected date

Successful Responses

34

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.3366.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
34 2026-08-26 10:44 639233370841350248
2287 ms 125.227.6.187
33 2026-08-26 10:27 639233360361507238
4548 ms 125.227.6.187
32 2026-08-26 10:10 639233350067824371
2510 ms 125.227.6.187
31 2026-08-26 09:53 639233339545274518
4285 ms 125.227.6.187
30 2026-08-26 09:35 639233329214918079
4285 ms 125.227.6.187
29 2026-08-26 09:18 639233318749762337
2008 ms 125.227.6.187
28 2026-08-26 09:00 639233308387917838
4290 ms 125.227.6.187
27 2026-08-26 08:43 639233297961740122
2275 ms 125.227.6.187
26 2026-08-26 08:26 639233287487159094
2008 ms 125.227.6.187
25 2026-08-26 08:08 639233276995531707
4278 ms 125.227.6.187
24 2026-08-26 07:51 639233266521568229
4008 ms 125.227.6.187
23 2026-08-26 07:33 639233256081047431
2011 ms 125.227.6.187
22 2026-08-26 06:39 639233223620132921
4009 ms 125.227.6.187
21 2026-08-26 06:22 639233213287814244
4287 ms 125.227.6.187
20 2026-08-26 06:05 639233202925983161
4290 ms 125.227.6.187
19 2026-08-26 05:47 639233192644780696
2286 ms 125.227.6.187
18 2026-08-26 05:30 639233182401183833
4010 ms 125.227.6.187
17 2026-08-26 05:13 639233172074181051
2010 ms 125.227.6.187
16 2026-08-26 04:56 639233161808421455
4011 ms 125.227.6.187
15 2026-08-26 04:39 639233151357344052
4287 ms 125.227.6.187
14 2026-08-26 04:21 639233141034116946
4296 ms 125.227.6.187
13 2026-08-26 04:04 639233130828334142
2285 ms 125.227.6.187
12 2026-08-26 03:47 639233120373450007
2010 ms 125.227.6.187
11 2026-08-26 03:30 639233110066216193
4299 ms 125.227.6.187
10 2026-08-26 02:37 639233078065410564
4008 ms 125.227.6.187
9 2026-08-26 02:19 639233067787457832
4295 ms 125.227.6.187
8 2026-08-26 02:02 639233057501801162
4010 ms 125.227.6.187
7 2026-08-26 01:45 639233047089431703
2284 ms 125.227.6.187
6 2026-08-26 01:28 639233036754790688
4286 ms 125.227.6.187
5 2026-08-26 01:11 639233026412602472
4008 ms 125.227.6.187
4 2026-08-26 00:53 639233016064066127
4009 ms 125.227.6.187
3 2026-08-26 00:36 639233005922655772
4292 ms 125.227.6.187
2 2026-08-26 00:19 639232995672256907
4539 ms 125.227.6.187
1 2026-08-26 00:02 639232985300872416
4296 ms 125.227.6.187