DNS response history for ns1.sanal.pro

ns1.sanal.pro 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-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 497 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 ns1.sanal.pro.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

497 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.138.208.228

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 ns1.sanal.pro

Showing DNS history for 2026-08-25 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-25 11:43 639232545839529039
98 ms 94.138.208.228
32 2026-08-25 11:25 639232535349285207
99 ms 94.138.208.228
31 2026-08-25 11:08 639232524938080723
67 ms 94.138.208.228
30 2026-08-25 10:14 639232492740373468
297 ms 94.138.208.228
29 2026-08-25 09:57 639232482235303141
212 ms 94.138.208.228
28 2026-08-25 09:39 639232471861770303
4058 ms 94.138.208.228
27 2026-08-25 09:22 639232461630217327
86 ms 94.138.208.228
26 2026-08-25 09:05 639232451282965990
232 ms 94.138.208.228
25 2026-08-25 08:48 639232440814614938
194 ms 94.138.208.228
24 2026-08-25 08:30 639232430410720425
93 ms 94.138.208.228
23 2026-08-25 08:13 639232420003096185
45 ms 94.138.208.228
22 2026-08-25 07:56 639232409467287444
328 ms 94.138.208.228
21 2026-08-25 07:38 639232399077195997
340 ms 94.138.208.228
20 2026-08-25 07:21 639232388731528337
213 ms 94.138.208.228
19 2026-08-25 07:03 639232378288598612
181 ms 94.138.208.228
18 2026-08-25 06:10 639232346196373643
215 ms 94.138.208.228
17 2026-08-25 05:53 639232336112370741
94 ms 94.138.208.228
16 2026-08-25 05:37 639232326146508970
122 ms 94.138.208.228
15 2026-08-25 05:20 639232316189381720
52 ms 94.138.208.228
14 2026-08-25 05:03 639232306217998913
2032 ms 94.138.208.228
13 2026-08-25 04:47 639232296255744174
56 ms 94.138.208.228
12 2026-08-25 04:30 639232286095760789
41 ms 94.138.208.228
11 2026-08-25 04:13 639232276086186273
2055 ms 94.138.208.228
10 2026-08-25 03:56 639232265900986425
87 ms 94.138.208.228
9 2026-08-25 03:39 639232255723518075
7 ms 94.138.208.228
8 2026-08-25 03:22 639232245484452890
103 ms 94.138.208.228
7 2026-08-25 03:05 639232235157175331
504 ms 94.138.208.228
6 2026-08-25 02:12 639232203197189095
96 ms 94.138.208.228
5 2026-08-25 01:54 639232192844564298
2008 ms 94.138.208.228
4 2026-08-25 01:37 639232182496008942
31 ms 94.138.208.228
3 2026-08-25 01:20 639232172197053132
2059 ms 94.138.208.228
2 2026-08-25 00:27 639232140250307418
216 ms 94.138.208.228
1 2026-08-25 00:10 639232129927860324
84 ms 94.138.208.228