DNS response history for ns1.7binario.com

ns1.7binario.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 261 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.7binario.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

261 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

152.53.236.69

Most recently resolved hosting IP on selected date

Successful Responses

28

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

Showing DNS history for 2026-08-25 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
28 2026-08-25 09:38 639232471861770303
72 ms 152.53.236.69
27 2026-08-25 09:21 639232461630217327
49 ms 152.53.236.69
26 2026-08-25 09:03 639232451282965990
41 ms 152.53.236.69
25 2026-08-25 08:46 639232440814614938
19 ms 152.53.236.69
24 2026-08-25 08:29 639232430410720425
155 ms 152.53.236.69
23 2026-08-25 08:11 639232420003096185
14 ms 152.53.236.69
22 2026-08-25 07:54 639232409467287444
32 ms 152.53.236.69
21 2026-08-25 07:36 639232399077195997
43 ms 152.53.236.69
20 2026-08-25 07:19 639232388731528337
32 ms 152.53.236.69
19 2026-08-25 07:02 639232378288598612
65 ms 152.53.236.69
18 2026-08-25 06:08 639232346196373643
38 ms 152.53.236.69
17 2026-08-25 05:51 639232336112370741
17 ms 152.53.236.69
16 2026-08-25 05:35 639232326146508970
84 ms 152.53.236.69
15 2026-08-25 05:18 639232316189381720
35 ms 152.53.236.69
14 2026-08-25 05:02 639232306217998913
2026 ms 152.53.236.69
13 2026-08-25 04:45 639232296255744174
31 ms 152.53.236.69
12 2026-08-25 04:28 639232286095760789
2021 ms 152.53.236.69
11 2026-08-25 04:11 639232276086186273
2028 ms 152.53.236.69
10 2026-08-25 03:54 639232265900986425
146 ms 152.53.236.69
9 2026-08-25 03:37 639232255723518075
56 ms 152.53.236.69
8 2026-08-25 03:20 639232245484452890
36 ms 152.53.236.69
7 2026-08-25 03:03 639232235157175331
32 ms 152.53.236.69
6 2026-08-25 02:10 639232203197189095
41 ms 152.53.236.69
5 2026-08-25 01:53 639232192844564298
61 ms 152.53.236.69
4 2026-08-25 01:36 639232182496008942
19 ms 152.53.236.69
3 2026-08-25 01:18 639232172197053132
24 ms 152.53.236.69
2 2026-08-25 00:25 639232140250307418
38 ms 152.53.236.69
1 2026-08-25 00:08 639232129927860324
43 ms 152.53.236.69