DNS response history for ns2.server32.net

ns2.server32.net 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 333 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.server32.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

333 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.121.194.170

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.server32.net

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:25 639233360361507238
418 ms 91.121.194.170
32 2026-08-26 10:08 639233350067824371
240 ms 91.121.194.170
31 2026-08-26 09:50 639233339545274518
226 ms 91.121.194.170
30 2026-08-26 09:33 639233329214918079
265 ms 91.121.194.170
29 2026-08-26 09:16 639233318749762337
258 ms 91.121.194.170
28 2026-08-26 08:58 639233308387917838
265 ms 91.121.194.170
27 2026-08-26 08:41 639233297961740122
251 ms 91.121.194.170
26 2026-08-26 08:23 639233287487159094
255 ms 91.121.194.170
25 2026-08-26 08:06 639233276995531707
2225 ms 91.121.194.170
24 2026-08-26 07:48 639233266521568229
132 ms 91.121.194.170
23 2026-08-26 07:31 639233256081047431
243 ms 91.121.194.170
22 2026-08-26 06:37 639233223620132921
225 ms 91.121.194.170
21 2026-08-26 06:20 639233213287814244
12 ms 91.121.194.170
20 2026-08-26 06:02 639233202925983161
143 ms 91.121.194.170
19 2026-08-26 05:45 639233192644780696
120 ms 91.121.194.170
18 2026-08-26 05:28 639233182401183833
223 ms 91.121.194.170
17 2026-08-26 05:11 639233172074181051
245 ms 91.121.194.170
16 2026-08-26 04:54 639233161808421455
232 ms 91.121.194.170
15 2026-08-26 04:37 639233151357344052
274 ms 91.121.194.170
14 2026-08-26 04:19 639233141034116946
268 ms 91.121.194.170
13 2026-08-26 04:02 639233130828334142
1753 ms 91.121.194.170
12 2026-08-26 03:45 639233120373450007
126 ms 91.121.194.170
11 2026-08-26 03:28 639233110066216193
158 ms 91.121.194.170
10 2026-08-26 02:34 639233078065410564
274 ms 91.121.194.170
9 2026-08-26 02:17 639233067787457832
260 ms 91.121.194.170
8 2026-08-26 02:00 639233057501801162
129 ms 91.121.194.170
7 2026-08-26 01:43 639233047089431703
261 ms 91.121.194.170
6 2026-08-26 01:26 639233036754790688
248 ms 91.121.194.170
5 2026-08-26 01:08 639233026412602472
258 ms 91.121.194.170
4 2026-08-26 00:51 639233016064066127
267 ms 91.121.194.170
3 2026-08-26 00:34 639233005922655772
254 ms 91.121.194.170
2 2026-08-26 00:17 639232995672256907
258 ms 91.121.194.170
1 2026-08-26 00:00 639232985300872416
230 ms 91.121.194.170