DNS response history for ns2.fuzecore.com

ns2.fuzecore.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 29 DNS check records, 29 successful responses, 0 failed responses, and 3116 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.fuzecore.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

3116 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.38.173.171

Most recently resolved hosting IP on selected date

Successful Responses

29

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.fuzecore.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
29 2026-08-26 09:21 639233318749762337
4171 ms 209.38.173.171
28 2026-08-26 09:04 639233308387917838
3888 ms 209.38.173.171
27 2026-08-26 08:46 639233297961740122
2166 ms 209.38.173.171
26 2026-08-26 08:29 639233287487159094
4185 ms 209.38.173.171
25 2026-08-26 08:11 639233276995531707
4184 ms 209.38.173.171
24 2026-08-26 07:54 639233266521568229
4185 ms 209.38.173.171
23 2026-08-26 07:36 639233256081047431
4161 ms 209.38.173.171
22 2026-08-26 06:42 639233223620132921
2197 ms 209.38.173.171
21 2026-08-26 06:25 639233213287814244
2176 ms 209.38.173.171
20 2026-08-26 06:08 639233202925983161
4172 ms 209.38.173.171
19 2026-08-26 05:51 639233192644780696
4170 ms 209.38.173.171
18 2026-08-26 05:33 639233182401183833
2275 ms 209.38.173.171
17 2026-08-26 05:16 639233172074181051
2169 ms 209.38.173.171
16 2026-08-26 04:59 639233161808421455
2165 ms 209.38.173.171
15 2026-08-26 04:42 639233151357344052
184 ms 209.38.173.171
14 2026-08-26 04:25 639233141034116946
4165 ms 209.38.173.171
13 2026-08-26 04:07 639233130828334142
4173 ms 209.38.173.171
12 2026-08-26 03:50 639233120373450007
1831 ms 209.38.173.171
11 2026-08-26 03:33 639233110066216193
4160 ms 209.38.173.171
10 2026-08-26 02:40 639233078065410564
4165 ms 209.38.173.171
9 2026-08-26 02:22 639233067787457832
2033 ms 209.38.173.171
8 2026-08-26 02:05 639233057501801162
2172 ms 209.38.173.171
7 2026-08-26 01:48 639233047089431703
4163 ms 209.38.173.171
6 2026-08-26 01:31 639233036754790688
2183 ms 209.38.173.171
5 2026-08-26 01:14 639233026412602472
4173 ms 209.38.173.171
4 2026-08-26 00:56 639233016064066127
4172 ms 209.38.173.171
3 2026-08-26 00:39 639233005922655772
2164 ms 209.38.173.171
2 2026-08-26 00:22 639232995672256907
2163 ms 209.38.173.171
1 2026-08-26 00:05 639232985300872416
2189 ms 209.38.173.171