DNS response history for ns2.daycred.com.br

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

34

Historical checks stored for this nameserver on selected date

Average Latency

290 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

201.56.78.69

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 ns2.daycred.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
34 2026-08-25 11:59 639232556111768563
40 ms 201.56.78.69
33 2026-08-25 11:42 639232545839529039
31 ms 201.56.78.69
32 2026-08-25 11:24 639232535349285207
68 ms 201.56.78.69
31 2026-08-25 11:07 639232524938080723
2026 ms 201.56.78.69
30 2026-08-25 10:13 639232492740373468
53 ms 201.56.78.69
29 2026-08-25 09:56 639232482235303141
54 ms 201.56.78.69
28 2026-08-25 09:38 639232471861770303
9 ms 201.56.78.69
27 2026-08-25 09:21 639232461630217327
74 ms 201.56.78.69
26 2026-08-25 09:04 639232451282965990
129 ms 201.56.78.69
25 2026-08-25 08:47 639232440814614938
418 ms 201.56.78.69
24 2026-08-25 08:29 639232430410720425
38 ms 201.56.78.69
23 2026-08-25 08:12 639232420003096185
9 ms 201.56.78.69
22 2026-08-25 07:55 639232409467287444
323 ms 201.56.78.69
21 2026-08-25 07:37 639232399077195997
26 ms 201.56.78.69
20 2026-08-25 07:20 639232388731528337
221 ms 201.56.78.69
19 2026-08-25 07:03 639232378288598612
56 ms 201.56.78.69
18 2026-08-25 06:09 639232346196373643
73 ms 201.56.78.69
17 2026-08-25 05:52 639232336112370741
471 ms 201.56.78.69
16 2026-08-25 05:36 639232326146508970
409 ms 201.56.78.69
15 2026-08-25 05:19 639232316189381720
2017 ms 201.56.78.69
14 2026-08-25 05:03 639232306217998913
21 ms 201.56.78.69
13 2026-08-25 04:46 639232296255744174
15 ms 201.56.78.69
12 2026-08-25 04:29 639232286095760789
366 ms 201.56.78.69
11 2026-08-25 04:12 639232276086186273
362 ms 201.56.78.69
10 2026-08-25 03:55 639232265900986425
32 ms 201.56.78.69
9 2026-08-25 03:38 639232255723518075
29 ms 201.56.78.69
8 2026-08-25 03:21 639232245484452890
64 ms 201.56.78.69
7 2026-08-25 03:04 639232235157175331
287 ms 201.56.78.69
6 2026-08-25 02:11 639232203197189095
26 ms 201.56.78.69
5 2026-08-25 01:54 639232192844564298
21 ms 201.56.78.69
4 2026-08-25 01:36 639232182496008942
25 ms 201.56.78.69
3 2026-08-25 01:19 639232172197053132
2011 ms 201.56.78.69
2 2026-08-25 00:26 639232140250307418
28 ms 201.56.78.69
1 2026-08-25 00:09 639232129927860324
45 ms 201.56.78.69