DNS response history for ns2.remelsan.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

356 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

146.185.149.154

Most recently resolved hosting IP on selected date

Successful Responses

38

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.remelsan.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
38 2026-08-26 12:42 639233445367152284
1285 ms 146.185.149.154
37 2026-08-26 12:24 639233434974187439
133 ms 146.185.149.154
36 2026-08-26 12:07 639233424567558554
122 ms 146.185.149.154
35 2026-08-26 11:49 639233414056832719
63 ms 146.185.149.154
34 2026-08-26 11:32 639233403515141099
126 ms 146.185.149.154
33 2026-08-26 10:37 639233370841350248
2069 ms 146.185.149.154
32 2026-08-26 10:20 639233360361507238
66 ms 146.185.149.154
31 2026-08-26 10:03 639233350067824371
116 ms 146.185.149.154
30 2026-08-26 09:45 639233339545274518
127 ms 146.185.149.154
29 2026-08-26 09:28 639233329214918079
146 ms 146.185.149.154
28 2026-08-26 09:10 639233318749762337
122 ms 146.185.149.154
27 2026-08-26 08:53 639233308387917838
122 ms 146.185.149.154
26 2026-08-26 08:36 639233297961740122
2051 ms 146.185.149.154
25 2026-08-26 08:18 639233287487159094
118 ms 146.185.149.154
24 2026-08-26 08:01 639233276995531707
63 ms 146.185.149.154
23 2026-08-26 07:43 639233266521568229
61 ms 146.185.149.154
22 2026-08-26 07:26 639233256081047431
718 ms 146.185.149.154
21 2026-08-26 06:32 639233223620132921
128 ms 146.185.149.154
20 2026-08-26 06:15 639233213287814244
4 ms 146.185.149.154
19 2026-08-26 05:57 639233202925983161
125 ms 146.185.149.154
18 2026-08-26 05:40 639233192644780696
59 ms 146.185.149.154
17 2026-08-26 05:23 639233182401183833
131 ms 146.185.149.154
16 2026-08-26 05:06 639233172074181051
122 ms 146.185.149.154
15 2026-08-26 04:49 639233161808421455
120 ms 146.185.149.154
14 2026-08-26 04:31 639233151357344052
117 ms 146.185.149.154
13 2026-08-26 04:14 639233141034116946
68 ms 146.185.149.154
12 2026-08-26 03:57 639233130828334142
67 ms 146.185.149.154
11 2026-08-26 03:40 639233120373450007
118 ms 146.185.149.154
10 2026-08-26 03:23 639233110066216193
32 ms 146.185.149.154
9 2026-08-26 02:29 639233078065410564
123 ms 146.185.149.154
8 2026-08-26 02:12 639233067787457832
122 ms 146.185.149.154
7 2026-08-26 01:55 639233057501801162
124 ms 146.185.149.154
6 2026-08-26 01:38 639233047089431703
91 ms 146.185.149.154
5 2026-08-26 01:21 639233036754790688
2041 ms 146.185.149.154
4 2026-08-26 01:03 639233026412602472
2094 ms 146.185.149.154
3 2026-08-26 00:46 639233016064066127
124 ms 146.185.149.154
2 2026-08-26 00:29 639233005922655772
59 ms 146.185.149.154
1 2026-08-26 00:12 639232995672256907
162 ms 146.185.149.154