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-28. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 370 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

29

Historical checks stored for this nameserver on selected date

Average Latency

370 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:24

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

29

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-28 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
29 2026-08-28 12:24 639235163898672622
2077 ms 185.14.97.165
28 2026-08-28 11:31 639235132147470568
43 ms 185.14.97.165
27 2026-08-28 11:14 639235121907744088
2027 ms 185.14.97.165
26 2026-08-28 10:57 639235111428014262
4 ms 185.14.97.165
25 2026-08-28 10:39 639235100921813626
40 ms 185.14.97.165
24 2026-08-28 09:45 639235068670703481
8 ms 185.14.97.165
23 2026-08-28 09:28 639235058337459445
15 ms 185.14.97.165
22 2026-08-28 09:11 639235047825109146
68 ms 185.14.97.165
21 2026-08-28 08:53 639235037383229033
71 ms 185.14.97.165
20 2026-08-28 08:00 639235005619242711
11 ms 185.14.97.165
19 2026-08-28 07:43 639234995310346584
7 ms 185.14.97.165
18 2026-08-28 07:26 639234984946548933
42 ms 185.14.97.165
17 2026-08-28 07:09 639234974608077290
9 ms 185.14.97.165
16 2026-08-28 06:15 639234942529845595
20 ms 185.14.97.165
15 2026-08-28 05:58 639234932259126627
6 ms 185.14.97.165
14 2026-08-28 05:41 639234921916735988
17 ms 185.14.97.165
13 2026-08-28 05:23 639234911470038027
9 ms 185.14.97.165
12 2026-08-28 04:30 639234879588411654
2026 ms 185.14.97.165
11 2026-08-28 04:13 639234869341589104
2014 ms 185.14.97.165
10 2026-08-28 03:56 639234859012216675
33 ms 185.14.97.165
9 2026-08-28 03:39 639234848695364934
2031 ms 185.14.97.165
8 2026-08-28 02:46 639234816952458162
24 ms 185.14.97.165
7 2026-08-28 02:29 639234806773081598
8 ms 185.14.97.165
6 2026-08-28 02:12 639234796382955255
10 ms 185.14.97.165
5 2026-08-28 01:54 639234786015782563
13 ms 185.14.97.165
4 2026-08-28 01:00 639234753811917646
3 ms 185.14.97.165
3 2026-08-28 00:44 639234743739767811
54 ms 185.14.97.165
2 2026-08-28 00:27 639234733372362811
14 ms 185.14.97.165
1 2026-08-28 00:09 639234723048550337
37 ms 185.14.97.165