DNS response history for dns2.ls3c.com.tw

dns2.ls3c.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 485 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 dns2.ls3c.com.tw.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

485 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.222.59.186

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 dns2.ls3c.com.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:45 639233370841350248
286 ms 61.222.59.186
33 2026-08-26 10:28 639233360361507238
284 ms 61.222.59.186
32 2026-08-26 10:11 639233350067824371
575 ms 61.222.59.186
31 2026-08-26 09:53 639233339545274518
283 ms 61.222.59.186
30 2026-08-26 09:36 639233329214918079
300 ms 61.222.59.186
29 2026-08-26 09:19 639233318749762337
601 ms 61.222.59.186
28 2026-08-26 09:01 639233308387917838
579 ms 61.222.59.186
27 2026-08-26 08:44 639233297961740122
590 ms 61.222.59.186
26 2026-08-26 08:26 639233287487159094
289 ms 61.222.59.186
25 2026-08-26 08:09 639233276995531707
692 ms 61.222.59.186
24 2026-08-26 07:51 639233266521568229
760 ms 61.222.59.186
23 2026-08-26 07:34 639233256081047431
596 ms 61.222.59.186
22 2026-08-26 06:40 639233223620132921
761 ms 61.222.59.186
21 2026-08-26 06:23 639233213287814244
284 ms 61.222.59.186
20 2026-08-26 06:05 639233202925983161
564 ms 61.222.59.186
19 2026-08-26 05:48 639233192644780696
586 ms 61.222.59.186
18 2026-08-26 05:31 639233182401183833
308 ms 61.222.59.186
17 2026-08-26 05:14 639233172074181051
569 ms 61.222.59.186
16 2026-08-26 04:57 639233161808421455
594 ms 61.222.59.186
15 2026-08-26 04:40 639233151357344052
3 ms 61.222.59.186
14 2026-08-26 04:22 639233141034116946
565 ms 61.222.59.186
13 2026-08-26 04:05 639233130828334142
287 ms 61.222.59.186
12 2026-08-26 03:48 639233120373450007
583 ms 61.222.59.186
11 2026-08-26 03:30 639233110066216193
581 ms 61.222.59.186
10 2026-08-26 02:37 639233078065410564
574 ms 61.222.59.186
9 2026-08-26 02:20 639233067787457832
278 ms 61.222.59.186
8 2026-08-26 02:03 639233057501801162
586 ms 61.222.59.186
7 2026-08-26 01:46 639233047089431703
702 ms 61.222.59.186
6 2026-08-26 01:28 639233036754790688
575 ms 61.222.59.186
5 2026-08-26 01:11 639233026412602472
287 ms 61.222.59.186
4 2026-08-26 00:54 639233016064066127
282 ms 61.222.59.186
3 2026-08-26 00:37 639233005922655772
597 ms 61.222.59.186
2 2026-08-26 00:20 639232995672256907
790 ms 61.222.59.186
1 2026-08-26 00:03 639232985300872416
286 ms 61.222.59.186