DNS response history for ns2.swiftlyserver.com

ns2.swiftlyserver.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 202 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.swiftlyserver.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

202 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.14.97.165

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 ns2.swiftlyserver.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:36 639233370841350248
5 ms 185.14.97.165
32 2026-08-26 10:18 639233360361507238
9 ms 185.14.97.165
31 2026-08-26 10:01 639233350067824371
5 ms 185.14.97.165
30 2026-08-26 09:44 639233339545274518
18 ms 185.14.97.165
29 2026-08-26 09:26 639233329214918079
6 ms 185.14.97.165
28 2026-08-26 09:09 639233318749762337
35 ms 185.14.97.165
27 2026-08-26 08:52 639233308387917838
7 ms 185.14.97.165
26 2026-08-26 08:34 639233297961740122
5 ms 185.14.97.165
25 2026-08-26 08:17 639233287487159094
15 ms 185.14.97.165
24 2026-08-26 07:59 639233276995531707
43 ms 185.14.97.165
23 2026-08-26 07:42 639233266521568229
24 ms 185.14.97.165
22 2026-08-26 07:24 639233256081047431
46 ms 185.14.97.165
21 2026-08-26 06:30 639233223620132921
18 ms 185.14.97.165
20 2026-08-26 06:13 639233213287814244
7 ms 185.14.97.165
19 2026-08-26 05:56 639233202925983161
4 ms 185.14.97.165
18 2026-08-26 05:39 639233192644780696
14 ms 185.14.97.165
17 2026-08-26 05:22 639233182401183833
9 ms 185.14.97.165
16 2026-08-26 05:04 639233172074181051
9 ms 185.14.97.165
15 2026-08-26 04:47 639233161808421455
2037 ms 185.14.97.165
14 2026-08-26 04:30 639233151357344052
59 ms 185.14.97.165
13 2026-08-26 04:13 639233141034116946
10 ms 185.14.97.165
12 2026-08-26 03:56 639233130828334142
21 ms 185.14.97.165
11 2026-08-26 03:38 639233120373450007
14 ms 185.14.97.165
10 2026-08-26 03:21 639233110066216193
28 ms 185.14.97.165
9 2026-08-26 02:28 639233078065410564
8 ms 185.14.97.165
8 2026-08-26 02:11 639233067787457832
12 ms 185.14.97.165
7 2026-08-26 01:54 639233057501801162
2034 ms 185.14.97.165
6 2026-08-26 01:36 639233047089431703
10 ms 185.14.97.165
5 2026-08-26 01:19 639233036754790688
2042 ms 185.14.97.165
4 2026-08-26 01:02 639233026412602472
33 ms 185.14.97.165
3 2026-08-26 00:44 639233016064066127
37 ms 185.14.97.165
2 2026-08-26 00:27 639233005922655772
10 ms 185.14.97.165
1 2026-08-26 00:10 639232995672256907
29 ms 185.14.97.165