DNS response history for ns1.mylogsys.com

ns1.mylogsys.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 35 DNS check records, 35 successful responses, 0 failed responses, and 282 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 ns1.mylogsys.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

282 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.248.172.170

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns1.mylogsys.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
35 2026-08-24 14:58 639231797631669865
2263 ms 173.248.172.170
34 2026-08-24 14:05 639231765923559455
131 ms 173.248.172.170
33 2026-08-24 13:49 639231755868832964
141 ms 173.248.172.170
32 2026-08-24 13:32 639231745628278877
8 ms 173.248.172.170
31 2026-08-24 13:14 639231735407682062
3 ms 173.248.172.170
30 2026-08-24 12:22 639231703815441688
12 ms 173.248.172.170
29 2026-08-24 12:05 639231693747052549
153 ms 173.248.172.170
28 2026-08-24 11:48 639231683712487276
264 ms 173.248.172.170
27 2026-08-24 11:31 639231673513573868
261 ms 173.248.172.170
26 2026-08-24 10:38 639231641791249939
8 ms 173.248.172.170
25 2026-08-24 10:22 639231631866211033
2 ms 173.248.172.170
24 2026-08-24 10:05 639231621644955316
2146 ms 173.248.172.170
23 2026-08-24 09:48 639231611478799259
3 ms 173.248.172.170
22 2026-08-24 08:55 639231579923718211
133 ms 173.248.172.170
21 2026-08-24 08:39 639231569810702936
257 ms 173.248.172.170
20 2026-08-24 08:21 639231559762411619
291 ms 173.248.172.170
19 2026-08-24 08:05 639231549663595407
263 ms 173.248.172.170
18 2026-08-24 07:12 639231518076817246
264 ms 173.248.172.170
17 2026-08-24 06:56 639231508078650885
8 ms 173.248.172.170
16 2026-08-24 06:39 639231498210697093
25 ms 173.248.172.170
15 2026-08-24 06:23 639231488109699360
130 ms 173.248.172.170
14 2026-08-24 05:30 639231456772510692
3 ms 173.248.172.170
13 2026-08-24 05:14 639231447084631185
262 ms 173.248.172.170
12 2026-08-24 04:57 639231437208519473
3 ms 173.248.172.170
11 2026-08-24 04:41 639231427209627490
142 ms 173.248.172.170
10 2026-08-24 03:48 639231395791246644
142 ms 173.248.172.170
9 2026-08-24 03:32 639231386075551458
161 ms 173.248.172.170
8 2026-08-24 03:16 639231376208713791
181 ms 173.248.172.170
7 2026-08-24 02:59 639231366170589276
3 ms 173.248.172.170
6 2026-08-24 02:07 639231334732159368
142 ms 173.248.172.170
5 2026-08-24 01:50 639231325035670078
3 ms 173.248.172.170
4 2026-08-24 01:34 639231315132253837
2 ms 173.248.172.170
3 2026-08-24 01:17 639231305014280808
23 ms 173.248.172.170
2 2026-08-24 00:25 639231273779380675
5 ms 173.248.172.170
1 2026-08-24 00:09 639231264180839154
2032 ms 173.248.172.170