DNS response history for ns1.pinesentry.com

ns1.pinesentry.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 37 DNS check records, 37 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 ns1.pinesentry.com.
Records on Selected Date

37

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-24 15:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

35.197.225.59

Most recently resolved hosting IP on selected date

Successful Responses

37

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.pinesentry.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
37 2026-08-24 15:27 639231818080917481
2019 ms 35.197.225.59
36 2026-08-24 15:10 639231807961539652
2036 ms 35.197.225.59
35 2026-08-24 14:53 639231797631669865
44 ms 35.197.225.59
34 2026-08-24 14:00 639231765923559455
139 ms 35.197.225.59
33 2026-08-24 13:43 639231755868832964
67 ms 35.197.225.59
32 2026-08-24 13:26 639231745628278877
123 ms 35.197.225.59
31 2026-08-24 13:09 639231735407682062
40 ms 35.197.225.59
30 2026-08-24 12:17 639231703815441688
28 ms 35.197.225.59
29 2026-08-24 12:00 639231693747052549
25 ms 35.197.225.59
28 2026-08-24 11:43 639231683712487276
67 ms 35.197.225.59
27 2026-08-24 11:26 639231673513573868
72 ms 35.197.225.59
26 2026-08-24 10:33 639231641791249939
46 ms 35.197.225.59
25 2026-08-24 10:16 639231631866211033
61 ms 35.197.225.59
24 2026-08-24 10:00 639231621644955316
2035 ms 35.197.225.59
23 2026-08-24 09:43 639231611478799259
2025 ms 35.197.225.59
22 2026-08-24 08:50 639231579923718211
25 ms 35.197.225.59
21 2026-08-24 08:33 639231569810702936
36 ms 35.197.225.59
20 2026-08-24 08:16 639231559762411619
134 ms 35.197.225.59
19 2026-08-24 08:00 639231549663595407
498 ms 35.197.225.59
18 2026-08-24 07:07 639231518076817246
31 ms 35.197.225.59
17 2026-08-24 06:50 639231508078650885
40 ms 35.197.225.59
16 2026-08-24 06:34 639231498210697093
51 ms 35.197.225.59
15 2026-08-24 06:17 639231488109699360
27 ms 35.197.225.59
14 2026-08-24 05:25 639231456772510692
81 ms 35.197.225.59
13 2026-08-24 05:09 639231447084631185
39 ms 35.197.225.59
12 2026-08-24 04:52 639231437208519473
29 ms 35.197.225.59
11 2026-08-24 04:36 639231427209627490
44 ms 35.197.225.59
10 2026-08-24 03:43 639231395791246644
11 ms 35.197.225.59
9 2026-08-24 03:27 639231386075551458
11 ms 35.197.225.59
8 2026-08-24 03:11 639231376208713791
44 ms 35.197.225.59
7 2026-08-24 02:54 639231366170589276
38 ms 35.197.225.59
6 2026-08-24 02:02 639231334732159368
2013 ms 35.197.225.59
5 2026-08-24 01:45 639231325035670078
164 ms 35.197.225.59
4 2026-08-24 01:29 639231315132253837
53 ms 35.197.225.59
3 2026-08-24 01:12 639231305014280808
42 ms 35.197.225.59
2 2026-08-24 00:20 639231273779380675
40 ms 35.197.225.59
1 2026-08-24 00:04 639231264180839154
53 ms 35.197.225.59