DNS response history for ns2.kansasgamblingsites.com

ns2.kansasgamblingsites.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 32 DNS check records, 32 successful responses, 0 failed responses, and 464 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.kansasgamblingsites.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

464 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.227.166.140

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.kansasgamblingsites.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
32 2026-08-24 13:32 639231745628278877
235 ms 67.227.166.140
31 2026-08-24 13:15 639231735407682062
2148 ms 67.227.166.140
30 2026-08-24 12:22 639231703815441688
233 ms 67.227.166.140
29 2026-08-24 12:05 639231693747052549
238 ms 67.227.166.140
28 2026-08-24 11:49 639231683712487276
231 ms 67.227.166.140
27 2026-08-24 11:32 639231673513573868
134 ms 67.227.166.140
26 2026-08-24 10:39 639231641791249939
227 ms 67.227.166.140
25 2026-08-24 10:22 639231631866211033
232 ms 67.227.166.140
24 2026-08-24 10:05 639231621644955316
151 ms 67.227.166.140
23 2026-08-24 09:48 639231611478799259
264 ms 67.227.166.140
22 2026-08-24 08:56 639231579923718211
245 ms 67.227.166.140
21 2026-08-24 08:39 639231569810702936
246 ms 67.227.166.140
20 2026-08-24 08:22 639231559762411619
119 ms 67.227.166.140
19 2026-08-24 08:05 639231549663595407
229 ms 67.227.166.140
18 2026-08-24 07:13 639231518076817246
224 ms 67.227.166.140
17 2026-08-24 06:56 639231508078650885
125 ms 67.227.166.140
16 2026-08-24 06:39 639231498210697093
228 ms 67.227.166.140
15 2026-08-24 06:23 639231488109699360
2127 ms 67.227.166.140
14 2026-08-24 05:31 639231456772510692
246 ms 67.227.166.140
13 2026-08-24 05:14 639231447084631185
224 ms 67.227.166.140
12 2026-08-24 04:58 639231437208519473
121 ms 67.227.166.140
11 2026-08-24 04:41 639231427209627490
226 ms 67.227.166.140
10 2026-08-24 03:49 639231395791246644
410 ms 67.227.166.140
9 2026-08-24 03:33 639231386075551458
487 ms 67.227.166.140
8 2026-08-24 03:16 639231376208713791
249 ms 67.227.166.140
7 2026-08-24 02:59 639231366170589276
237 ms 67.227.166.140
6 2026-08-24 02:07 639231334732159368
137 ms 67.227.166.140
5 2026-08-24 01:51 639231325035670078
226 ms 67.227.166.140
4 2026-08-24 01:34 639231315132253837
130 ms 67.227.166.140
3 2026-08-24 01:18 639231305014280808
231 ms 67.227.166.140
2 2026-08-24 00:25 639231273779380675
2157 ms 67.227.166.140
1 2026-08-24 00:09 639231264180839154
2142 ms 67.227.166.140