DNS response history for ns2.hattech.com.br

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

34

Historical checks stored for this nameserver on selected date

Average Latency

385 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.155.121

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.hattech.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
34 2026-08-26 10:44 639233370841350248
174 ms 162.240.155.121
33 2026-08-26 10:27 639233360361507238
367 ms 162.240.155.121
32 2026-08-26 10:09 639233350067824371
360 ms 162.240.155.121
31 2026-08-26 09:52 639233339545274518
175 ms 162.240.155.121
30 2026-08-26 09:35 639233329214918079
361 ms 162.240.155.121
29 2026-08-26 09:17 639233318749762337
395 ms 162.240.155.121
28 2026-08-26 09:00 639233308387917838
385 ms 162.240.155.121
27 2026-08-26 08:43 639233297961740122
391 ms 162.240.155.121
26 2026-08-26 08:25 639233287487159094
1086 ms 162.240.155.121
25 2026-08-26 08:08 639233276995531707
192 ms 162.240.155.121
24 2026-08-26 07:50 639233266521568229
380 ms 162.240.155.121
23 2026-08-26 07:33 639233256081047431
364 ms 162.240.155.121
22 2026-08-26 06:39 639233223620132921
174 ms 162.240.155.121
21 2026-08-26 06:22 639233213287814244
393 ms 162.240.155.121
20 2026-08-26 06:04 639233202925983161
348 ms 162.240.155.121
19 2026-08-26 05:47 639233192644780696
176 ms 162.240.155.121
18 2026-08-26 05:30 639233182401183833
176 ms 162.240.155.121
17 2026-08-26 05:13 639233172074181051
391 ms 162.240.155.121
16 2026-08-26 04:56 639233161808421455
531 ms 162.240.155.121
15 2026-08-26 04:39 639233151357344052
369 ms 162.240.155.121
14 2026-08-26 04:21 639233141034116946
363 ms 162.240.155.121
13 2026-08-26 04:04 639233130828334142
182 ms 162.240.155.121
12 2026-08-26 03:47 639233120373450007
363 ms 162.240.155.121
11 2026-08-26 03:29 639233110066216193
361 ms 162.240.155.121
10 2026-08-26 02:36 639233078065410564
3 ms 162.240.155.121
9 2026-08-26 02:19 639233067787457832
368 ms 162.240.155.121
8 2026-08-26 02:02 639233057501801162
351 ms 162.240.155.121
7 2026-08-26 01:45 639233047089431703
350 ms 162.240.155.121
6 2026-08-26 01:27 639233036754790688
507 ms 162.240.155.121
5 2026-08-26 01:10 639233026412602472
2178 ms 162.240.155.121
4 2026-08-26 00:53 639233016064066127
348 ms 162.240.155.121
3 2026-08-26 00:36 639233005922655772
176 ms 162.240.155.121
2 2026-08-26 00:19 639232995672256907
176 ms 162.240.155.121
1 2026-08-26 00:02 639232985300872416
176 ms 162.240.155.121