DNS response history for dns2.samplay.com.br

dns2.samplay.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 36 DNS check records, 36 successful responses, 0 failed responses, and 431 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 dns2.samplay.com.br.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

431 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

189.38.95.3

Most recently resolved hosting IP on selected date

Successful Responses

36

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 dns2.samplay.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
36 2026-08-25 12:40 639232576780683689
184 ms 189.38.95.3
35 2026-08-25 12:22 639232566381512620
342 ms 189.38.95.3
34 2026-08-25 12:05 639232556111768563
361 ms 189.38.95.3
33 2026-08-25 11:48 639232545839529039
392 ms 189.38.95.3
32 2026-08-25 11:31 639232535349285207
174 ms 189.38.95.3
31 2026-08-25 11:13 639232524938080723
353 ms 189.38.95.3
30 2026-08-25 10:20 639232492740373468
188 ms 189.38.95.3
29 2026-08-25 10:02 639232482235303141
174 ms 189.38.95.3
28 2026-08-25 09:45 639232471861770303
356 ms 189.38.95.3
27 2026-08-25 09:28 639232461630217327
176 ms 189.38.95.3
26 2026-08-25 09:10 639232451282965990
7 ms 189.38.95.3
25 2026-08-25 08:53 639232440814614938
357 ms 189.38.95.3
24 2026-08-25 08:36 639232430410720425
342 ms 189.38.95.3
23 2026-08-25 08:18 639232420003096185
318 ms 189.38.95.3
22 2026-08-25 08:01 639232409467287444
338 ms 189.38.95.3
21 2026-08-25 07:43 639232399077195997
184 ms 189.38.95.3
20 2026-08-25 07:26 639232388731528337
174 ms 189.38.95.3
19 2026-08-25 07:09 639232378288598612
373 ms 189.38.95.3
18 2026-08-25 06:15 639232346196373643
2181 ms 189.38.95.3
17 2026-08-25 05:58 639232336112370741
219 ms 189.38.95.3
16 2026-08-25 05:42 639232326146508970
345 ms 189.38.95.3
15 2026-08-25 05:25 639232316189381720
353 ms 189.38.95.3
14 2026-08-25 05:09 639232306217998913
353 ms 189.38.95.3
13 2026-08-25 04:52 639232296255744174
186 ms 189.38.95.3
12 2026-08-25 04:35 639232286095760789
171 ms 189.38.95.3
11 2026-08-25 04:18 639232276086186273
342 ms 189.38.95.3
10 2026-08-25 04:01 639232265900986425
341 ms 189.38.95.3
9 2026-08-25 03:45 639232255723518075
2203 ms 189.38.95.3
8 2026-08-25 03:27 639232245484452890
171 ms 189.38.95.3
7 2026-08-25 03:10 639232235157175331
359 ms 189.38.95.3
6 2026-08-25 02:17 639232203197189095
163 ms 189.38.95.3
5 2026-08-25 02:00 639232192844564298
2291 ms 189.38.95.3
4 2026-08-25 01:43 639232182496008942
175 ms 189.38.95.3
3 2026-08-25 01:25 639232172197053132
349 ms 189.38.95.3
2 2026-08-25 00:32 639232140250307418
345 ms 189.38.95.3
1 2026-08-25 00:15 639232129927860324
173 ms 189.38.95.3