DNS response history for ns1.berield.com

ns1.berield.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 37 DNS check records, 36 successful responses, 1 failed responses, and 536 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.berield.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

536 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

89.38.211.71

Most recently resolved hosting IP on selected date

Successful Responses

36

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.berield.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
37 2026-08-27 12:20 639234296664302575
87 ms 89.38.211.71
36 2026-08-27 12:02 639234286253196126
123 ms 89.38.211.71
35 2026-08-27 11:08 639234253963286387
86 ms 89.38.211.71
34 2026-08-27 10:51 639234243654907465
2061 ms 89.38.211.71
33 2026-08-27 10:34 639234233269654413
156 ms 89.38.211.71
32 2026-08-27 10:17 639234222943951923
118 ms 89.38.211.71
31 2026-08-27 09:59 639234212558002823
87 ms 89.38.211.71
30 2026-08-27 09:42 639234202117531850
86 ms 89.38.211.71
29 2026-08-27 09:25 639234191649612722
2035 ms 89.38.211.71
28 2026-08-27 09:07 639234181105879568
2095 ms 89.38.211.71
27 2026-08-27 08:50 639234170713214496
87 ms 89.38.211.71
26 2026-08-27 08:32 639234160341037652
100 ms 89.38.211.71
25 2026-08-27 08:15 639234149799404224
2110 ms 89.38.211.71
24 2026-08-27 07:58 639234139553286469
166 ms 89.38.211.71
23 2026-08-27 07:04 639234107183588293
93 ms 89.38.211.71
22 2026-08-27 06:47 639234096905435724
-
21 2026-08-27 06:30 639234086579410775
153 ms 89.38.211.71
20 2026-08-27 06:12 639234076291157956
84 ms 89.38.211.71
19 2026-08-27 05:55 639234065981939454
84 ms 89.38.211.71
18 2026-08-27 05:38 639234055548642997
135 ms 89.38.211.71
17 2026-08-27 05:21 639234045267979603
43 ms 89.38.211.71
16 2026-08-27 05:04 639234034999717463
86 ms 89.38.211.71
15 2026-08-27 04:47 639234024739225358
2210 ms 89.38.211.71
14 2026-08-27 04:29 639234014311170162
4092 ms 89.38.211.71
13 2026-08-27 04:12 639234003806017640
81 ms 89.38.211.71
12 2026-08-27 03:54 639233993356203030
83 ms 89.38.211.71
11 2026-08-27 03:01 639233961301716608
45 ms 89.38.211.71
10 2026-08-27 02:44 639233950834200647
114 ms 89.38.211.71
9 2026-08-27 02:26 639233940431849026
2061 ms 89.38.211.71
8 2026-08-27 02:09 639233930110596398
33 ms 89.38.211.71
7 2026-08-27 01:51 639233919705434540
82 ms 89.38.211.71
6 2026-08-27 01:34 639233909452807845
86 ms 89.38.211.71
5 2026-08-27 01:17 639233899096420820
29 ms 89.38.211.71
4 2026-08-27 01:00 639233888707824939
70 ms 89.38.211.71
3 2026-08-27 00:43 639233878461203802
83 ms 89.38.211.71
2 2026-08-27 00:25 639233868060868209
52 ms 89.38.211.71
1 2026-08-27 00:08 639233857450922991
91 ms 89.38.211.71