DNS response history for ns1.bisneros.pro

ns1.bisneros.pro 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 34 DNS check records, 34 successful responses, 0 failed responses, and 452 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.bisneros.pro.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

452 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.208.184.120

Most recently resolved hosting IP on selected date

Successful Responses

34

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.bisneros.pro

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
34 2026-08-26 11:35 639233403515141099
659 ms 74.208.184.120
33 2026-08-26 10:41 639233370841350248
323 ms 74.208.184.120
32 2026-08-26 10:23 639233360361507238
2008 ms 74.208.184.120
31 2026-08-26 10:06 639233350067824371
8 ms 74.208.184.120
30 2026-08-26 09:49 639233339545274518
2020 ms 74.208.184.120
29 2026-08-26 09:31 639233329214918079
10 ms 74.208.184.120
28 2026-08-26 09:14 639233318749762337
30 ms 74.208.184.120
27 2026-08-26 08:57 639233308387917838
526 ms 74.208.184.120
26 2026-08-26 08:39 639233297961740122
134 ms 74.208.184.120
25 2026-08-26 08:22 639233287487159094
544 ms 74.208.184.120
24 2026-08-26 08:05 639233276995531707
150 ms 74.208.184.120
23 2026-08-26 07:47 639233266521568229
332 ms 74.208.184.120
22 2026-08-26 07:29 639233256081047431
31 ms 74.208.184.120
21 2026-08-26 06:36 639233223620132921
205 ms 74.208.184.120
20 2026-08-26 06:18 639233213287814244
536 ms 74.208.184.120
19 2026-08-26 06:01 639233202925983161
569 ms 74.208.184.120
18 2026-08-26 05:44 639233192644780696
439 ms 74.208.184.120
17 2026-08-26 05:27 639233182401183833
411 ms 74.208.184.120
16 2026-08-26 05:10 639233172074181051
309 ms 74.208.184.120
15 2026-08-26 04:52 639233161808421455
336 ms 74.208.184.120
14 2026-08-26 04:35 639233151357344052
453 ms 74.208.184.120
13 2026-08-26 04:18 639233141034116946
531 ms 74.208.184.120
12 2026-08-26 04:01 639233130828334142
2210 ms 74.208.184.120
11 2026-08-26 03:43 639233120373450007
122 ms 74.208.184.120
10 2026-08-26 03:26 639233110066216193
130 ms 74.208.184.120
9 2026-08-26 02:33 639233078065410564
432 ms 74.208.184.120
8 2026-08-26 02:16 639233067787457832
124 ms 74.208.184.120
7 2026-08-26 01:58 639233057501801162
155 ms 74.208.184.120
6 2026-08-26 01:41 639233047089431703
433 ms 74.208.184.120
5 2026-08-26 01:24 639233036754790688
719 ms 74.208.184.120
4 2026-08-26 01:07 639233026412602472
122 ms 74.208.184.120
3 2026-08-26 00:49 639233016064066127
7 ms 74.208.184.120
2 2026-08-26 00:32 639233005922655772
16 ms 74.208.184.120
1 2026-08-26 00:15 639232995672256907
338 ms 74.208.184.120