DNS response history for ns2.evoserver.co.uk

ns2.evoserver.co.uk 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 31 DNS check records, 31 successful responses, 0 failed responses, and 242 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.evoserver.co.uk.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

242 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

166.117.220.151

Most recently resolved hosting IP on selected date

Successful Responses

31

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.evoserver.co.uk

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
31 2026-08-26 10:05 639233350067824371
26 ms 166.117.220.151
30 2026-08-26 09:48 639233339545274518
3 ms 166.117.220.151
29 2026-08-26 09:31 639233329214918079
21 ms 166.117.220.151
28 2026-08-26 09:13 639233318749762337
33 ms 166.117.220.151
27 2026-08-26 08:56 639233308387917838
2195 ms 166.117.220.151
26 2026-08-26 08:39 639233297961740122
50 ms 166.117.220.151
25 2026-08-26 08:21 639233287487159094
44 ms 166.117.220.151
24 2026-08-26 08:04 639233276995531707
4 ms 166.117.220.151
23 2026-08-26 07:46 639233266521568229
3 ms 166.117.220.151
22 2026-08-26 07:29 639233256081047431
43 ms 166.117.220.151
21 2026-08-26 06:35 639233223620132921
2022 ms 166.117.220.151
20 2026-08-26 06:18 639233213287814244
23 ms 166.117.220.151
19 2026-08-26 06:00 639233202925983161
271 ms 166.117.220.151
18 2026-08-26 05:43 639233192644780696
2223 ms 166.117.220.151
17 2026-08-26 05:26 639233182401183833
3 ms 166.117.220.151
16 2026-08-26 05:09 639233172074181051
5 ms 166.117.220.151
15 2026-08-26 04:52 639233161808421455
39 ms 166.117.220.151
14 2026-08-26 04:34 639233151357344052
48 ms 166.117.220.151
13 2026-08-26 04:17 639233141034116946
20 ms 166.117.220.151
12 2026-08-26 04:00 639233130828334142
29 ms 166.117.220.151
11 2026-08-26 03:43 639233120373450007
44 ms 166.117.220.151
10 2026-08-26 03:25 639233110066216193
64 ms 166.117.220.151
9 2026-08-26 02:32 639233078065410564
45 ms 166.117.220.151
8 2026-08-26 02:15 639233067787457832
3 ms 166.117.220.151
7 2026-08-26 01:58 639233057501801162
4 ms 166.117.220.151
6 2026-08-26 01:40 639233047089431703
53 ms 166.117.220.151
5 2026-08-26 01:23 639233036754790688
2 ms 166.117.220.151
4 2026-08-26 01:06 639233026412602472
3 ms 166.117.220.151
3 2026-08-26 00:49 639233016064066127
13 ms 166.117.220.151
2 2026-08-26 00:32 639233005922655772
32 ms 166.117.220.151
1 2026-08-26 00:15 639232995672256907
122 ms 166.117.220.151