DNS response history for ns2.lotusbet605.com

ns2.lotusbet605.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-26. For this date, NameServerHistory found 31 DNS check records, 30 successful responses, 1 failed responses, and 92 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.lotusbet605.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

92 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

3.75.17.59

Most recently resolved hosting IP on selected date

Successful Responses

30

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.lotusbet605.com

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
31 2026-08-26 09:59 639233350067824371
126 ms 3.75.17.59
30 2026-08-26 09:41 639233339545274518
109 ms 3.75.17.59
29 2026-08-26 09:24 639233329214918079
156 ms 3.75.17.59
28 2026-08-26 09:07 639233318749762337
195 ms 3.75.17.59
27 2026-08-26 08:49 639233308387917838
18 ms 3.75.17.59
26 2026-08-26 08:32 639233297961740122
131 ms 3.75.17.59
25 2026-08-26 08:14 639233287487159094
107 ms 3.75.17.59
24 2026-08-26 07:57 639233276995531707
126 ms 3.75.17.59
23 2026-08-26 07:39 639233266521568229
89 ms 3.75.17.59
22 2026-08-26 07:22 639233256081047431
64 ms 3.75.17.59
21 2026-08-26 06:28 639233223620132921
53 ms 3.75.17.59
20 2026-08-26 06:11 639233213287814244
186 ms 3.75.17.59
19 2026-08-26 05:53 639233202925983161
93 ms 3.75.17.59
18 2026-08-26 05:36 639233192644780696
84 ms 3.75.17.59
17 2026-08-26 05:19 639233182401183833
82 ms 3.75.17.59
16 2026-08-26 05:02 639233172074181051
47 ms 3.75.17.59
15 2026-08-26 04:45 639233161808421455
-
14 2026-08-26 04:27 639233151357344052
45 ms 3.75.17.59
13 2026-08-26 04:10 639233141034116946
94 ms 3.75.17.59
12 2026-08-26 03:53 639233130828334142
38 ms 3.75.17.59
11 2026-08-26 03:36 639233120373450007
59 ms 3.75.17.59
10 2026-08-26 03:19 639233110066216193
115 ms 3.75.17.59
9 2026-08-26 02:25 639233078065410564
87 ms 3.75.17.59
8 2026-08-26 02:08 639233067787457832
100 ms 3.75.17.59
7 2026-08-26 01:51 639233057501801162
138 ms 3.75.17.59
6 2026-08-26 01:34 639233047089431703
25 ms 3.75.17.59
5 2026-08-26 01:16 639233036754790688
126 ms 3.75.17.59
4 2026-08-26 00:59 639233026412602472
22 ms 3.75.17.59
3 2026-08-26 00:42 639233016064066127
128 ms 3.75.17.59
2 2026-08-26 00:25 639233005922655772
41 ms 3.75.17.59
1 2026-08-26 00:08 639232995672256907
87 ms 3.75.17.59