DNS response history for ns2.swimsel.com

ns2.swimsel.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 386 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.swimsel.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

386 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.160.177

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.swimsel.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:28 639233360361507238
353 ms 162.240.160.177
32 2026-08-26 10:10 639233350067824371
1185 ms 162.240.160.177
31 2026-08-26 09:53 639233339545274518
354 ms 162.240.160.177
30 2026-08-26 09:36 639233329214918079
363 ms 162.240.160.177
29 2026-08-26 09:18 639233318749762337
374 ms 162.240.160.177
28 2026-08-26 09:01 639233308387917838
380 ms 162.240.160.177
27 2026-08-26 08:44 639233297961740122
377 ms 162.240.160.177
26 2026-08-26 08:26 639233287487159094
507 ms 162.240.160.177
25 2026-08-26 08:09 639233276995531707
379 ms 162.240.160.177
24 2026-08-26 07:51 639233266521568229
378 ms 162.240.160.177
23 2026-08-26 07:34 639233256081047431
353 ms 162.240.160.177
22 2026-08-26 06:40 639233223620132921
353 ms 162.240.160.177
21 2026-08-26 06:23 639233213287814244
376 ms 162.240.160.177
20 2026-08-26 06:05 639233202925983161
352 ms 162.240.160.177
19 2026-08-26 05:48 639233192644780696
350 ms 162.240.160.177
18 2026-08-26 05:31 639233182401183833
346 ms 162.240.160.177
17 2026-08-26 05:14 639233172074181051
355 ms 162.240.160.177
16 2026-08-26 04:57 639233161808421455
350 ms 162.240.160.177
15 2026-08-26 04:39 639233151357344052
348 ms 162.240.160.177
14 2026-08-26 04:22 639233141034116946
348 ms 162.240.160.177
13 2026-08-26 04:05 639233130828334142
350 ms 162.240.160.177
12 2026-08-26 03:48 639233120373450007
350 ms 162.240.160.177
11 2026-08-26 03:30 639233110066216193
348 ms 162.240.160.177
10 2026-08-26 02:37 639233078065410564
351 ms 162.240.160.177
9 2026-08-26 02:20 639233067787457832
353 ms 162.240.160.177
8 2026-08-26 02:03 639233057501801162
348 ms 162.240.160.177
7 2026-08-26 01:46 639233047089431703
349 ms 162.240.160.177
6 2026-08-26 01:28 639233036754790688
352 ms 162.240.160.177
5 2026-08-26 01:11 639233026412602472
345 ms 162.240.160.177
4 2026-08-26 00:54 639233016064066127
363 ms 162.240.160.177
3 2026-08-26 00:37 639233005922655772
349 ms 162.240.160.177
2 2026-08-26 00:20 639232995672256907
345 ms 162.240.160.177
1 2026-08-26 00:03 639232985300872416
347 ms 162.240.160.177