DNS response history for ns4.binaryracks.com

ns4.binaryracks.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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 216 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 ns4.binaryracks.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

216 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

196.46.188.5

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns4.binaryracks.com

Showing DNS history for 2026-08-26 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
33 2026-08-26 10:42 639233370841350248
30 ms 196.46.188.5
32 2026-08-26 10:24 639233360361507238
33 ms 196.46.188.5
31 2026-08-26 10:07 639233350067824371
75 ms 196.46.188.5
30 2026-08-26 09:50 639233339545274518
15 ms 196.46.188.5
29 2026-08-26 09:32 639233329214918079
9 ms 196.46.188.5
28 2026-08-26 09:15 639233318749762337
29 ms 196.46.188.5
27 2026-08-26 08:58 639233308387917838
31 ms 196.46.188.5
26 2026-08-26 08:40 639233297961740122
31 ms 196.46.188.5
25 2026-08-26 08:23 639233287487159094
30 ms 196.46.188.5
24 2026-08-26 08:05 639233276995531707
9 ms 196.46.188.5
23 2026-08-26 07:48 639233266521568229
36 ms 196.46.188.5
22 2026-08-26 07:30 639233256081047431
52 ms 196.46.188.5
21 2026-08-26 06:37 639233223620132921
31 ms 196.46.188.5
20 2026-08-26 06:19 639233213287814244
2013 ms 196.46.188.5
19 2026-08-26 06:02 639233202925983161
31 ms 196.46.188.5
18 2026-08-26 05:45 639233192644780696
30 ms 196.46.188.5
17 2026-08-26 05:28 639233182401183833
14 ms 196.46.188.5
16 2026-08-26 05:11 639233172074181051
3 ms 196.46.188.5
15 2026-08-26 04:53 639233161808421455
30 ms 196.46.188.5
14 2026-08-26 04:36 639233151357344052
75 ms 196.46.188.5
13 2026-08-26 04:19 639233141034116946
32 ms 196.46.188.5
12 2026-08-26 04:02 639233130828334142
58 ms 196.46.188.5
11 2026-08-26 03:44 639233120373450007
7 ms 196.46.188.5
10 2026-08-26 03:27 639233110066216193
9 ms 196.46.188.5
9 2026-08-26 02:34 639233078065410564
31 ms 196.46.188.5
8 2026-08-26 02:17 639233067787457832
2047 ms 196.46.188.5
7 2026-08-26 02:00 639233057501801162
639 ms 196.46.188.5
6 2026-08-26 01:42 639233047089431703
30 ms 196.46.188.5
5 2026-08-26 01:25 639233036754790688
16 ms 196.46.188.5
4 2026-08-26 01:08 639233026412602472
1554 ms 196.46.188.5
3 2026-08-26 00:50 639233016064066127
30 ms 196.46.188.5
2 2026-08-26 00:33 639233005922655772
58 ms 196.46.188.5
1 2026-08-26 00:16 639232995672256907
11 ms 196.46.188.5