DNS response history for ns2.casino-1win.top

ns2.casino-1win.top 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 32 DNS check records, 32 successful responses, 0 failed responses, and 41 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.casino-1win.top.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

41 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 06:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

149.33.33.115

Most recently resolved hosting IP on selected date

Successful Responses

32

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.casino-1win.top

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
32 2026-08-24 06:36 639231498210697093
41 ms 149.33.33.115
31 2026-08-24 06:36 639231498210697093
41 ms 37.1.194.113
30 2026-08-24 06:20 639231488109699360
108 ms 149.33.33.115
29 2026-08-24 06:20 639231488109699360
108 ms 37.1.194.113
28 2026-08-24 05:27 639231456772510692
39 ms 149.33.33.115
27 2026-08-24 05:27 639231456772510692
39 ms 37.1.194.113
26 2026-08-24 05:11 639231447084631185
35 ms 37.1.194.113
25 2026-08-24 05:11 639231447084631185
35 ms 149.33.33.115
24 2026-08-24 04:55 639231437208519473
46 ms 37.1.194.113
23 2026-08-24 04:55 639231437208519473
46 ms 149.33.33.115
22 2026-08-24 04:38 639231427209627490
49 ms 37.1.194.113
21 2026-08-24 04:38 639231427209627490
49 ms 149.33.33.115
20 2026-08-24 03:46 639231395791246644
45 ms 149.33.33.115
19 2026-08-24 03:46 639231395791246644
45 ms 37.1.194.113
18 2026-08-24 03:30 639231386075551458
17 ms 37.1.194.113
17 2026-08-24 03:30 639231386075551458
17 ms 149.33.33.115
16 2026-08-24 03:13 639231376208713791
29 ms 37.1.194.113
15 2026-08-24 03:13 639231376208713791
29 ms 149.33.33.115
14 2026-08-24 02:56 639231366170589276
48 ms 149.33.33.115
13 2026-08-24 02:56 639231366170589276
48 ms 37.1.194.113
12 2026-08-24 02:04 639231334732159368
2 ms 149.33.33.115
11 2026-08-24 02:04 639231334732159368
2 ms 37.1.194.113
10 2026-08-24 01:48 639231325035670078
12 ms 149.33.33.115
9 2026-08-24 01:48 639231325035670078
12 ms 37.1.194.113
8 2026-08-24 01:31 639231315132253837
18 ms 149.33.33.115
7 2026-08-24 01:31 639231315132253837
18 ms 37.1.194.113
6 2026-08-24 01:14 639231305014280808
59 ms 149.33.33.115
5 2026-08-24 01:14 639231305014280808
59 ms 37.1.194.113
4 2026-08-24 00:22 639231273779380675
61 ms 37.1.194.113
3 2026-08-24 00:22 639231273779380675
61 ms 149.33.33.115
2 2026-08-24 00:06 639231264180839154
47 ms 37.1.194.113
1 2026-08-24 00:06 639231264180839154
47 ms 149.33.33.115