DNS response history for ns2.yaop.com.br

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

30

Historical checks stored for this nameserver on selected date

Average Latency

311 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.109.34.5

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.yaop.com.br

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
30 2026-08-25 10:19 639232492740373468
3 ms 208.109.34.5
29 2026-08-25 10:01 639232482235303141
3 ms 208.109.34.5
28 2026-08-25 09:44 639232471861770303
210 ms 208.109.34.5
27 2026-08-25 09:27 639232461630217327
158 ms 208.109.34.5
26 2026-08-25 09:10 639232451282965990
340 ms 208.109.34.5
25 2026-08-25 08:52 639232440814614938
351 ms 208.109.34.5
24 2026-08-25 08:35 639232430410720425
158 ms 208.109.34.5
23 2026-08-25 08:18 639232420003096185
156 ms 208.109.34.5
22 2026-08-25 08:00 639232409467287444
370 ms 208.109.34.5
21 2026-08-25 07:43 639232399077195997
2573 ms 208.109.34.5
20 2026-08-25 07:25 639232388731528337
340 ms 208.109.34.5
19 2026-08-25 07:08 639232378288598612
34 ms 208.109.34.5
18 2026-08-25 06:14 639232346196373643
343 ms 208.109.34.5
17 2026-08-25 05:57 639232336112370741
349 ms 208.109.34.5
16 2026-08-25 05:41 639232326146508970
337 ms 208.109.34.5
15 2026-08-25 05:24 639232316189381720
3 ms 208.109.34.5
14 2026-08-25 05:08 639232306217998913
308 ms 208.109.34.5
13 2026-08-25 04:51 639232296255744174
324 ms 208.109.34.5
12 2026-08-25 04:34 639232286095760789
5 ms 208.109.34.5
11 2026-08-25 04:17 639232276086186273
156 ms 208.109.34.5
10 2026-08-25 04:01 639232265900986425
344 ms 208.109.34.5
9 2026-08-25 03:44 639232255723518075
353 ms 208.109.34.5
8 2026-08-25 03:27 639232245484452890
263 ms 208.109.34.5
7 2026-08-25 03:09 639232235157175331
336 ms 208.109.34.5
6 2026-08-25 02:16 639232203197189095
347 ms 208.109.34.5
5 2026-08-25 01:59 639232192844564298
158 ms 208.109.34.5
4 2026-08-25 01:42 639232182496008942
160 ms 208.109.34.5
3 2026-08-25 01:24 639232172197053132
350 ms 208.109.34.5
2 2026-08-25 00:31 639232140250307418
354 ms 208.109.34.5
1 2026-08-25 00:14 639232129927860324
155 ms 208.109.34.5