DNS response history for ns2.partner-s.pro

ns2.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-27. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 404 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.partner-s.pro.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

404 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

178.236.128.109

Most recently resolved hosting IP on selected date

Successful Responses

32

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

Showing DNS history for 2026-08-27 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
32 2026-08-27 10:17 639234222943951923
2078 ms 178.236.128.109
31 2026-08-27 10:00 639234212558002823
438 ms 178.236.128.109
30 2026-08-27 09:43 639234202117531850
317 ms 178.236.128.109
29 2026-08-27 09:25 639234191649612722
65 ms 178.236.128.109
28 2026-08-27 09:08 639234181105879568
69 ms 178.236.128.109
27 2026-08-27 08:50 639234170713214496
318 ms 178.236.128.109
26 2026-08-27 08:33 639234160341037652
201 ms 178.236.128.109
25 2026-08-27 08:16 639234149799404224
326 ms 178.236.128.109
24 2026-08-27 07:58 639234139553286469
94 ms 178.236.128.109
23 2026-08-27 07:05 639234107183588293
318 ms 178.236.128.109
22 2026-08-27 06:47 639234096905435724
542 ms 178.236.128.109
21 2026-08-27 06:30 639234086579410775
425 ms 178.236.128.109
20 2026-08-27 06:13 639234076291157956
545 ms 178.236.128.109
19 2026-08-27 05:56 639234065981939454
327 ms 178.236.128.109
18 2026-08-27 05:39 639234055548642997
546 ms 178.236.128.109
17 2026-08-27 05:21 639234045267979603
148 ms 178.236.128.109
16 2026-08-27 05:04 639234034999717463
59 ms 178.236.128.109
15 2026-08-27 04:47 639234024739225358
64 ms 178.236.128.109
14 2026-08-27 04:30 639234014311170162
64 ms 178.236.128.109
13 2026-08-27 04:12 639234003806017640
586 ms 178.236.128.109
12 2026-08-27 03:55 639233993356203030
2081 ms 178.236.128.109
11 2026-08-27 03:02 639233961301716608
146 ms 178.236.128.109
10 2026-08-27 02:44 639233950834200647
642 ms 178.236.128.109
9 2026-08-27 02:27 639233940431849026
366 ms 178.236.128.109
8 2026-08-27 02:09 639233930110596398
323 ms 178.236.128.109
7 2026-08-27 01:52 639233919705434540
147 ms 178.236.128.109
6 2026-08-27 01:35 639233909452807845
67 ms 178.236.128.109
5 2026-08-27 01:18 639233899096420820
251 ms 178.236.128.109
4 2026-08-27 01:00 639233888707824939
151 ms 178.236.128.109
3 2026-08-27 00:43 639233878461203802
829 ms 178.236.128.109
2 2026-08-27 00:26 639233868060868209
156 ms 178.236.128.109
1 2026-08-27 00:08 639233857450922991
252 ms 178.236.128.109