DNS response history for ns2.logsipe.com

ns2.logsipe.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 552 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.logsipe.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

552 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.161.75.129

Most recently resolved hosting IP on selected date

Successful Responses

30

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.logsipe.com

Showing DNS history for 2026-08-24 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
30 2026-08-24 12:25 639231703815441688
8 ms 51.161.75.129
29 2026-08-24 12:08 639231693747052549
4 ms 51.161.75.129
28 2026-08-24 11:51 639231683712487276
236 ms 51.161.75.129
27 2026-08-24 11:34 639231673513573868
348 ms 51.161.75.129
26 2026-08-24 10:41 639231641791249939
241 ms 51.161.75.129
25 2026-08-24 10:25 639231631866211033
354 ms 51.161.75.129
24 2026-08-24 10:08 639231621644955316
5 ms 51.161.75.129
23 2026-08-24 09:51 639231611478799259
235 ms 51.161.75.129
22 2026-08-24 08:58 639231579923718211
354 ms 51.161.75.129
21 2026-08-24 08:42 639231569810702936
4 ms 51.161.75.129
20 2026-08-24 08:24 639231559762411619
355 ms 51.161.75.129
19 2026-08-24 08:08 639231549663595407
233 ms 51.161.75.129
18 2026-08-24 07:15 639231518076817246
359 ms 51.161.75.129
17 2026-08-24 06:59 639231508078650885
5 ms 51.161.75.129
16 2026-08-24 06:42 639231498210697093
347 ms 51.161.75.129
15 2026-08-24 06:25 639231488109699360
4138 ms 51.161.75.129
14 2026-08-24 05:33 639231456772510692
5 ms 51.161.75.129
13 2026-08-24 05:17 639231447084631185
113 ms 51.161.75.129
12 2026-08-24 05:00 639231437208519473
221 ms 51.161.75.129
11 2026-08-24 04:44 639231427209627490
355 ms 51.161.75.129
10 2026-08-24 03:51 639231395791246644
318 ms 51.161.75.129
9 2026-08-24 03:35 639231386075551458
349 ms 51.161.75.129
8 2026-08-24 03:19 639231376208713791
2231 ms 51.161.75.129
7 2026-08-24 03:02 639231366170589276
4326 ms 51.161.75.129
6 2026-08-24 02:10 639231334732159368
347 ms 51.161.75.129
5 2026-08-24 01:53 639231325035670078
112 ms 51.161.75.129
4 2026-08-24 01:37 639231315132253837
246 ms 51.161.75.129
3 2026-08-24 01:20 639231305014280808
3 ms 51.161.75.129
2 2026-08-24 00:28 639231273779380675
348 ms 51.161.75.129
1 2026-08-24 00:12 639231264180839154
360 ms 51.161.75.129