DNS response history for ns1.partner-s.pro

ns1.partner-s.pro 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 34 DNS check records, 34 successful responses, 0 failed responses, and 313 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.partner-s.pro.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

313 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

178.236.128.108

Most recently resolved hosting IP on selected date

Successful Responses

34

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.partner-s.pro

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
34 2026-08-24 14:04 639231765923559455
63 ms 178.236.128.108
33 2026-08-24 13:47 639231755868832964
138 ms 178.236.128.108
32 2026-08-24 13:30 639231745628278877
128 ms 178.236.128.108
31 2026-08-24 13:13 639231735407682062
132 ms 178.236.128.108
30 2026-08-24 12:20 639231703815441688
73 ms 178.236.128.108
29 2026-08-24 12:03 639231693747052549
57 ms 178.236.128.108
28 2026-08-24 11:46 639231683712487276
53 ms 178.236.128.108
27 2026-08-24 11:29 639231673513573868
135 ms 178.236.128.108
26 2026-08-24 10:37 639231641791249939
63 ms 178.236.128.108
25 2026-08-24 10:20 639231631866211033
68 ms 178.236.128.108
24 2026-08-24 10:03 639231621644955316
80 ms 178.236.128.108
23 2026-08-24 09:46 639231611478799259
83 ms 178.236.128.108
22 2026-08-24 08:54 639231579923718211
131 ms 178.236.128.108
21 2026-08-24 08:37 639231569810702936
87 ms 178.236.128.108
20 2026-08-24 08:20 639231559762411619
62 ms 178.236.128.108
19 2026-08-24 08:03 639231549663595407
58 ms 178.236.128.108
18 2026-08-24 07:11 639231518076817246
133 ms 178.236.128.108
17 2026-08-24 06:54 639231508078650885
66 ms 178.236.128.108
16 2026-08-24 06:37 639231498210697093
62 ms 178.236.128.108
15 2026-08-24 06:21 639231488109699360
2075 ms 178.236.128.108
14 2026-08-24 05:28 639231456772510692
76 ms 178.236.128.108
13 2026-08-24 05:12 639231447084631185
70 ms 178.236.128.108
12 2026-08-24 04:56 639231437208519473
73 ms 178.236.128.108
11 2026-08-24 04:39 639231427209627490
122 ms 178.236.128.108
10 2026-08-24 03:47 639231395791246644
59 ms 178.236.128.108
9 2026-08-24 03:31 639231386075551458
7 ms 178.236.128.108
8 2026-08-24 03:14 639231376208713791
65 ms 178.236.128.108
7 2026-08-24 02:57 639231366170589276
101 ms 178.236.128.108
6 2026-08-24 02:05 639231334732159368
61 ms 178.236.128.108
5 2026-08-24 01:49 639231325035670078
2071 ms 178.236.128.108
4 2026-08-24 01:32 639231315132253837
61 ms 178.236.128.108
3 2026-08-24 01:15 639231305014280808
67 ms 178.236.128.108
2 2026-08-24 00:23 639231273779380675
7 ms 178.236.128.108
1 2026-08-24 00:07 639231264180839154
4070 ms 178.236.128.108