DNS response history for ns2.swdhdns.com

ns2.swdhdns.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 35 DNS check records, 35 successful responses, 0 failed responses, and 286 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.swdhdns.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

286 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

97.79.236.53

Most recently resolved hosting IP on selected date

Successful Responses

35

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.swdhdns.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
35 2026-08-26 11:54 639233414056832719
312 ms 97.79.236.53
34 2026-08-26 11:37 639233403515141099
272 ms 97.79.236.53
33 2026-08-26 10:42 639233370841350248
161 ms 97.79.236.53
32 2026-08-26 10:25 639233360361507238
268 ms 97.79.236.53
31 2026-08-26 10:07 639233350067824371
270 ms 97.79.236.53
30 2026-08-26 09:50 639233339545274518
2165 ms 97.79.236.53
29 2026-08-26 09:32 639233329214918079
157 ms 97.79.236.53
28 2026-08-26 09:15 639233318749762337
159 ms 97.79.236.53
27 2026-08-26 08:58 639233308387917838
272 ms 97.79.236.53
26 2026-08-26 08:41 639233297961740122
262 ms 97.79.236.53
25 2026-08-26 08:23 639233287487159094
272 ms 97.79.236.53
24 2026-08-26 08:06 639233276995531707
275 ms 97.79.236.53
23 2026-08-26 07:48 639233266521568229
275 ms 97.79.236.53
22 2026-08-26 07:31 639233256081047431
146 ms 97.79.236.53
21 2026-08-26 06:37 639233223620132921
156 ms 97.79.236.53
20 2026-08-26 06:19 639233213287814244
281 ms 97.79.236.53
19 2026-08-26 06:02 639233202925983161
267 ms 97.79.236.53
18 2026-08-26 05:45 639233192644780696
142 ms 97.79.236.53
17 2026-08-26 05:28 639233182401183833
268 ms 97.79.236.53
16 2026-08-26 05:11 639233172074181051
271 ms 97.79.236.53
15 2026-08-26 04:54 639233161808421455
272 ms 97.79.236.53
14 2026-08-26 04:36 639233151357344052
276 ms 97.79.236.53
13 2026-08-26 04:19 639233141034116946
269 ms 97.79.236.53
12 2026-08-26 04:02 639233130828334142
147 ms 97.79.236.53
11 2026-08-26 03:45 639233120373450007
265 ms 97.79.236.53
10 2026-08-26 03:27 639233110066216193
139 ms 97.79.236.53
9 2026-08-26 02:34 639233078065410564
148 ms 97.79.236.53
8 2026-08-26 02:17 639233067787457832
272 ms 97.79.236.53
7 2026-08-26 02:00 639233057501801162
262 ms 97.79.236.53
6 2026-08-26 01:43 639233047089431703
141 ms 97.79.236.53
5 2026-08-26 01:25 639233036754790688
166 ms 97.79.236.53
4 2026-08-26 01:08 639233026412602472
264 ms 97.79.236.53
3 2026-08-26 00:51 639233016064066127
268 ms 97.79.236.53
2 2026-08-26 00:34 639233005922655772
206 ms 97.79.236.53
1 2026-08-26 00:17 639232995672256907
270 ms 97.79.236.53