DNS response history for ns2.casinotroya.pro

ns2.casinotroya.pro 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 30 DNS check records, 30 successful responses, 0 failed responses, and 385 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.casinotroya.pro.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

385 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

151.241.99.72

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 ns2.casinotroya.pro

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
30 2026-08-24 12:20 639231703815441688
2140 ms 151.241.99.72
29 2026-08-24 12:04 639231693747052549
2243 ms 151.241.99.72
28 2026-08-24 11:47 639231683712487276
13 ms 151.241.99.72
27 2026-08-24 11:30 639231673513573868
19 ms 151.241.99.72
26 2026-08-24 10:37 639231641791249939
32 ms 151.241.99.72
25 2026-08-24 10:21 639231631866211033
85 ms 151.241.99.72
24 2026-08-24 10:04 639231621644955316
49 ms 151.241.99.72
23 2026-08-24 09:47 639231611478799259
33 ms 151.241.99.72
22 2026-08-24 08:54 639231579923718211
19 ms 151.241.99.72
21 2026-08-24 08:37 639231569810702936
16 ms 151.241.99.72
20 2026-08-24 08:20 639231559762411619
23 ms 151.241.99.72
19 2026-08-24 08:04 639231549663595407
14 ms 151.241.99.72
18 2026-08-24 07:11 639231518076817246
25 ms 151.241.99.72
17 2026-08-24 06:55 639231508078650885
2037 ms 151.241.99.72
16 2026-08-24 06:38 639231498210697093
82 ms 151.241.99.72
15 2026-08-24 06:21 639231488109699360
2024 ms 151.241.99.72
14 2026-08-24 05:29 639231456772510692
16 ms 151.241.99.72
13 2026-08-24 05:13 639231447084631185
10 ms 151.241.99.72
12 2026-08-24 04:56 639231437208519473
37 ms 151.241.99.72
11 2026-08-24 04:40 639231427209627490
28 ms 151.241.99.72
10 2026-08-24 03:47 639231395791246644
18 ms 151.241.99.72
9 2026-08-24 03:31 639231386075551458
33 ms 151.241.99.72
8 2026-08-24 03:15 639231376208713791
12 ms 151.241.99.72
7 2026-08-24 02:58 639231366170589276
2246 ms 151.241.99.72
6 2026-08-24 02:06 639231334732159368
50 ms 151.241.99.72
5 2026-08-24 01:49 639231325035670078
29 ms 151.241.99.72
4 2026-08-24 01:33 639231315132253837
16 ms 151.241.99.72
3 2026-08-24 01:16 639231305014280808
156 ms 151.241.99.72
2 2026-08-24 00:24 639231273779380675
14 ms 151.241.99.72
1 2026-08-24 00:08 639231264180839154
29 ms 151.241.99.72