DNS response history for ns2.newbernwebdesign.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

357 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.16.239.36

Most recently resolved hosting IP on selected date

Successful Responses

35

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.newbernwebdesign.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
35 2026-08-27 11:13 639234253963286387
232 ms 69.16.239.36
34 2026-08-27 10:55 639234243654907465
114 ms 69.16.239.36
33 2026-08-27 10:38 639234233269654413
219 ms 69.16.239.36
32 2026-08-27 10:21 639234222943951923
168 ms 69.16.239.36
31 2026-08-27 10:03 639234212558002823
229 ms 69.16.239.36
30 2026-08-27 09:46 639234202117531850
137 ms 69.16.239.36
29 2026-08-27 09:29 639234191649612722
241 ms 69.16.239.36
28 2026-08-27 09:11 639234181105879568
305 ms 69.16.239.36
27 2026-08-27 08:54 639234170713214496
234 ms 69.16.239.36
26 2026-08-27 08:36 639234160341037652
235 ms 69.16.239.36
25 2026-08-27 08:19 639234149799404224
240 ms 69.16.239.36
24 2026-08-27 08:02 639234139553286469
230 ms 69.16.239.36
23 2026-08-27 07:08 639234107183588293
110 ms 69.16.239.36
22 2026-08-27 06:51 639234096905435724
121 ms 69.16.239.36
21 2026-08-27 06:34 639234086579410775
131 ms 69.16.239.36
20 2026-08-27 06:16 639234076291157956
232 ms 69.16.239.36
19 2026-08-27 05:59 639234065981939454
4121 ms 69.16.239.36
18 2026-08-27 05:42 639234055548642997
225 ms 69.16.239.36
17 2026-08-27 05:25 639234045267979603
125 ms 69.16.239.36
16 2026-08-27 05:08 639234034999717463
2148 ms 69.16.239.36
15 2026-08-27 04:50 639234024739225358
230 ms 69.16.239.36
14 2026-08-27 04:33 639234014311170162
231 ms 69.16.239.36
13 2026-08-27 04:16 639234003806017640
115 ms 69.16.239.36
12 2026-08-27 03:58 639233993356203030
226 ms 69.16.239.36
11 2026-08-27 03:05 639233961301716608
115 ms 69.16.239.36
10 2026-08-27 02:48 639233950834200647
224 ms 69.16.239.36
9 2026-08-27 02:30 639233940431849026
225 ms 69.16.239.36
8 2026-08-27 02:13 639233930110596398
116 ms 69.16.239.36
7 2026-08-27 01:56 639233919705434540
111 ms 69.16.239.36
6 2026-08-27 01:39 639233909452807845
228 ms 69.16.239.36
5 2026-08-27 01:21 639233899096420820
112 ms 69.16.239.36
4 2026-08-27 01:04 639233888707824939
114 ms 69.16.239.36
3 2026-08-27 00:47 639233878461203802
225 ms 69.16.239.36
2 2026-08-27 00:29 639233868060868209
226 ms 69.16.239.36
1 2026-08-27 00:12 639233857450922991
216 ms 69.16.239.36