DNS response history for ns11.dnshfe.com

ns11.dnshfe.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 36 DNS check records, 36 successful responses, 0 failed responses, and 191 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 ns11.dnshfe.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

191 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

62.138.16.229

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 ns11.dnshfe.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
36 2026-08-26 12:01 639233424567558554
44 ms 62.138.16.229
35 2026-08-26 11:44 639233414056832719
16 ms 62.138.16.229
34 2026-08-26 11:26 639233403515141099
17 ms 62.138.16.229
33 2026-08-26 10:32 639233370841350248
8 ms 62.138.16.229
32 2026-08-26 10:14 639233360361507238
25 ms 62.138.16.229
31 2026-08-26 09:57 639233350067824371
16 ms 62.138.16.229
30 2026-08-26 09:40 639233339545274518
22 ms 62.138.16.229
29 2026-08-26 09:22 639233329214918079
31 ms 62.138.16.229
28 2026-08-26 09:05 639233318749762337
13 ms 62.138.16.229
27 2026-08-26 08:48 639233308387917838
47 ms 62.138.16.229
26 2026-08-26 08:30 639233297961740122
34 ms 62.138.16.229
25 2026-08-26 08:13 639233287487159094
16 ms 62.138.16.229
24 2026-08-26 07:55 639233276995531707
47 ms 62.138.16.229
23 2026-08-26 07:38 639233266521568229
2019 ms 62.138.16.229
22 2026-08-26 07:21 639233256081047431
32 ms 62.138.16.229
21 2026-08-26 06:26 639233223620132921
26 ms 62.138.16.229
20 2026-08-26 06:09 639233213287814244
19 ms 62.138.16.229
19 2026-08-26 05:52 639233202925983161
33 ms 62.138.16.229
18 2026-08-26 05:35 639233192644780696
36 ms 62.138.16.229
17 2026-08-26 05:18 639233182401183833
76 ms 62.138.16.229
16 2026-08-26 05:00 639233172074181051
24 ms 62.138.16.229
15 2026-08-26 04:43 639233161808421455
13 ms 62.138.16.229
14 2026-08-26 04:26 639233151357344052
9 ms 62.138.16.229
13 2026-08-26 04:09 639233141034116946
7 ms 62.138.16.229
12 2026-08-26 03:52 639233130828334142
15 ms 62.138.16.229
11 2026-08-26 03:34 639233120373450007
2028 ms 62.138.16.229
10 2026-08-26 03:17 639233110066216193
5 ms 62.138.16.229
9 2026-08-26 02:24 639233078065410564
41 ms 62.138.16.229
8 2026-08-26 02:07 639233067787457832
7 ms 62.138.16.229
7 2026-08-26 01:50 639233057501801162
2039 ms 62.138.16.229
6 2026-08-26 01:32 639233047089431703
9 ms 62.138.16.229
5 2026-08-26 01:15 639233036754790688
22 ms 62.138.16.229
4 2026-08-26 00:58 639233026412602472
12 ms 62.138.16.229
3 2026-08-26 00:40 639233016064066127
19 ms 62.138.16.229
2 2026-08-26 00:24 639233005922655772
25 ms 62.138.16.229
1 2026-08-26 00:06 639232995672256907
40 ms 62.138.16.229