DNS response history for ns2.behineserver.com

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

26

Historical checks stored for this nameserver on selected date

Average Latency

96 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.202.6.220

Most recently resolved hosting IP on selected date

Successful Responses

26

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.behineserver.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
26 2026-08-24 10:36 639231641791249939
112 ms 5.202.6.220
25 2026-08-24 10:20 639231631866211033
171 ms 5.202.6.220
24 2026-08-24 10:03 639231621644955316
33 ms 5.202.6.220
23 2026-08-24 09:46 639231611478799259
202 ms 5.202.6.220
22 2026-08-24 08:53 639231579923718211
91 ms 5.202.6.220
21 2026-08-24 08:36 639231569810702936
89 ms 5.202.6.220
20 2026-08-24 08:19 639231559762411619
77 ms 5.202.6.220
19 2026-08-24 08:03 639231549663595407
120 ms 5.202.6.220
18 2026-08-24 07:10 639231518076817246
145 ms 5.202.6.220
17 2026-08-24 06:54 639231508078650885
140 ms 5.202.6.220
16 2026-08-24 06:37 639231498210697093
208 ms 5.202.6.220
15 2026-08-24 06:20 639231488109699360
9 ms 5.202.6.220
14 2026-08-24 05:28 639231456772510692
72 ms 5.202.6.220
13 2026-08-24 05:12 639231447084631185
113 ms 5.202.6.220
12 2026-08-24 04:55 639231437208519473
57 ms 5.202.6.220
11 2026-08-24 04:39 639231427209627490
65 ms 5.202.6.220
10 2026-08-24 03:46 639231395791246644
177 ms 5.202.6.220
9 2026-08-24 03:30 639231386075551458
58 ms 5.202.6.220
8 2026-08-24 03:14 639231376208713791
64 ms 5.202.6.220
7 2026-08-24 02:57 639231366170589276
108 ms 5.202.6.220
6 2026-08-24 02:05 639231334732159368
96 ms 5.202.6.220
5 2026-08-24 01:48 639231325035670078
23 ms 5.202.6.220
4 2026-08-24 01:32 639231315132253837
55 ms 5.202.6.220
3 2026-08-24 01:15 639231305014280808
51 ms 5.202.6.220
2 2026-08-24 00:23 639231273779380675
50 ms 5.202.6.220
1 2026-08-24 00:07 639231264180839154
106 ms 5.202.6.220