DNS response history for ns2.quailclan.net

ns2.quailclan.net 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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 352 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.quailclan.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

352 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.181.167.138

Most recently resolved hosting IP on selected date

Successful Responses

35

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.quailclan.net

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:16 639234253963286387
275 ms 104.181.167.138
34 2026-08-27 10:59 639234243654907465
274 ms 104.181.167.138
33 2026-08-27 10:42 639234233269654413
688 ms 104.181.167.138
32 2026-08-27 10:24 639234222943951923
274 ms 104.181.167.138
31 2026-08-27 10:07 639234212558002823
279 ms 104.181.167.138
30 2026-08-27 09:50 639234202117531850
286 ms 104.181.167.138
29 2026-08-27 09:32 639234191649612722
290 ms 104.181.167.138
28 2026-08-27 09:15 639234181105879568
272 ms 104.181.167.138
27 2026-08-27 08:57 639234170713214496
275 ms 104.181.167.138
26 2026-08-27 08:40 639234160341037652
281 ms 104.181.167.138
25 2026-08-27 08:23 639234149799404224
281 ms 104.181.167.138
24 2026-08-27 08:05 639234139553286469
285 ms 104.181.167.138
23 2026-08-27 07:11 639234107183588293
284 ms 104.181.167.138
22 2026-08-27 06:54 639234096905435724
268 ms 104.181.167.138
21 2026-08-27 06:37 639234086579410775
276 ms 104.181.167.138
20 2026-08-27 06:20 639234076291157956
273 ms 104.181.167.138
19 2026-08-27 06:03 639234065981939454
9 ms 104.181.167.138
18 2026-08-27 05:46 639234055548642997
278 ms 104.181.167.138
17 2026-08-27 05:28 639234045267979603
262 ms 104.181.167.138
16 2026-08-27 05:11 639234034999717463
8 ms 104.181.167.138
15 2026-08-27 04:54 639234024739225358
854 ms 104.181.167.138
14 2026-08-27 04:37 639234014311170162
277 ms 104.181.167.138
13 2026-08-27 04:19 639234003806017640
276 ms 104.181.167.138
12 2026-08-27 04:02 639233993356203030
862 ms 104.181.167.138
11 2026-08-27 03:08 639233961301716608
266 ms 104.181.167.138
10 2026-08-27 02:51 639233950834200647
9 ms 104.181.167.138
9 2026-08-27 02:34 639233940431849026
266 ms 104.181.167.138
8 2026-08-27 02:16 639233930110596398
268 ms 104.181.167.138
7 2026-08-27 01:59 639233919705434540
857 ms 104.181.167.138
6 2026-08-27 01:42 639233909452807845
267 ms 104.181.167.138
5 2026-08-27 01:25 639233899096420820
262 ms 104.181.167.138
4 2026-08-27 01:07 639233888707824939
1639 ms 104.181.167.138
3 2026-08-27 00:50 639233878461203802
265 ms 104.181.167.138
2 2026-08-27 00:33 639233868060868209
267 ms 104.181.167.138
1 2026-08-27 00:16 639233857450922991
257 ms 104.181.167.138