DNS response history for ns2.ten11restaurant.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

267 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

97.74.93.4

Most recently resolved hosting IP on selected date

Successful Responses

34

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.ten11restaurant.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
34 2026-08-26 10:42 639233370841350248
326 ms 97.74.93.4
33 2026-08-26 10:25 639233360361507238
328 ms 97.74.93.4
32 2026-08-26 10:08 639233350067824371
329 ms 97.74.93.4
31 2026-08-26 09:50 639233339545274518
317 ms 97.74.93.4
30 2026-08-26 09:33 639233329214918079
316 ms 97.74.93.4
29 2026-08-26 09:16 639233318749762337
10 ms 97.74.93.4
28 2026-08-26 08:58 639233308387917838
322 ms 97.74.93.4
27 2026-08-26 08:41 639233297961740122
320 ms 97.74.93.4
26 2026-08-26 08:23 639233287487159094
321 ms 97.74.93.4
25 2026-08-26 08:06 639233276995531707
331 ms 97.74.93.4
24 2026-08-26 07:48 639233266521568229
328 ms 97.74.93.4
23 2026-08-26 07:31 639233256081047431
323 ms 97.74.93.4
22 2026-08-26 06:37 639233223620132921
317 ms 97.74.93.4
21 2026-08-26 06:20 639233213287814244
319 ms 97.74.93.4
20 2026-08-26 06:02 639233202925983161
175 ms 97.74.93.4
19 2026-08-26 05:45 639233192644780696
322 ms 97.74.93.4
18 2026-08-26 05:28 639233182401183833
321 ms 97.74.93.4
17 2026-08-26 05:11 639233172074181051
324 ms 97.74.93.4
16 2026-08-26 04:54 639233161808421455
323 ms 97.74.93.4
15 2026-08-26 04:37 639233151357344052
321 ms 97.74.93.4
14 2026-08-26 04:19 639233141034116946
321 ms 97.74.93.4
13 2026-08-26 04:02 639233130828334142
11 ms 97.74.93.4
12 2026-08-26 03:45 639233120373450007
325 ms 97.74.93.4
11 2026-08-26 03:28 639233110066216193
182 ms 97.74.93.4
10 2026-08-26 02:34 639233078065410564
321 ms 97.74.93.4
9 2026-08-26 02:17 639233067787457832
318 ms 97.74.93.4
8 2026-08-26 02:00 639233057501801162
7 ms 97.74.93.4
7 2026-08-26 01:43 639233047089431703
318 ms 97.74.93.4
6 2026-08-26 01:26 639233036754790688
2 ms 97.74.93.4
5 2026-08-26 01:08 639233026412602472
5 ms 97.74.93.4
4 2026-08-26 00:51 639233016064066127
314 ms 97.74.93.4
3 2026-08-26 00:34 639233005922655772
320 ms 97.74.93.4
2 2026-08-26 00:17 639232995672256907
317 ms 97.74.93.4
1 2026-08-26 00:00 639232985300872416
334 ms 97.74.93.4