DNS response history for ns2.fundacionhugozarate.com

ns2.fundacionhugozarate.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 31 DNS check records, 31 successful responses, 0 failed responses, and 555 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 ns2.fundacionhugozarate.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

555 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

194.163.130.153

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns2.fundacionhugozarate.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
31 2026-08-26 09:52 639233339545274518
3024 ms 194.163.130.153
30 2026-08-26 09:35 639233329214918079
103 ms 194.163.130.153
29 2026-08-26 09:17 639233318749762337
65 ms 194.163.130.153
28 2026-08-26 09:00 639233308387917838
187 ms 194.163.130.153
27 2026-08-26 08:43 639233297961740122
346 ms 194.163.130.153
26 2026-08-26 08:25 639233287487159094
785 ms 194.163.130.153
25 2026-08-26 08:08 639233276995531707
495 ms 194.163.130.153
24 2026-08-26 07:50 639233266521568229
460 ms 194.163.130.153
23 2026-08-26 07:33 639233256081047431
111 ms 194.163.130.153
22 2026-08-26 06:39 639233223620132921
632 ms 194.163.130.153
21 2026-08-26 06:22 639233213287814244
4 ms 194.163.130.153
20 2026-08-26 06:04 639233202925983161
493 ms 194.163.130.153
19 2026-08-26 05:47 639233192644780696
1629 ms 194.163.130.153
18 2026-08-26 05:30 639233182401183833
413 ms 194.163.130.153
17 2026-08-26 05:13 639233172074181051
205 ms 194.163.130.153
16 2026-08-26 04:56 639233161808421455
504 ms 194.163.130.153
15 2026-08-26 04:39 639233151357344052
443 ms 194.163.130.153
14 2026-08-26 04:21 639233141034116946
376 ms 194.163.130.153
13 2026-08-26 04:04 639233130828334142
179 ms 194.163.130.153
12 2026-08-26 03:47 639233120373450007
15 ms 194.163.130.153
11 2026-08-26 03:29 639233110066216193
147 ms 194.163.130.153
10 2026-08-26 02:36 639233078065410564
127 ms 194.163.130.153
9 2026-08-26 02:19 639233067787457832
517 ms 194.163.130.153
8 2026-08-26 02:02 639233057501801162
394 ms 194.163.130.153
7 2026-08-26 01:45 639233047089431703
74 ms 194.163.130.153
6 2026-08-26 01:27 639233036754790688
19 ms 194.163.130.153
5 2026-08-26 01:10 639233026412602472
1265 ms 194.163.130.153
4 2026-08-26 00:53 639233016064066127
2031 ms 194.163.130.153
3 2026-08-26 00:36 639233005922655772
265 ms 194.163.130.153
2 2026-08-26 00:19 639232995672256907
920 ms 194.163.130.153
1 2026-08-26 00:02 639232985300872416
969 ms 194.163.130.153