DNS response history for ns.sanascope.com

ns.sanascope.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 33 DNS check records, 33 successful responses, 0 failed responses, and 168 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 ns.sanascope.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

168 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.250.97.97

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns.sanascope.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
33 2026-08-26 10:26 639233360361507238
3 ms 91.250.97.97
32 2026-08-26 10:09 639233350067824371
3 ms 91.250.97.97
31 2026-08-26 09:51 639233339545274518
104 ms 91.250.97.97
30 2026-08-26 09:34 639233329214918079
8 ms 91.250.97.97
29 2026-08-26 09:17 639233318749762337
5 ms 91.250.97.97
28 2026-08-26 08:59 639233308387917838
44 ms 91.250.97.97
27 2026-08-26 08:42 639233297961740122
54 ms 91.250.97.97
26 2026-08-26 08:24 639233287487159094
45 ms 91.250.97.97
25 2026-08-26 08:07 639233276995531707
42 ms 91.250.97.97
24 2026-08-26 07:49 639233266521568229
44 ms 91.250.97.97
23 2026-08-26 07:32 639233256081047431
56 ms 91.250.97.97
22 2026-08-26 06:38 639233223620132921
2009 ms 91.250.97.97
21 2026-08-26 06:21 639233213287814244
42 ms 91.250.97.97
20 2026-08-26 06:03 639233202925983161
3 ms 91.250.97.97
19 2026-08-26 05:46 639233192644780696
49 ms 91.250.97.97
18 2026-08-26 05:29 639233182401183833
2 ms 91.250.97.97
17 2026-08-26 05:12 639233172074181051
54 ms 91.250.97.97
16 2026-08-26 04:55 639233161808421455
74 ms 91.250.97.97
15 2026-08-26 04:38 639233151357344052
3 ms 91.250.97.97
14 2026-08-26 04:20 639233141034116946
18 ms 91.250.97.97
13 2026-08-26 04:03 639233130828334142
47 ms 91.250.97.97
12 2026-08-26 03:46 639233120373450007
41 ms 91.250.97.97
11 2026-08-26 03:29 639233110066216193
2 ms 91.250.97.97
10 2026-08-26 02:35 639233078065410564
54 ms 91.250.97.97
9 2026-08-26 02:18 639233067787457832
553 ms 91.250.97.97
8 2026-08-26 02:01 639233057501801162
53 ms 91.250.97.97
7 2026-08-26 01:44 639233047089431703
57 ms 91.250.97.97
6 2026-08-26 01:27 639233036754790688
4 ms 91.250.97.97
5 2026-08-26 01:09 639233026412602472
4 ms 91.250.97.97
4 2026-08-26 00:52 639233016064066127
3 ms 91.250.97.97
3 2026-08-26 00:35 639233005922655772
42 ms 91.250.97.97
2 2026-08-26 00:18 639232995672256907
2016 ms 91.250.97.97
1 2026-08-26 00:01 639232985300872416
3 ms 91.250.97.97