DNS response history for ns2.behundreds.com

ns2.behundreds.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 407 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.behundreds.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

407 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

107.175.212.78

Most recently resolved hosting IP on selected date

Successful Responses

36

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.behundreds.com

Showing DNS history for 2026-08-24 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
36 2026-08-24 15:16 639231807961539652
213 ms 107.175.212.78
35 2026-08-24 14:59 639231797631669865
220 ms 107.175.212.78
34 2026-08-24 14:06 639231765923559455
213 ms 107.175.212.78
33 2026-08-24 13:49 639231755868832964
370 ms 107.175.212.78
32 2026-08-24 13:32 639231745628278877
223 ms 107.175.212.78
31 2026-08-24 13:15 639231735407682062
226 ms 107.175.212.78
30 2026-08-24 12:23 639231703815441688
2115 ms 107.175.212.78
29 2026-08-24 12:06 639231693747052549
129 ms 107.175.212.78
28 2026-08-24 11:49 639231683712487276
220 ms 107.175.212.78
27 2026-08-24 11:32 639231673513573868
114 ms 107.175.212.78
26 2026-08-24 10:39 639231641791249939
164 ms 107.175.212.78
25 2026-08-24 10:23 639231631866211033
108 ms 107.175.212.78
24 2026-08-24 10:06 639231621644955316
234 ms 107.175.212.78
23 2026-08-24 09:49 639231611478799259
226 ms 107.175.212.78
22 2026-08-24 08:56 639231579923718211
2105 ms 107.175.212.78
21 2026-08-24 08:39 639231569810702936
2111 ms 107.175.212.78
20 2026-08-24 08:22 639231559762411619
112 ms 107.175.212.78
19 2026-08-24 08:06 639231549663595407
216 ms 107.175.212.78
18 2026-08-24 07:13 639231518076817246
2210 ms 107.175.212.78
17 2026-08-24 06:57 639231508078650885
105 ms 107.175.212.78
16 2026-08-24 06:40 639231498210697093
211 ms 107.175.212.78
15 2026-08-24 06:23 639231488109699360
219 ms 107.175.212.78
14 2026-08-24 05:31 639231456772510692
211 ms 107.175.212.78
13 2026-08-24 05:15 639231447084631185
207 ms 107.175.212.78
12 2026-08-24 04:58 639231437208519473
120 ms 107.175.212.78
11 2026-08-24 04:42 639231427209627490
104 ms 107.175.212.78
10 2026-08-24 03:49 639231395791246644
218 ms 107.175.212.78
9 2026-08-24 03:33 639231386075551458
209 ms 107.175.212.78
8 2026-08-24 03:17 639231376208713791
230 ms 107.175.212.78
7 2026-08-24 03:00 639231366170589276
105 ms 107.175.212.78
6 2026-08-24 02:08 639231334732159368
205 ms 107.175.212.78
5 2026-08-24 01:51 639231325035670078
212 ms 107.175.212.78
4 2026-08-24 01:35 639231315132253837
218 ms 107.175.212.78
3 2026-08-24 01:18 639231305014280808
224 ms 107.175.212.78
2 2026-08-24 00:26 639231273779380675
211 ms 107.175.212.78
1 2026-08-24 00:10 639231264180839154
110 ms 107.175.212.78