DNS response history for ns1.newenglandfirenews.net

ns1.newenglandfirenews.net 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 35 DNS check records, 34 successful responses, 1 failed responses, and 302 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 ns1.newenglandfirenews.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

302 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

18.224.134.165

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.newenglandfirenews.net

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
35 2026-08-27 11:09 639234253963286387
215 ms 18.224.134.165
34 2026-08-27 10:52 639234243654907465
200 ms 18.224.134.165
33 2026-08-27 10:35 639234233269654413
210 ms 18.224.134.165
32 2026-08-27 10:18 639234222943951923
210 ms 18.224.134.165
31 2026-08-27 10:00 639234212558002823
204 ms 18.224.134.165
30 2026-08-27 09:43 639234202117531850
213 ms 18.224.134.165
29 2026-08-27 09:26 639234191649612722
210 ms 18.224.134.165
28 2026-08-27 09:08 639234181105879568
202 ms 18.224.134.165
27 2026-08-27 08:51 639234170713214496
202 ms 18.224.134.165
26 2026-08-27 08:33 639234160341037652
442 ms 18.224.134.165
25 2026-08-27 08:16 639234149799404224
201 ms 18.224.134.165
24 2026-08-27 07:59 639234139553286469
196 ms 18.224.134.165
23 2026-08-27 07:05 639234107183588293
116 ms 18.224.134.165
22 2026-08-27 06:48 639234096905435724
209 ms 18.224.134.165
21 2026-08-27 06:31 639234086579410775
208 ms 18.224.134.165
20 2026-08-27 06:14 639234076291157956
2141 ms 18.224.134.165
19 2026-08-27 05:56 639234065981939454
198 ms 18.224.134.165
18 2026-08-27 05:39 639234055548642997
230 ms 18.224.134.165
17 2026-08-27 05:22 639234045267979603
234 ms 18.224.134.165
16 2026-08-27 05:05 639234034999717463
199 ms 18.224.134.165
15 2026-08-27 04:48 639234024739225358
206 ms 18.224.134.165
14 2026-08-27 04:30 639234014311170162
207 ms 18.224.134.165
13 2026-08-27 04:13 639234003806017640
202 ms 18.224.134.165
12 2026-08-27 03:55 639233993356203030
205 ms 18.224.134.165
11 2026-08-27 03:02 639233961301716608
10 ms 18.224.134.165
10 2026-08-27 02:45 639233950834200647
2120 ms 18.224.134.165
9 2026-08-27 02:27 639233940431849026
207 ms 18.224.134.165
8 2026-08-27 02:10 639233930110596398
196 ms 18.224.134.165
7 2026-08-27 01:53 639233919705434540
204 ms 18.224.134.165
6 2026-08-27 01:35 639233909452807845
272 ms 18.224.134.165
5 2026-08-27 01:18 639233899096420820
-
4 2026-08-27 01:01 639233888707824939
8 ms 18.224.134.165
3 2026-08-27 00:44 639233878461203802
23 ms 18.224.134.165
2 2026-08-27 00:26 639233868060868209
7 ms 18.224.134.165
1 2026-08-27 00:09 639233857450922991
163 ms 18.224.134.165