DNS response history for ns2.otocasino265.com

ns2.otocasino265.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-25. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 316 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.otocasino265.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

316 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:04

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

38

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.otocasino265.com

Showing DNS history for 2026-08-25 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
38 2026-08-25 13:04 639232597643611557
38 ms 3.75.17.59
37 2026-08-25 12:47 639232587225721862
15 ms 3.75.17.59
36 2026-08-25 12:30 639232576780683689
87 ms 3.75.17.59
35 2026-08-25 12:12 639232566381512620
134 ms 3.75.17.59
34 2026-08-25 11:55 639232556111768563
30 ms 3.75.17.59
33 2026-08-25 11:38 639232545839529039
39 ms 3.75.17.59
32 2026-08-25 11:21 639232535349285207
44 ms 3.75.17.59
31 2026-08-25 11:03 639232524938080723
46 ms 3.75.17.59
30 2026-08-25 10:10 639232492740373468
40 ms 3.75.17.59
29 2026-08-25 09:52 639232482235303141
2026 ms 3.75.17.59
28 2026-08-25 09:35 639232471861770303
43 ms 3.75.17.59
27 2026-08-25 09:18 639232461630217327
46 ms 3.75.17.59
26 2026-08-25 09:00 639232451282965990
41 ms 3.75.17.59
25 2026-08-25 08:43 639232440814614938
48 ms 3.75.17.59
24 2026-08-25 08:26 639232430410720425
74 ms 3.75.17.59
23 2026-08-25 08:08 639232420003096185
50 ms 3.75.17.59
22 2026-08-25 07:51 639232409467287444
4013 ms 3.75.17.59
21 2026-08-25 07:33 639232399077195997
14 ms 3.75.17.59
20 2026-08-25 07:16 639232388731528337
2144 ms 3.75.17.59
19 2026-08-25 06:59 639232378288598612
20 ms 3.75.17.59
18 2026-08-25 06:05 639232346196373643
44 ms 3.75.17.59
17 2026-08-25 05:48 639232336112370741
69 ms 3.75.17.59
16 2026-08-25 05:32 639232326146508970
123 ms 3.75.17.59
15 2026-08-25 05:15 639232316189381720
44 ms 3.75.17.59
14 2026-08-25 04:59 639232306217998913
28 ms 3.75.17.59
13 2026-08-25 04:42 639232296255744174
49 ms 3.75.17.59
12 2026-08-25 04:25 639232286095760789
50 ms 3.75.17.59
11 2026-08-25 04:08 639232276086186273
42 ms 3.75.17.59
10 2026-08-25 03:52 639232265900986425
54 ms 3.75.17.59
9 2026-08-25 03:35 639232255723518075
2033 ms 3.75.17.59
8 2026-08-25 03:17 639232245484452890
49 ms 3.75.17.59
7 2026-08-25 03:00 639232235157175331
36 ms 3.75.17.59
6 2026-08-25 02:07 639232203197189095
142 ms 3.75.17.59
5 2026-08-25 01:50 639232192844564298
17 ms 3.75.17.59
4 2026-08-25 01:33 639232182496008942
67 ms 3.75.17.59
3 2026-08-25 01:15 639232172197053132
40 ms 3.75.17.59
2 2026-08-25 00:22 639232140250307418
113 ms 3.75.17.59
1 2026-08-25 00:05 639232129927860324
33 ms 3.75.17.59