DNS response history for ns1.primedesign.info

ns1.primedesign.info 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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 250 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.primedesign.info.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

250 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 05:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.173.117.205

Most recently resolved hosting IP on selected date

Successful Responses

36

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.primedesign.info

Showing DNS history for 2026-08-26 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
36 2026-08-26 05:28 639233182401183833
4 ms 216.173.117.205
35 2026-08-26 05:28 639233182401183833
4 ms 194.50.200.120
34 2026-08-26 05:11 639233172074181051
189 ms 194.50.200.120
33 2026-08-26 05:11 639233172074181051
189 ms 216.173.117.205
32 2026-08-26 04:54 639233161808421455
441 ms 194.50.200.120
31 2026-08-26 04:54 639233161808421455
441 ms 216.173.117.205
30 2026-08-26 04:37 639233151357344052
120 ms 216.173.117.205
29 2026-08-26 04:37 639233151357344052
120 ms 194.50.200.120
28 2026-08-26 04:19 639233141034116946
48 ms 194.50.200.120
27 2026-08-26 04:19 639233141034116946
48 ms 216.173.117.205
26 2026-08-26 04:02 639233130828334142
39 ms 216.173.117.205
25 2026-08-26 04:02 639233130828334142
39 ms 194.50.200.120
24 2026-08-26 03:45 639233120373450007
396 ms 216.173.117.205
23 2026-08-26 03:45 639233120373450007
396 ms 194.50.200.120
22 2026-08-26 03:28 639233110066216193
100 ms 216.173.117.205
21 2026-08-26 03:28 639233110066216193
100 ms 194.50.200.120
20 2026-08-26 02:34 639233078065410564
60 ms 216.173.117.205
19 2026-08-26 02:34 639233078065410564
60 ms 194.50.200.120
18 2026-08-26 02:17 639233067787457832
8 ms 216.173.117.205
17 2026-08-26 02:17 639233067787457832
8 ms 194.50.200.120
16 2026-08-26 02:00 639233057501801162
74 ms 216.173.117.205
15 2026-08-26 02:00 639233057501801162
74 ms 194.50.200.120
14 2026-08-26 01:43 639233047089431703
61 ms 194.50.200.120
13 2026-08-26 01:43 639233047089431703
61 ms 216.173.117.205
12 2026-08-26 01:26 639233036754790688
114 ms 216.173.117.205
11 2026-08-26 01:26 639233036754790688
114 ms 194.50.200.120
10 2026-08-26 01:09 639233026412602472
2099 ms 216.173.117.205
9 2026-08-26 01:09 639233026412602472
2099 ms 194.50.200.120
8 2026-08-26 00:51 639233016064066127
222 ms 194.50.200.120
7 2026-08-26 00:51 639233016064066127
222 ms 216.173.117.205
6 2026-08-26 00:34 639233005922655772
314 ms 216.173.117.205
5 2026-08-26 00:34 639233005922655772
314 ms 194.50.200.120
4 2026-08-26 00:17 639232995672256907
100 ms 194.50.200.120
3 2026-08-26 00:17 639232995672256907
100 ms 216.173.117.205
2 2026-08-26 00:00 639232985300872416
114 ms 216.173.117.205
1 2026-08-26 00:00 639232985300872416
114 ms 194.50.200.120