DNS response history for ns1.binadar.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

392 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

13.248.158.180

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.binadar.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
37 2026-08-26 12:22 639233434974187439
2040 ms 13.248.158.180
36 2026-08-26 12:05 639233424567558554
48 ms 13.248.158.180
35 2026-08-26 11:47 639233414056832719
23 ms 13.248.158.180
34 2026-08-26 11:30 639233403515141099
230 ms 13.248.158.180
33 2026-08-26 10:35 639233370841350248
13 ms 13.248.158.180
32 2026-08-26 10:18 639233360361507238
31 ms 13.248.158.180
31 2026-08-26 10:01 639233350067824371
62 ms 13.248.158.180
30 2026-08-26 09:43 639233339545274518
2079 ms 13.248.158.180
29 2026-08-26 09:26 639233329214918079
16 ms 13.248.158.180
28 2026-08-26 09:09 639233318749762337
63 ms 13.248.158.180
27 2026-08-26 08:51 639233308387917838
53 ms 13.248.158.180
26 2026-08-26 08:34 639233297961740122
57 ms 13.248.158.180
25 2026-08-26 08:16 639233287487159094
28 ms 13.248.158.180
24 2026-08-26 07:59 639233276995531707
48 ms 13.248.158.180
23 2026-08-26 07:41 639233266521568229
151 ms 13.248.158.180
22 2026-08-26 07:24 639233256081047431
39 ms 13.248.158.180
21 2026-08-26 06:30 639233223620132921
57 ms 13.248.158.180
20 2026-08-26 06:13 639233213287814244
39 ms 13.248.158.180
19 2026-08-26 05:55 639233202925983161
2029 ms 13.248.158.180
18 2026-08-26 05:38 639233192644780696
103 ms 13.248.158.180
17 2026-08-26 05:21 639233182401183833
19 ms 13.248.158.180
16 2026-08-26 05:04 639233172074181051
20 ms 13.248.158.180
15 2026-08-26 04:47 639233161808421455
150 ms 13.248.158.180
14 2026-08-26 04:29 639233151357344052
22 ms 13.248.158.180
13 2026-08-26 04:12 639233141034116946
217 ms 13.248.158.180
12 2026-08-26 03:55 639233130828334142
45 ms 13.248.158.180
11 2026-08-26 03:38 639233120373450007
2023 ms 13.248.158.180
10 2026-08-26 03:21 639233110066216193
48 ms 13.248.158.180
9 2026-08-26 02:27 639233078065410564
20 ms 13.248.158.180
8 2026-08-26 02:10 639233067787457832
-
7 2026-08-26 01:53 639233057501801162
2035 ms 13.248.158.180
6 2026-08-26 01:36 639233047089431703
31 ms 13.248.158.180
5 2026-08-26 01:18 639233036754790688
35 ms 13.248.158.180
4 2026-08-26 01:01 639233026412602472
7 ms 13.248.158.180
3 2026-08-26 00:44 639233016064066127
2145 ms 13.248.158.180
2 2026-08-26 00:27 639233005922655772
37 ms 13.248.158.180
1 2026-08-26 00:10 639232995672256907
41 ms 13.248.158.180