DNS response history for ns1.hghctp.com

ns1.hghctp.com 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 30 DNS check records, 30 successful responses, 0 failed responses, and 210 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.hghctp.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

210 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.160.146.160

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns1.hghctp.com

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
30 2026-08-26 09:45 639233339545274518
228 ms 108.160.146.160
29 2026-08-26 09:27 639233329214918079
133 ms 108.160.146.160
28 2026-08-26 09:10 639233318749762337
125 ms 108.160.146.160
27 2026-08-26 08:53 639233308387917838
107 ms 108.160.146.160
26 2026-08-26 08:35 639233297961740122
34 ms 108.160.146.160
25 2026-08-26 08:18 639233287487159094
243 ms 108.160.146.160
24 2026-08-26 08:00 639233276995531707
157 ms 108.160.146.160
23 2026-08-26 07:43 639233266521568229
244 ms 108.160.146.160
22 2026-08-26 07:25 639233256081047431
157 ms 108.160.146.160
21 2026-08-26 06:31 639233223620132921
2139 ms 108.160.146.160
20 2026-08-26 06:14 639233213287814244
103 ms 108.160.146.160
19 2026-08-26 05:57 639233202925983161
9 ms 108.160.146.160
18 2026-08-26 05:40 639233192644780696
41 ms 108.160.146.160
17 2026-08-26 05:22 639233182401183833
121 ms 108.160.146.160
16 2026-08-26 05:05 639233172074181051
121 ms 108.160.146.160
15 2026-08-26 04:48 639233161808421455
27 ms 108.160.146.160
14 2026-08-26 04:31 639233151357344052
8 ms 108.160.146.160
13 2026-08-26 04:14 639233141034116946
135 ms 108.160.146.160
12 2026-08-26 03:57 639233130828334142
114 ms 108.160.146.160
11 2026-08-26 03:39 639233120373450007
121 ms 108.160.146.160
10 2026-08-26 03:22 639233110066216193
219 ms 108.160.146.160
9 2026-08-26 02:29 639233078065410564
224 ms 108.160.146.160
8 2026-08-26 02:12 639233067787457832
120 ms 108.160.146.160
7 2026-08-26 01:55 639233057501801162
116 ms 108.160.146.160
6 2026-08-26 01:37 639233047089431703
223 ms 108.160.146.160
5 2026-08-26 01:20 639233036754790688
128 ms 108.160.146.160
4 2026-08-26 01:03 639233026412602472
222 ms 108.160.146.160
3 2026-08-26 00:45 639233016064066127
221 ms 108.160.146.160
2 2026-08-26 00:28 639233005922655772
220 ms 108.160.146.160
1 2026-08-26 00:11 639232995672256907
251 ms 108.160.146.160