|
| 1 | +# 2nd of Mar 2026 (1.61) |
| 2 | + |
| 3 | +- **ADDED** Added an Availability Test Results page showing the last 6 days of availability checks for the current site, giving customers a single place to review recent site health history. |
| 4 | + |
| 5 | +> This update is expected to be generally available on 2026-03-09. |
| 6 | +
|
| 7 | +## Highlights |
| 8 | + |
| 9 | +### Availability Tests |
| 10 | + |
| 11 | +Release highlight: Availability Test Results — your 6‑day site health timeline, all in one place |
| 12 | + |
| 13 | +#### What’s new |
| 14 | +We’ve added a new **Availability Test Results** page that shows the **last 6 days of availability checks for your current site**—a single, go-to place to review recent site health for your **DeskDirector** instance. |
| 15 | + |
| 16 | +#### Why we built it |
| 17 | +When something “looks off” (a brief outage report, a slow period, a certificate warning, a DNS hiccup), you shouldn’t have to piece together clues across tools or guess whether it was real or just a one-time blip. This page was created to make availability monitoring **transparent and actionable** by surfacing both **history** and **diagnostic detail** in one view. |
| 18 | + |
| 19 | +It also sets the foundation for what’s next: **a future publicly available status page** intended to display broader virtual machine health. But this release is intentionally different and more personal—**it’s focused on your own site**, and it includes deeper, per-check insight. |
| 20 | + |
| 21 | +#### How it improves everyday us |
| 22 | +With Availability Test Results, customers can quickly answer: *“Has my site been healthy lately?”* and *“What exactly failed?”*—without leaving the product. |
| 23 | + |
| 24 | +You can use it to: |
| 25 | +- **Review the last 6 days of checks** for your specific site in one timeline |
| 26 | +- **Drill into individual check results** for richer troubleshooting context, including: |
| 27 | + - **DNS resolution details** |
| 28 | + - **SSL certificate information** |
| 29 | + - **Failure response details** (e.g., failed request responses) |
| 30 | + |
| 31 | +This is especially helpful when diagnosing intermittent issues, confirming whether a problem is recurring, and deciding whether action is needed—or whether the site recovered on its own. |
| 32 | + |
| 33 | +**Availability testing behavior (so you know what to expect)** |
| 34 | +- **Test frequency** |
| 35 | + - **Platform / standard hostnames:** every **5 minutes** |
| 36 | + - **Custom domains:** every **6 hours** |
| 37 | +- **Alerts:** we alert on **2 consecutive failures** and investigate. **Single failures usually don’t require action.** |
| 38 | +- **Occasional single failures can be normal:** a one-off **timeout / 404** may occur during routine maintenance and typically recovers on the next run. |
| 39 | +- **Common maintenance windows** |
| 40 | + - **Daily database backup (off-peak):** may cause brief slowness/timeouts |
| 41 | + - **Weekly environment update:** |
| 42 | + - **9:00 AM Mon (NZT)** — US/CA/UK (NY Sun 3pm, LA Sun 12pm, London Sun 8pm) |
| 43 | + - **6:00 PM Sun (NZT)** — AU (Sydney Sun 4pm) |
| 44 | + |
| 45 | +#### Why you’ll love it |
| 46 | +This update turns availability monitoring into something you can **check in seconds**—with the detail you need when things go wrong, and the reassurance you want when they don’t. It’s a clearer, faster way to understand your site’s real-world health—and it puts recent history and diagnostics exactly where you need them: **inside your DeskDirector experience**. |
0 commit comments