DNS response history for ns2.baji-onlinecasino.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

102 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:46

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

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.baji-onlinecasino.com

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
38 2026-08-24 15:46 639231828211839931
54 ms 38.180.157.160
37 2026-08-24 15:29 639231818080917481
174 ms 38.180.157.160
36 2026-08-24 15:12 639231807961539652
194 ms 38.180.157.160
35 2026-08-24 14:55 639231797631669865
57 ms 38.180.157.160
34 2026-08-24 14:02 639231765923559455
88 ms 38.180.157.160
33 2026-08-24 13:46 639231755868832964
97 ms 38.180.157.160
32 2026-08-24 13:29 639231745628278877
167 ms 38.180.157.160
31 2026-08-24 13:11 639231735407682062
121 ms 38.180.157.160
30 2026-08-24 12:19 639231703815441688
108 ms 38.180.157.160
29 2026-08-24 12:02 639231693747052549
153 ms 38.180.157.160
28 2026-08-24 11:45 639231683712487276
131 ms 38.180.157.160
27 2026-08-24 11:28 639231673513573868
116 ms 38.180.157.160
26 2026-08-24 10:35 639231641791249939
33 ms 38.180.157.160
25 2026-08-24 10:19 639231631866211033
55 ms 38.180.157.160
24 2026-08-24 10:02 639231621644955316
104 ms 38.180.157.160
23 2026-08-24 09:45 639231611478799259
153 ms 38.180.157.160
22 2026-08-24 08:52 639231579923718211
36 ms 38.180.157.160
21 2026-08-24 08:36 639231569810702936
7 ms 38.180.157.160
20 2026-08-24 08:19 639231559762411619
205 ms 38.180.157.160
19 2026-08-24 08:02 639231549663595407
195 ms 38.180.157.160
18 2026-08-24 07:09 639231518076817246
210 ms 38.180.157.160
17 2026-08-24 06:53 639231508078650885
84 ms 38.180.157.160
16 2026-08-24 06:36 639231498210697093
59 ms 38.180.157.160
15 2026-08-24 06:20 639231488109699360
147 ms 38.180.157.160
14 2026-08-24 05:27 639231456772510692
109 ms 38.180.157.160
13 2026-08-24 05:11 639231447084631185
65 ms 38.180.157.160
12 2026-08-24 04:55 639231437208519473
19 ms 38.180.157.160
11 2026-08-24 04:38 639231427209627490
138 ms 38.180.157.160
10 2026-08-24 03:45 639231395791246644
50 ms 38.180.157.160
9 2026-08-24 03:29 639231386075551458
18 ms 38.180.157.160
8 2026-08-24 03:13 639231376208713791
141 ms 38.180.157.160
7 2026-08-24 02:56 639231366170589276
53 ms 38.180.157.160
6 2026-08-24 02:04 639231334732159368
16 ms 38.180.157.160
5 2026-08-24 01:48 639231325035670078
6 ms 38.180.157.160
4 2026-08-24 01:31 639231315132253837
3 ms 38.180.157.160
3 2026-08-24 01:14 639231305014280808
102 ms 38.180.157.160
2 2026-08-24 00:22 639231273779380675
193 ms 38.180.157.160
1 2026-08-24 00:06 639231264180839154
200 ms 38.180.157.160