DNS response history for ns2.chimneyfireplacetopeka.com

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

26

Historical checks stored for this nameserver on selected date

Average Latency

378 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.81.158.106

Most recently resolved hosting IP on selected date

Successful Responses

26

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.chimneyfireplacetopeka.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
26 2026-08-26 08:24 639233287487159094
163 ms 51.81.158.106
25 2026-08-26 08:07 639233276995531707
332 ms 51.81.158.106
24 2026-08-26 07:49 639233266521568229
331 ms 51.81.158.106
23 2026-08-26 07:32 639233256081047431
351 ms 51.81.158.106
22 2026-08-26 06:38 639233223620132921
361 ms 51.81.158.106
21 2026-08-26 06:21 639233213287814244
221 ms 51.81.158.106
20 2026-08-26 06:03 639233202925983161
181 ms 51.81.158.106
19 2026-08-26 05:46 639233192644780696
366 ms 51.81.158.106
18 2026-08-26 05:29 639233182401183833
345 ms 51.81.158.106
17 2026-08-26 05:12 639233172074181051
341 ms 51.81.158.106
16 2026-08-26 04:55 639233161808421455
2176 ms 51.81.158.106
15 2026-08-26 04:38 639233151357344052
347 ms 51.81.158.106
14 2026-08-26 04:20 639233141034116946
371 ms 51.81.158.106
13 2026-08-26 04:03 639233130828334142
354 ms 51.81.158.106
12 2026-08-26 03:46 639233120373450007
331 ms 51.81.158.106
11 2026-08-26 03:29 639233110066216193
173 ms 51.81.158.106
10 2026-08-26 02:35 639233078065410564
190 ms 51.81.158.106
9 2026-08-26 02:18 639233067787457832
344 ms 51.81.158.106
8 2026-08-26 02:01 639233057501801162
155 ms 51.81.158.106
7 2026-08-26 01:44 639233047089431703
344 ms 51.81.158.106
6 2026-08-26 01:27 639233036754790688
333 ms 51.81.158.106
5 2026-08-26 01:09 639233026412602472
355 ms 51.81.158.106
4 2026-08-26 00:52 639233016064066127
333 ms 51.81.158.106
3 2026-08-26 00:35 639233005922655772
330 ms 51.81.158.106
2 2026-08-26 00:18 639232995672256907
339 ms 51.81.158.106
1 2026-08-26 00:01 639232985300872416
355 ms 51.81.158.106