DNS response history for ns2.yahuitl.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

253 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

201.130.4.164

Most recently resolved hosting IP on selected date

Successful Responses

32

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.yahuitl.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
32 2026-08-25 11:30 639232535349285207
161 ms 201.130.4.164
31 2026-08-25 11:12 639232524938080723
336 ms 201.130.4.164
30 2026-08-25 10:18 639232492740373468
333 ms 201.130.4.164
29 2026-08-25 10:01 639232482235303141
344 ms 201.130.4.164
28 2026-08-25 09:44 639232471861770303
170 ms 201.130.4.164
27 2026-08-25 09:26 639232461630217327
335 ms 201.130.4.164
26 2026-08-25 09:09 639232451282965990
161 ms 201.130.4.164
25 2026-08-25 08:52 639232440814614938
335 ms 201.130.4.164
24 2026-08-25 08:35 639232430410720425
345 ms 201.130.4.164
23 2026-08-25 08:17 639232420003096185
237 ms 201.130.4.164
22 2026-08-25 08:00 639232409467287444
349 ms 201.130.4.164
21 2026-08-25 07:42 639232399077195997
334 ms 201.130.4.164
20 2026-08-25 07:25 639232388731528337
337 ms 201.130.4.164
19 2026-08-25 07:08 639232378288598612
350 ms 201.130.4.164
18 2026-08-25 06:14 639232346196373643
4 ms 201.130.4.164
17 2026-08-25 05:57 639232336112370741
5 ms 201.130.4.164
16 2026-08-25 05:41 639232326146508970
337 ms 201.130.4.164
15 2026-08-25 05:24 639232316189381720
3 ms 201.130.4.164
14 2026-08-25 05:07 639232306217998913
5 ms 201.130.4.164
13 2026-08-25 04:51 639232296255744174
212 ms 201.130.4.164
12 2026-08-25 04:34 639232286095760789
335 ms 201.130.4.164
11 2026-08-25 04:17 639232276086186273
335 ms 201.130.4.164
10 2026-08-25 04:00 639232265900986425
351 ms 201.130.4.164
9 2026-08-25 03:43 639232255723518075
333 ms 201.130.4.164
8 2026-08-25 03:26 639232245484452890
335 ms 201.130.4.164
7 2026-08-25 03:09 639232235157175331
335 ms 201.130.4.164
6 2026-08-25 02:16 639232203197189095
335 ms 201.130.4.164
5 2026-08-25 01:59 639232192844564298
13 ms 201.130.4.164
4 2026-08-25 01:41 639232182496008942
188 ms 201.130.4.164
3 2026-08-25 01:24 639232172197053132
172 ms 201.130.4.164
2 2026-08-25 00:31 639232140250307418
330 ms 201.130.4.164
1 2026-08-25 00:14 639232129927860324
338 ms 201.130.4.164