DNS response history for ns2.ansiedadno.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

201 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.56.59.125

Most recently resolved hosting IP on selected date

Successful Responses

30

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.ansiedadno.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
30 2026-08-26 09:39 639233339545274518
39 ms 5.56.59.125
29 2026-08-26 09:22 639233329214918079
29 ms 5.56.59.125
28 2026-08-26 09:05 639233318749762337
67 ms 5.56.59.125
27 2026-08-26 08:47 639233308387917838
95 ms 5.56.59.125
26 2026-08-26 08:30 639233297961740122
85 ms 5.56.59.125
25 2026-08-26 08:12 639233287487159094
75 ms 5.56.59.125
24 2026-08-26 07:55 639233276995531707
45 ms 5.56.59.125
23 2026-08-26 07:38 639233266521568229
98 ms 5.56.59.125
22 2026-08-26 07:20 639233256081047431
68 ms 5.56.59.125
21 2026-08-26 06:26 639233223620132921
110 ms 5.56.59.125
20 2026-08-26 06:09 639233213287814244
84 ms 5.56.59.125
19 2026-08-26 05:52 639233202925983161
12 ms 5.56.59.125
18 2026-08-26 05:34 639233192644780696
76 ms 5.56.59.125
17 2026-08-26 05:17 639233182401183833
8 ms 5.56.59.125
16 2026-08-26 05:00 639233172074181051
11 ms 5.56.59.125
15 2026-08-26 04:43 639233161808421455
152 ms 5.56.59.125
14 2026-08-26 04:26 639233151357344052
73 ms 5.56.59.125
13 2026-08-26 04:08 639233141034116946
55 ms 5.56.59.125
12 2026-08-26 03:51 639233130828334142
3 ms 5.56.59.125
11 2026-08-26 03:34 639233120373450007
62 ms 5.56.59.125
10 2026-08-26 03:17 639233110066216193
76 ms 5.56.59.125
9 2026-08-26 02:23 639233078065410564
2073 ms 5.56.59.125
8 2026-08-26 02:06 639233067787457832
67 ms 5.56.59.125
7 2026-08-26 01:49 639233057501801162
21 ms 5.56.59.125
6 2026-08-26 01:32 639233047089431703
106 ms 5.56.59.125
5 2026-08-26 01:15 639233036754790688
80 ms 5.56.59.125
4 2026-08-26 00:57 639233026412602472
127 ms 5.56.59.125
3 2026-08-26 00:40 639233016064066127
2063 ms 5.56.59.125
2 2026-08-26 00:23 639233005922655772
89 ms 5.56.59.125
1 2026-08-26 00:06 639232995672256907
70 ms 5.56.59.125