DNS response history for ns2.algomonk.net

ns2.algomonk.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 26 DNS check records, 26 successful responses, 0 failed responses, and 211 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.algomonk.net.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

211 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.171.180.182

Most recently resolved hosting IP on selected date

Successful Responses

26

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.algomonk.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
26 2026-08-26 08:40 639233297961740122
264 ms 103.171.180.182
25 2026-08-26 08:23 639233287487159094
273 ms 103.171.180.182
24 2026-08-26 08:05 639233276995531707
279 ms 103.171.180.182
23 2026-08-26 07:48 639233266521568229
284 ms 103.171.180.182
22 2026-08-26 07:30 639233256081047431
271 ms 103.171.180.182
21 2026-08-26 06:36 639233223620132921
276 ms 103.171.180.182
20 2026-08-26 06:19 639233213287814244
11 ms 103.171.180.182
19 2026-08-26 06:02 639233202925983161
304 ms 103.171.180.182
18 2026-08-26 05:45 639233192644780696
135 ms 103.171.180.182
17 2026-08-26 05:27 639233182401183833
284 ms 103.171.180.182
16 2026-08-26 05:10 639233172074181051
276 ms 103.171.180.182
15 2026-08-26 04:53 639233161808421455
308 ms 103.171.180.182
14 2026-08-26 04:36 639233151357344052
267 ms 103.171.180.182
13 2026-08-26 04:19 639233141034116946
160 ms 103.171.180.182
12 2026-08-26 04:02 639233130828334142
278 ms 103.171.180.182
11 2026-08-26 03:44 639233120373450007
129 ms 103.171.180.182
10 2026-08-26 03:27 639233110066216193
134 ms 103.171.180.182
9 2026-08-26 02:34 639233078065410564
3 ms 103.171.180.182
8 2026-08-26 02:17 639233067787457832
270 ms 103.171.180.182
7 2026-08-26 01:59 639233057501801162
6 ms 103.171.180.182
6 2026-08-26 01:42 639233047089431703
134 ms 103.171.180.182
5 2026-08-26 01:25 639233036754790688
281 ms 103.171.180.182
4 2026-08-26 01:08 639233026412602472
289 ms 103.171.180.182
3 2026-08-26 00:50 639233016064066127
140 ms 103.171.180.182
2 2026-08-26 00:33 639233005922655772
156 ms 103.171.180.182
1 2026-08-26 00:16 639232995672256907
280 ms 103.171.180.182