DNS response history for ns3.nnncorps.com

ns3.nnncorps.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 708 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 ns3.nnncorps.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

708 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

68.186.41.118

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 ns3.nnncorps.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 11:57 639233414056832719
172 ms 68.186.41.118
35 2026-08-26 11:39 639233403515141099
563 ms 68.186.41.118
34 2026-08-26 10:45 639233370841350248
548 ms 68.186.41.118
33 2026-08-26 10:27 639233360361507238
180 ms 68.186.41.118
32 2026-08-26 10:10 639233350067824371
182 ms 68.186.41.118
31 2026-08-26 09:53 639233339545274518
1489 ms 68.186.41.118
30 2026-08-26 09:35 639233329214918079
189 ms 68.186.41.118
29 2026-08-26 09:18 639233318749762337
1051 ms 68.186.41.118
28 2026-08-26 09:01 639233308387917838
354 ms 68.186.41.118
27 2026-08-26 08:43 639233297961740122
553 ms 68.186.41.118
26 2026-08-26 08:26 639233287487159094
1248 ms 68.186.41.118
25 2026-08-26 08:08 639233276995531707
3854 ms 68.186.41.118
24 2026-08-26 07:51 639233266521568229
340 ms 68.186.41.118
23 2026-08-26 07:33 639233256081047431
816 ms 68.186.41.118
22 2026-08-26 06:39 639233223620132921
177 ms 68.186.41.118
21 2026-08-26 06:22 639233213287814244
3 ms 68.186.41.118
20 2026-08-26 06:05 639233202925983161
176 ms 68.186.41.118
19 2026-08-26 05:48 639233192644780696
173 ms 68.186.41.118
18 2026-08-26 05:30 639233182401183833
348 ms 68.186.41.118
17 2026-08-26 05:13 639233172074181051
729 ms 68.186.41.118
16 2026-08-26 04:56 639233161808421455
2281 ms 68.186.41.118
15 2026-08-26 04:39 639233151357344052
1111 ms 68.186.41.118
14 2026-08-26 04:22 639233141034116946
173 ms 68.186.41.118
13 2026-08-26 04:04 639233130828334142
529 ms 68.186.41.118
12 2026-08-26 03:47 639233120373450007
172 ms 68.186.41.118
11 2026-08-26 03:30 639233110066216193
2346 ms 68.186.41.118
10 2026-08-26 02:37 639233078065410564
692 ms 68.186.41.118
9 2026-08-26 02:20 639233067787457832
169 ms 68.186.41.118
8 2026-08-26 02:02 639233057501801162
377 ms 68.186.41.118
7 2026-08-26 01:45 639233047089431703
864 ms 68.186.41.118
6 2026-08-26 01:28 639233036754790688
347 ms 68.186.41.118
5 2026-08-26 01:11 639233026412602472
819 ms 68.186.41.118
4 2026-08-26 00:53 639233016064066127
737 ms 68.186.41.118
3 2026-08-26 00:36 639233005922655772
683 ms 68.186.41.118
2 2026-08-26 00:19 639232995672256907
355 ms 68.186.41.118
1 2026-08-26 00:02 639232985300872416
682 ms 68.186.41.118