DNS response history for ns1.binarioserver.com

ns1.binarioserver.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, 37 successful responses, 0 failed responses, and 145 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.binarioserver.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

145 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

63.250.38.233

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns1.binarioserver.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:18 639233434974187439
34 ms 63.250.38.233
36 2026-08-26 12:01 639233424567558554
30 ms 63.250.38.233
35 2026-08-26 11:43 639233414056832719
28 ms 63.250.38.233
34 2026-08-26 11:26 639233403515141099
33 ms 63.250.38.233
33 2026-08-26 10:31 639233370841350248
34 ms 63.250.38.233
32 2026-08-26 10:14 639233360361507238
21 ms 63.250.38.233
31 2026-08-26 09:57 639233350067824371
65 ms 63.250.38.233
30 2026-08-26 09:39 639233339545274518
27 ms 63.250.38.233
29 2026-08-26 09:22 639233329214918079
25 ms 63.250.38.233
28 2026-08-26 09:05 639233318749762337
22 ms 63.250.38.233
27 2026-08-26 08:47 639233308387917838
76 ms 63.250.38.233
26 2026-08-26 08:30 639233297961740122
73 ms 63.250.38.233
25 2026-08-26 08:12 639233287487159094
19 ms 63.250.38.233
24 2026-08-26 07:55 639233276995531707
25 ms 63.250.38.233
23 2026-08-26 07:37 639233266521568229
19 ms 63.250.38.233
22 2026-08-26 07:20 639233256081047431
35 ms 63.250.38.233
21 2026-08-26 06:26 639233223620132921
20 ms 63.250.38.233
20 2026-08-26 06:09 639233213287814244
22 ms 63.250.38.233
19 2026-08-26 05:51 639233202925983161
18 ms 63.250.38.233
18 2026-08-26 05:34 639233192644780696
18 ms 63.250.38.233
17 2026-08-26 05:17 639233182401183833
36 ms 63.250.38.233
16 2026-08-26 05:00 639233172074181051
29 ms 63.250.38.233
15 2026-08-26 04:43 639233161808421455
2093 ms 63.250.38.233
14 2026-08-26 04:25 639233151357344052
18 ms 63.250.38.233
13 2026-08-26 04:08 639233141034116946
2083 ms 63.250.38.233
12 2026-08-26 03:51 639233130828334142
22 ms 63.250.38.233
11 2026-08-26 03:34 639233120373450007
52 ms 63.250.38.233
10 2026-08-26 03:17 639233110066216193
27 ms 63.250.38.233
9 2026-08-26 02:23 639233078065410564
67 ms 63.250.38.233
8 2026-08-26 02:06 639233067787457832
26 ms 63.250.38.233
7 2026-08-26 01:49 639233057501801162
20 ms 63.250.38.233
6 2026-08-26 01:32 639233047089431703
103 ms 63.250.38.233
5 2026-08-26 01:15 639233036754790688
49 ms 63.250.38.233
4 2026-08-26 00:57 639233026412602472
7 ms 63.250.38.233
3 2026-08-26 00:40 639233016064066127
40 ms 63.250.38.233
2 2026-08-26 00:23 639233005922655772
37 ms 63.250.38.233
1 2026-08-26 00:06 639232995672256907
10 ms 63.250.38.233