DNS response history for ns3.166.com

ns3.166.com 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-30. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 330 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 ns3.166.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

330 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 09:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

182.92.22.240

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns3.166.com

Showing DNS history for 2026-08-30 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
30 2026-08-30 09:28 639236785770651804
44 ms 182.92.22.240
29 2026-08-30 09:12 639236775820686373
13 ms 182.92.22.240
28 2026-08-30 08:55 639236765768339082
2310 ms 182.92.22.240
27 2026-08-30 08:38 639236755602384085
19 ms 182.92.22.240
26 2026-08-30 08:21 639236745600094925
2043 ms 182.92.22.240
25 2026-08-30 08:04 639236735311262753
46 ms 182.92.22.240
24 2026-08-30 07:47 639236724996745235
273 ms 182.92.22.240
23 2026-08-30 07:30 639236714839899761
2026 ms 182.92.22.240
22 2026-08-30 07:13 639236704748431488
34 ms 182.92.22.240
21 2026-08-30 06:56 639236694430128550
29 ms 182.92.22.240
20 2026-08-30 06:39 639236684143292417
69 ms 182.92.22.240
19 2026-08-30 06:22 639236673972499943
39 ms 182.92.22.240
18 2026-08-30 05:29 639236642126522802
58 ms 182.92.22.240
17 2026-08-30 05:12 639236632183518198
33 ms 182.92.22.240
16 2026-08-30 04:56 639236622289312589
58 ms 182.92.22.240
15 2026-08-30 04:39 639236612490676525
47 ms 182.92.22.240
14 2026-08-30 04:23 639236602582494852
59 ms 182.92.22.240
13 2026-08-30 04:06 639236592511706469
61 ms 182.92.22.240
12 2026-08-30 03:49 639236582441006869
14 ms 182.92.22.240
11 2026-08-30 03:33 639236572478785089
23 ms 182.92.22.240
10 2026-08-30 03:16 639236562556749999
35 ms 182.92.22.240
9 2026-08-30 02:59 639236552353482281
47 ms 182.92.22.240
8 2026-08-30 02:42 639236542188881607
49 ms 182.92.22.240
7 2026-08-30 02:25 639236531885440105
17 ms 182.92.22.240
6 2026-08-30 01:32 639236499922985383
275 ms 182.92.22.240
5 2026-08-30 01:15 639236489713594431
39 ms 182.92.22.240
4 2026-08-30 00:58 639236479750443901
14 ms 182.92.22.240
3 2026-08-30 00:41 639236469719936375
59 ms 182.92.22.240
2 2026-08-30 00:25 639236459579244885
2019 ms 182.92.22.240
1 2026-08-30 00:08 639236449582837549
57 ms 182.92.22.240