DNS response history for ns2.treszero.com.br

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

32

Historical checks stored for this nameserver on selected date

Average Latency

181 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

188.166.104.225

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.treszero.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
32 2026-08-25 11:26 639232535349285207
68 ms 188.166.104.225
31 2026-08-25 11:09 639232524938080723
210 ms 188.166.104.225
30 2026-08-25 10:15 639232492740373468
54 ms 188.166.104.225
29 2026-08-25 09:58 639232482235303141
50 ms 188.166.104.225
28 2026-08-25 09:40 639232471861770303
53 ms 188.166.104.225
27 2026-08-25 09:23 639232461630217327
428 ms 188.166.104.225
26 2026-08-25 09:06 639232451282965990
19 ms 188.166.104.225
25 2026-08-25 08:48 639232440814614938
138 ms 188.166.104.225
24 2026-08-25 08:31 639232430410720425
2416 ms 188.166.104.225
23 2026-08-25 08:14 639232420003096185
52 ms 188.166.104.225
22 2026-08-25 07:56 639232409467287444
152 ms 188.166.104.225
21 2026-08-25 07:39 639232399077195997
52 ms 188.166.104.225
20 2026-08-25 07:22 639232388731528337
20 ms 188.166.104.225
19 2026-08-25 07:04 639232378288598612
65 ms 188.166.104.225
18 2026-08-25 06:11 639232346196373643
24 ms 188.166.104.225
17 2026-08-25 05:54 639232336112370741
181 ms 188.166.104.225
16 2026-08-25 05:37 639232326146508970
28 ms 188.166.104.225
15 2026-08-25 05:21 639232316189381720
259 ms 188.166.104.225
14 2026-08-25 05:04 639232306217998913
154 ms 188.166.104.225
13 2026-08-25 04:48 639232296255744174
533 ms 188.166.104.225
12 2026-08-25 04:31 639232286095760789
33 ms 188.166.104.225
11 2026-08-25 04:14 639232276086186273
45 ms 188.166.104.225
10 2026-08-25 03:57 639232265900986425
61 ms 188.166.104.225
9 2026-08-25 03:40 639232255723518075
27 ms 188.166.104.225
8 2026-08-25 03:23 639232245484452890
59 ms 188.166.104.225
7 2026-08-25 03:06 639232235157175331
38 ms 188.166.104.225
6 2026-08-25 02:13 639232203197189095
58 ms 188.166.104.225
5 2026-08-25 01:55 639232192844564298
215 ms 188.166.104.225
4 2026-08-25 01:38 639232182496008942
30 ms 188.166.104.225
3 2026-08-25 01:21 639232172197053132
161 ms 188.166.104.225
2 2026-08-25 00:27 639232140250307418
47 ms 188.166.104.225
1 2026-08-25 00:10 639232129927860324
64 ms 188.166.104.225