DNS response history for ns1.hhteam.pro

ns1.hhteam.pro 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 37 DNS check records, 34 successful responses, 3 failed responses, and 2508 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 ns1.hhteam.pro.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

2508 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.222.24.253

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

3

Checks with no response or no returned latency

Failure Rate

8%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.hhteam.pro

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
37 2026-08-26 12:17 639233424567558554
116 ms 51.222.24.253
36 2026-08-26 11:59 639233414056832719
2570 ms 51.222.24.253
35 2026-08-26 11:42 639233403515141099
3726 ms 51.222.24.253
34 2026-08-26 10:47 639233370841350248
4109 ms 51.222.24.253
33 2026-08-26 10:30 639233360361507238
2011 ms 51.222.24.253
32 2026-08-26 10:13 639233350067824371
2107 ms 51.222.24.253
31 2026-08-26 09:55 639233339545274518
3707 ms 51.222.24.253
30 2026-08-26 09:38 639233329214918079
3948 ms 51.222.24.253
29 2026-08-26 09:21 639233318749762337
3875 ms 51.222.24.253
28 2026-08-26 09:03 639233308387917838
111 ms 51.222.24.253
27 2026-08-26 08:46 639233297961740122
3611 ms 51.222.24.253
26 2026-08-26 08:28 639233287487159094
3831 ms 51.222.24.253
25 2026-08-26 08:11 639233276995531707
4 ms 51.222.24.253
24 2026-08-26 07:54 639233266521568229
4004 ms 51.222.24.253
23 2026-08-26 07:36 639233256081047431
-
22 2026-08-26 06:42 639233223620132921
3701 ms 51.222.24.253
21 2026-08-26 06:25 639233213287814244
108 ms 51.222.24.253
20 2026-08-26 06:07 639233202925983161
-
19 2026-08-26 05:50 639233192644780696
4 ms 51.222.24.253
18 2026-08-26 05:33 639233182401183833
4587 ms 51.222.24.253
17 2026-08-26 05:16 639233172074181051
4008 ms 51.222.24.253
16 2026-08-26 04:59 639233161808421455
2035 ms 51.222.24.253
15 2026-08-26 04:42 639233151357344052
3699 ms 51.222.24.253
14 2026-08-26 04:24 639233141034116946
-
13 2026-08-26 04:07 639233130828334142
2103 ms 51.222.24.253
12 2026-08-26 03:50 639233120373450007
110 ms 51.222.24.253
11 2026-08-26 03:32 639233110066216193
3719 ms 51.222.24.253
10 2026-08-26 02:39 639233078065410564
3697 ms 51.222.24.253
9 2026-08-26 02:22 639233067787457832
3 ms 51.222.24.253
8 2026-08-26 02:05 639233057501801162
2 ms 51.222.24.253
7 2026-08-26 01:48 639233047089431703
3715 ms 51.222.24.253
6 2026-08-26 01:30 639233036754790688
3619 ms 51.222.24.253
5 2026-08-26 01:13 639233026412602472
2113 ms 51.222.24.253
4 2026-08-26 00:56 639233016064066127
3952 ms 51.222.24.253
3 2026-08-26 00:39 639233005922655772
2007 ms 51.222.24.253
2 2026-08-26 00:22 639232995672256907
2147 ms 51.222.24.253
1 2026-08-26 00:05 639232985300872416
2197 ms 51.222.24.253