DNS response history for ns1.partness.com

ns1.partness.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-25. For this date, NameServerHistory found 24 DNS check records, 24 successful responses, 0 failed responses, and 320 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.partness.com.
Records on Selected Date

24

Historical checks stored for this nameserver on selected date

Average Latency

320 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 08:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.46.30.37

Most recently resolved hosting IP on selected date

Successful Responses

24

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

Showing DNS history for 2026-08-25 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
24 2026-08-25 08:27 639232430410720425
2008 ms 94.46.30.37
23 2026-08-25 08:10 639232420003096185
49 ms 94.46.30.37
22 2026-08-25 07:52 639232409467287444
47 ms 94.46.30.37
21 2026-08-25 07:35 639232399077195997
9 ms 94.46.30.37
20 2026-08-25 07:17 639232388731528337
118 ms 94.46.30.37
19 2026-08-25 07:00 639232378288598612
96 ms 94.46.30.37
18 2026-08-25 06:07 639232346196373643
2084 ms 94.46.30.37
17 2026-08-25 05:50 639232336112370741
11 ms 94.46.30.37
16 2026-08-25 05:33 639232326146508970
7 ms 94.46.30.37
15 2026-08-25 05:16 639232316189381720
84 ms 94.46.30.37
14 2026-08-25 05:00 639232306217998913
105 ms 94.46.30.37
13 2026-08-25 04:43 639232296255744174
107 ms 94.46.30.37
12 2026-08-25 04:26 639232286095760789
90 ms 94.46.30.37
11 2026-08-25 04:10 639232276086186273
101 ms 94.46.30.37
10 2026-08-25 03:53 639232265900986425
104 ms 94.46.30.37
9 2026-08-25 03:36 639232255723518075
88 ms 94.46.30.37
8 2026-08-25 03:19 639232245484452890
96 ms 94.46.30.37
7 2026-08-25 03:01 639232235157175331
49 ms 94.46.30.37
6 2026-08-25 02:08 639232203197189095
115 ms 94.46.30.37
5 2026-08-25 01:51 639232192844564298
120 ms 94.46.30.37
4 2026-08-25 01:34 639232182496008942
2007 ms 94.46.30.37
3 2026-08-25 01:16 639232172197053132
52 ms 94.46.30.37
2 2026-08-25 00:23 639232140250307418
49 ms 94.46.30.37
1 2026-08-25 00:06 639232129927860324
88 ms 94.46.30.37