DNS response history for ns2.exbet-casino.com

ns2.exbet-casino.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 28 DNS check records, 28 successful responses, 0 failed responses, and 257 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.exbet-casino.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

257 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.180.157.160

Most recently resolved hosting IP on selected date

Successful Responses

28

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.exbet-casino.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
28 2026-08-26 09:10 639233318749762337
31 ms 38.180.157.160
27 2026-08-26 08:53 639233308387917838
52 ms 38.180.157.160
26 2026-08-26 08:35 639233297961740122
31 ms 38.180.157.160
25 2026-08-26 08:18 639233287487159094
49 ms 38.180.157.160
24 2026-08-26 08:00 639233276995531707
28 ms 38.180.157.160
23 2026-08-26 07:43 639233266521568229
48 ms 38.180.157.160
22 2026-08-26 07:25 639233256081047431
52 ms 38.180.157.160
21 2026-08-26 06:31 639233223620132921
79 ms 38.180.157.160
20 2026-08-26 06:14 639233213287814244
45 ms 38.180.157.160
19 2026-08-26 05:57 639233202925983161
56 ms 38.180.157.160
18 2026-08-26 05:40 639233192644780696
12 ms 38.180.157.160
17 2026-08-26 05:22 639233182401183833
2027 ms 38.180.157.160
16 2026-08-26 05:05 639233172074181051
54 ms 38.180.157.160
15 2026-08-26 04:48 639233161808421455
50 ms 38.180.157.160
14 2026-08-26 04:31 639233151357344052
33 ms 38.180.157.160
13 2026-08-26 04:14 639233141034116946
23 ms 38.180.157.160
12 2026-08-26 03:57 639233130828334142
25 ms 38.180.157.160
11 2026-08-26 03:39 639233120373450007
19 ms 38.180.157.160
10 2026-08-26 03:22 639233110066216193
41 ms 38.180.157.160
9 2026-08-26 02:29 639233078065410564
60 ms 38.180.157.160
8 2026-08-26 02:12 639233067787457832
87 ms 38.180.157.160
7 2026-08-26 01:55 639233057501801162
30 ms 38.180.157.160
6 2026-08-26 01:37 639233047089431703
39 ms 38.180.157.160
5 2026-08-26 01:20 639233036754790688
35 ms 38.180.157.160
4 2026-08-26 01:03 639233026412602472
2012 ms 38.180.157.160
3 2026-08-26 00:45 639233016064066127
48 ms 38.180.157.160
2 2026-08-26 00:28 639233005922655772
2015 ms 38.180.157.160
1 2026-08-26 00:11 639232995672256907
105 ms 38.180.157.160