DNS response history for grizzlybearhandyman.com

grizzlybearhandyman.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 2676 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 grizzlybearhandyman.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

2676 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

174.160.235.172

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 grizzlybearhandyman.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:28 639233287487159094
2031 ms 174.160.235.172
25 2026-08-26 08:10 639233276995531707
2030 ms 174.160.235.172
24 2026-08-26 07:53 639233266521568229
2114 ms 174.160.235.172
23 2026-08-26 07:35 639233256081047431
2023 ms 174.160.235.172
22 2026-08-26 06:41 639233223620132921
2029 ms 174.160.235.172
21 2026-08-26 06:24 639233213287814244
3560 ms 174.160.235.172
20 2026-08-26 06:07 639233202925983161
3526 ms 174.160.235.172
19 2026-08-26 05:49 639233192644780696
2023 ms 174.160.235.172
18 2026-08-26 05:32 639233182401183833
3561 ms 174.160.235.172
17 2026-08-26 05:15 639233172074181051
3559 ms 174.160.235.172
16 2026-08-26 04:58 639233161808421455
2051 ms 174.160.235.172
15 2026-08-26 04:41 639233151357344052
2115 ms 174.160.235.172
14 2026-08-26 04:23 639233141034116946
3529 ms 174.160.235.172
13 2026-08-26 04:06 639233130828334142
2036 ms 174.160.235.172
12 2026-08-26 03:49 639233120373450007
2020 ms 174.160.235.172
11 2026-08-26 03:32 639233110066216193
3520 ms 174.160.235.172
10 2026-08-26 02:38 639233078065410564
2045 ms 174.160.235.172
9 2026-08-26 02:21 639233067787457832
3541 ms 174.160.235.172
8 2026-08-26 02:04 639233057501801162
3526 ms 174.160.235.172
7 2026-08-26 01:47 639233047089431703
3521 ms 174.160.235.172
6 2026-08-26 01:30 639233036754790688
3525 ms 174.160.235.172
5 2026-08-26 01:13 639233026412602472
3519 ms 174.160.235.172
4 2026-08-26 00:55 639233016064066127
2022 ms 174.160.235.172
3 2026-08-26 00:38 639233005922655772
2116 ms 174.160.235.172
2 2026-08-26 00:21 639232995672256907
2019 ms 174.160.235.172
1 2026-08-26 00:04 639232985300872416
2024 ms 174.160.235.172