DNS response history for pns11.spectator-healthcare.com

pns11.spectator-healthcare.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 18 DNS check records, 18 successful responses, 0 failed responses, and 256 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 pns11.spectator-healthcare.com.
Records on Selected Date

18

Historical checks stored for this nameserver on selected date

Average Latency

256 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 06:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.96.133

Most recently resolved hosting IP on selected date

Successful Responses

18

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 pns11.spectator-healthcare.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
18 2026-08-25 06:03 639232346196373643
5 ms 185.136.96.133
17 2026-08-25 05:46 639232336112370741
18 ms 185.136.96.133
16 2026-08-25 05:30 639232326146508970
33 ms 185.136.96.133
15 2026-08-25 05:13 639232316189381720
25 ms 185.136.96.133
14 2026-08-25 04:57 639232306217998913
48 ms 185.136.96.133
13 2026-08-25 04:40 639232296255744174
25 ms 185.136.96.133
12 2026-08-25 04:23 639232286095760789
117 ms 185.136.96.133
11 2026-08-25 04:06 639232276086186273
34 ms 185.136.96.133
10 2026-08-25 03:49 639232265900986425
2075 ms 185.136.96.133
9 2026-08-25 03:32 639232255723518075
7 ms 185.136.96.133
8 2026-08-25 03:15 639232245484452890
8 ms 185.136.96.133
7 2026-08-25 02:58 639232235157175331
97 ms 185.136.96.133
6 2026-08-25 02:05 639232203197189095
9 ms 185.136.96.133
5 2026-08-25 01:48 639232192844564298
7 ms 185.136.96.133
4 2026-08-25 01:30 639232182496008942
2014 ms 185.136.96.133
3 2026-08-25 01:13 639232172197053132
8 ms 185.136.96.133
2 2026-08-25 00:20 639232140250307418
42 ms 185.136.96.133
1 2026-08-25 00:03 639232129927860324
33 ms 185.136.96.133