DNS response history for ns1.accessapp.tn

ns1.accessapp.tn 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 38 DNS check records, 37 successful responses, 1 failed responses, and 154 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.accessapp.tn.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

154 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.91.156.250

Most recently resolved hosting IP on selected date

Successful Responses

37

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.accessapp.tn

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
38 2026-08-25 13:06 639232597643611557
112 ms 51.91.156.250
37 2026-08-25 12:48 639232587225721862
201 ms 51.91.156.250
36 2026-08-25 12:31 639232576780683689
34 ms 51.91.156.250
35 2026-08-25 12:14 639232566381512620
4 ms 51.91.156.250
34 2026-08-25 11:56 639232556111768563
27 ms 51.91.156.250
33 2026-08-25 11:39 639232545839529039
22 ms 51.91.156.250
32 2026-08-25 11:22 639232535349285207
170 ms 51.91.156.250
31 2026-08-25 11:04 639232524938080723
20 ms 51.91.156.250
30 2026-08-25 10:11 639232492740373468
32 ms 51.91.156.250
29 2026-08-25 09:53 639232482235303141
39 ms 51.91.156.250
28 2026-08-25 09:36 639232471861770303
23 ms 51.91.156.250
27 2026-08-25 09:19 639232461630217327
55 ms 51.91.156.250
26 2026-08-25 09:02 639232451282965990
23 ms 51.91.156.250
25 2026-08-25 08:44 639232440814614938
2024 ms 51.91.156.250
24 2026-08-25 08:27 639232430410720425
41 ms 51.91.156.250
23 2026-08-25 08:10 639232420003096185
53 ms 51.91.156.250
22 2026-08-25 07:52 639232409467287444
21 ms 51.91.156.250
21 2026-08-25 07:35 639232399077195997
193 ms 51.91.156.250
20 2026-08-25 07:17 639232388731528337
24 ms 51.91.156.250
19 2026-08-25 07:00 639232378288598612
20 ms 51.91.156.250
18 2026-08-25 06:07 639232346196373643
31 ms 51.91.156.250
17 2026-08-25 05:50 639232336112370741
6 ms 51.91.156.250
16 2026-08-25 05:33 639232326146508970
2059 ms 51.91.156.250
15 2026-08-25 05:17 639232316189381720
11 ms 51.91.156.250
14 2026-08-25 05:00 639232306217998913
18 ms 51.91.156.250
13 2026-08-25 04:43 639232296255744174
110 ms 51.91.156.250
12 2026-08-25 04:26 639232286095760789
14 ms 51.91.156.250
11 2026-08-25 04:10 639232276086186273
24 ms 51.91.156.250
10 2026-08-25 03:53 639232265900986425
65 ms 51.91.156.250
9 2026-08-25 03:36 639232255723518075
-
8 2026-08-25 03:19 639232245484452890
53 ms 51.91.156.250
7 2026-08-25 03:02 639232235157175331
29 ms 51.91.156.250
6 2026-08-25 02:08 639232203197189095
27 ms 51.91.156.250
5 2026-08-25 01:51 639232192844564298
20 ms 51.91.156.250
4 2026-08-25 01:34 639232182496008942
27 ms 51.91.156.250
3 2026-08-25 01:17 639232172197053132
25 ms 51.91.156.250
2 2026-08-25 00:23 639232140250307418
23 ms 51.91.156.250
1 2026-08-25 00:06 639232129927860324
34 ms 51.91.156.250