DNS response history for ns2.s3med.com.br

ns2.s3med.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 388 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.s3med.com.br.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

388 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.214.77.236

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-08-26 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
35 2026-08-26 11:37 639233403515141099
165 ms 162.214.77.236
34 2026-08-26 10:42 639233370841350248
326 ms 162.214.77.236
33 2026-08-26 10:25 639233360361507238
329 ms 162.214.77.236
32 2026-08-26 10:08 639233350067824371
162 ms 162.214.77.236
31 2026-08-26 09:51 639233339545274518
2156 ms 162.214.77.236
30 2026-08-26 09:33 639233329214918079
158 ms 162.214.77.236
29 2026-08-26 09:16 639233318749762337
173 ms 162.214.77.236
28 2026-08-26 08:58 639233308387917838
7 ms 162.214.77.236
27 2026-08-26 08:41 639233297961740122
2010 ms 162.214.77.236
26 2026-08-26 08:24 639233287487159094
363 ms 162.214.77.236
25 2026-08-26 08:06 639233276995531707
357 ms 162.214.77.236
24 2026-08-26 07:49 639233266521568229
2683 ms 162.214.77.236
23 2026-08-26 07:31 639233256081047431
160 ms 162.214.77.236
22 2026-08-26 06:37 639233223620132921
172 ms 162.214.77.236
21 2026-08-26 06:20 639233213287814244
165 ms 162.214.77.236
20 2026-08-26 06:03 639233202925983161
241 ms 162.214.77.236
19 2026-08-26 05:45 639233192644780696
164 ms 162.214.77.236
18 2026-08-26 05:28 639233182401183833
335 ms 162.214.77.236
17 2026-08-26 05:11 639233172074181051
154 ms 162.214.77.236
16 2026-08-26 04:54 639233161808421455
493 ms 162.214.77.236
15 2026-08-26 04:37 639233151357344052
4 ms 162.214.77.236
14 2026-08-26 04:19 639233141034116946
354 ms 162.214.77.236
13 2026-08-26 04:02 639233130828334142
348 ms 162.214.77.236
12 2026-08-26 03:45 639233120373450007
159 ms 162.214.77.236
11 2026-08-26 03:28 639233110066216193
5 ms 162.214.77.236
10 2026-08-26 02:35 639233078065410564
3 ms 162.214.77.236
9 2026-08-26 02:17 639233067787457832
157 ms 162.214.77.236
8 2026-08-26 02:00 639233057501801162
173 ms 162.214.77.236
7 2026-08-26 01:43 639233047089431703
159 ms 162.214.77.236
6 2026-08-26 01:26 639233036754790688
315 ms 162.214.77.236
5 2026-08-26 01:09 639233026412602472
3 ms 162.214.77.236
4 2026-08-26 00:51 639233016064066127
158 ms 162.214.77.236
3 2026-08-26 00:34 639233005922655772
315 ms 162.214.77.236
2 2026-08-26 00:17 639232995672256907
338 ms 162.214.77.236
1 2026-08-26 00:00 639232985300872416
319 ms 162.214.77.236