DNS response history for ns2.poken.com.br

ns2.poken.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 455 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.poken.com.br.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

455 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

177.53.143.49

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.poken.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:31 639232535349285207
362 ms 177.53.143.49
31 2026-08-25 11:14 639232524938080723
8 ms 177.53.143.49
30 2026-08-25 10:20 639232492740373468
177 ms 177.53.143.49
29 2026-08-25 10:03 639232482235303141
359 ms 177.53.143.49
28 2026-08-25 09:45 639232471861770303
365 ms 177.53.143.49
27 2026-08-25 09:28 639232461630217327
2017 ms 177.53.143.49
26 2026-08-25 09:11 639232451282965990
378 ms 177.53.143.49
25 2026-08-25 08:53 639232440814614938
365 ms 177.53.143.49
24 2026-08-25 08:36 639232430410720425
221 ms 177.53.143.49
23 2026-08-25 08:19 639232420003096185
2213 ms 177.53.143.49
22 2026-08-25 08:01 639232409467287444
174 ms 177.53.143.49
21 2026-08-25 07:44 639232399077195997
175 ms 177.53.143.49
20 2026-08-25 07:27 639232388731528337
350 ms 177.53.143.49
19 2026-08-25 07:09 639232378288598612
175 ms 177.53.143.49
18 2026-08-25 06:15 639232346196373643
359 ms 177.53.143.49
17 2026-08-25 05:59 639232336112370741
361 ms 177.53.143.49
16 2026-08-25 05:42 639232326146508970
364 ms 177.53.143.49
15 2026-08-25 05:25 639232316189381720
355 ms 177.53.143.49
14 2026-08-25 05:09 639232306217998913
9 ms 177.53.143.49
13 2026-08-25 04:52 639232296255744174
347 ms 177.53.143.49
12 2026-08-25 04:35 639232286095760789
222 ms 177.53.143.49
11 2026-08-25 04:18 639232276086186273
174 ms 177.53.143.49
10 2026-08-25 04:02 639232265900986425
355 ms 177.53.143.49
9 2026-08-25 03:45 639232255723518075
2198 ms 177.53.143.49
8 2026-08-25 03:28 639232245484452890
354 ms 177.53.143.49
7 2026-08-25 03:11 639232235157175331
358 ms 177.53.143.49
6 2026-08-25 02:17 639232203197189095
360 ms 177.53.143.49
5 2026-08-25 02:00 639232192844564298
178 ms 177.53.143.49
4 2026-08-25 01:43 639232182496008942
176 ms 177.53.143.49
3 2026-08-25 01:26 639232172197053132
174 ms 177.53.143.49
2 2026-08-25 00:32 639232140250307418
530 ms 177.53.143.49
1 2026-08-25 00:15 639232129927860324
358 ms 177.53.143.49