DNS response history for ns2.quincywaterdamage.com

ns2.quincywaterdamage.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-27. For this date, NameServerHistory found 28 DNS check records, 27 successful responses, 1 failed responses, and 241 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.quincywaterdamage.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

241 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.148.25.195

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.quincywaterdamage.com

Showing DNS history for 2026-08-27 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-27 09:09 639234181105879568
256 ms 135.148.25.195
27 2026-08-27 08:52 639234170713214496
274 ms 135.148.25.195
26 2026-08-27 08:35 639234160341037652
257 ms 135.148.25.195
25 2026-08-27 08:17 639234149799404224
264 ms 135.148.25.195
24 2026-08-27 08:00 639234139553286469
2035 ms 135.148.25.195
23 2026-08-27 07:06 639234107183588293
238 ms 135.148.25.195
22 2026-08-27 06:49 639234096905435724
241 ms 135.148.25.195
21 2026-08-27 06:32 639234086579410775
13 ms 135.148.25.195
20 2026-08-27 06:15 639234076291157956
155 ms 135.148.25.195
19 2026-08-27 05:58 639234065981939454
-
18 2026-08-27 05:40 639234055548642997
15 ms 135.148.25.195
17 2026-08-27 05:23 639234045267979603
12 ms 135.148.25.195
16 2026-08-27 05:06 639234034999717463
207 ms 135.148.25.195
15 2026-08-27 04:49 639234024739225358
203 ms 135.148.25.195
14 2026-08-27 04:32 639234014311170162
110 ms 135.148.25.195
13 2026-08-27 04:14 639234003806017640
206 ms 135.148.25.195
12 2026-08-27 03:57 639233993356203030
100 ms 135.148.25.195
11 2026-08-27 03:03 639233961301716608
209 ms 135.148.25.195
10 2026-08-27 02:46 639233950834200647
215 ms 135.148.25.195
9 2026-08-27 02:28 639233940431849026
107 ms 135.148.25.195
8 2026-08-27 02:11 639233930110596398
207 ms 135.148.25.195
7 2026-08-27 01:54 639233919705434540
113 ms 135.148.25.195
6 2026-08-27 01:37 639233909452807845
206 ms 135.148.25.195
5 2026-08-27 01:20 639233899096420820
106 ms 135.148.25.195
4 2026-08-27 01:02 639233888707824939
205 ms 135.148.25.195
3 2026-08-27 00:45 639233878461203802
218 ms 135.148.25.195
2 2026-08-27 00:28 639233868060868209
208 ms 135.148.25.195
1 2026-08-27 00:10 639233857450922991
136 ms 135.148.25.195