DNS response history for ns2.long-dragon.com

ns2.long-dragon.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-24. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 356 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.long-dragon.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

356 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 16:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.56.230.150

Most recently resolved hosting IP on selected date

Successful Responses

39

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.long-dragon.com

Showing DNS history for 2026-08-24 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
39 2026-08-24 16:46 639231860258429562
248 ms 96.56.230.150
38 2026-08-24 15:53 639231828211839931
163 ms 96.56.230.150
37 2026-08-24 15:36 639231818080917481
232 ms 96.56.230.150
36 2026-08-24 15:19 639231807961539652
238 ms 96.56.230.150
35 2026-08-24 15:02 639231797631669865
4227 ms 96.56.230.150
34 2026-08-24 14:09 639231765923559455
243 ms 96.56.230.150
33 2026-08-24 13:52 639231755868832964
231 ms 96.56.230.150
32 2026-08-24 13:35 639231745628278877
220 ms 96.56.230.150
31 2026-08-24 13:18 639231735407682062
233 ms 96.56.230.150
30 2026-08-24 12:25 639231703815441688
225 ms 96.56.230.150
29 2026-08-24 12:09 639231693747052549
235 ms 96.56.230.150
28 2026-08-24 11:52 639231683712487276
248 ms 96.56.230.150
27 2026-08-24 11:35 639231673513573868
150 ms 96.56.230.150
26 2026-08-24 10:42 639231641791249939
220 ms 96.56.230.150
25 2026-08-24 10:26 639231631866211033
223 ms 96.56.230.150
24 2026-08-24 10:09 639231621644955316
224 ms 96.56.230.150
23 2026-08-24 09:52 639231611478799259
229 ms 96.56.230.150
22 2026-08-24 08:59 639231579923718211
224 ms 96.56.230.150
21 2026-08-24 08:42 639231569810702936
237 ms 96.56.230.150
20 2026-08-24 08:25 639231559762411619
238 ms 96.56.230.150
19 2026-08-24 08:09 639231549663595407
227 ms 96.56.230.150
18 2026-08-24 07:16 639231518076817246
230 ms 96.56.230.150
17 2026-08-24 06:59 639231508078650885
219 ms 96.56.230.150
16 2026-08-24 06:43 639231498210697093
226 ms 96.56.230.150
15 2026-08-24 06:26 639231488109699360
226 ms 96.56.230.150
14 2026-08-24 05:34 639231456772510692
223 ms 96.56.230.150
13 2026-08-24 05:17 639231447084631185
214 ms 96.56.230.150
12 2026-08-24 05:01 639231437208519473
140 ms 96.56.230.150
11 2026-08-24 04:44 639231427209627490
230 ms 96.56.230.150
10 2026-08-24 03:52 639231395791246644
1609 ms 96.56.230.150
9 2026-08-24 03:36 639231386075551458
230 ms 96.56.230.150
8 2026-08-24 03:19 639231376208713791
228 ms 96.56.230.150
7 2026-08-24 03:03 639231366170589276
227 ms 96.56.230.150
6 2026-08-24 02:10 639231334732159368
230 ms 96.56.230.150
5 2026-08-24 01:54 639231325035670078
230 ms 96.56.230.150
4 2026-08-24 01:38 639231315132253837
221 ms 96.56.230.150
3 2026-08-24 01:21 639231305014280808
139 ms 96.56.230.150
2 2026-08-24 00:28 639231273779380675
231 ms 96.56.230.150
1 2026-08-24 00:13 639231264180839154
127 ms 96.56.230.150