See exactly how reliable UniLink has been — past incidents, root causes, and what uptime percentages actually mean for your page.
- UniLink publishes a rolling 90-day uptime history at status.unilink.us/history with per-component breakdowns.
- 99.9% uptime means roughly 8.7 hours of potential downtime per year — understanding this helps set realistic expectations.
- Pro and Business plans include SLA guarantees; free and Starter users can still monitor status and subscribe to incident alerts.
Every platform experiences occasional hiccups, and UniLink is no exception. The difference is transparency: UniLink maintains a public status page where anyone can review historical availability data, read post-incident analyses, and understand exactly what happened during any outage. Whether you're an agency evaluating reliability for a client proposal or a creator who noticed a slow page last Tuesday, the uptime history page gives you the full picture.
What Uptime History Does
The uptime history feature at status.unilink.us/history provides a 90-day rolling record of system availability across every major UniLink component. Each component — the main dashboard at app.unilink.us, user pages at unil.ink, the API, and the CDN — is tracked independently. This means a brief issue with the dashboard won't show up as downtime on your public-facing unil.ink page, giving you a granular view rather than a misleading single uptime number.
Each incident in the history log includes a timeline: when the issue was first detected, when it was acknowledged, what mitigations were applied, and when full service was restored. For significant outages, UniLink publishes a root cause analysis (RCA) that explains what went wrong at a technical level and what changes were made to prevent recurrence. These RCA posts are linked directly from the incident entry so you can read the full explanation without digging through support channels.
The 90-day window is intentional. It covers three full billing cycles, giving paid users a meaningful look at reliability before renewing or upgrading. Uptime percentages are calculated as total minutes of availability divided by total minutes in the period, excluding scheduled maintenance windows that were announced at least 24 hours in advance.
How to Get Started
- Navigate to status.unilink.us in any browser — no login required. The current status of all components is shown at the top of the page.
- Click Uptime History in the top navigation or scroll to the history section below the current status panel.
- Review the color-coded timeline grid. Green squares indicate full availability, yellow indicates degraded performance, and red indicates a confirmed outage during that time block.
- Click any colored square or incident label to expand the full incident report, including the timeline and any root cause analysis that has been published.
- Click Subscribe to Updates to receive email or SMS notifications the moment a new incident is opened or updated — so you're never caught off guard.
How to Use Uptime History
- Use the component filter at the top of the history page to isolate the service most relevant to you. If your concern is visitor page performance, focus on the "User Pages (unil.ink)" component rather than the dashboard.
- Click Export CSV to download the full 90-day incident log. The CSV includes incident ID, start time, end time, duration, affected components, and status. Import this into a spreadsheet for custom uptime calculations.
- Compare the uptime percentage shown against your plan's SLA. Pro and Business accounts can cross-reference any SLA credit eligibility using the incident durations in the exported data.
- Read the root cause analysis for any major incident. RCAs are typically published within 5 business days and include a "What We Changed" section — useful if you're reporting to a stakeholder who wants assurance the issue won't recur.
- Bookmark the history page and check it before contacting support about a slow page. Many reported issues are already documented as resolved incidents, saving you time waiting for a ticket response.
Key Settings
| Setting | What It Does | Recommended |
|---|---|---|
| Email Notifications | Sends an alert when a new incident is opened or its status changes | Enable for all paid-plan users |
| SMS Notifications | Delivers a text message for critical outages affecting user pages | Enable if you run high-traffic pages |
| Component Filter | Limits the history view and notifications to specific services | Select "User Pages" + "API" for most users |
| CSV Export Range | Choose 7, 30, or 90 days when exporting incident data | 90 days for SLA reviews, 30 days for monthly reports |
| Scheduled Maintenance Alerts | Notifies you of upcoming planned maintenance windows in advance | Enable to plan around maintenance windows |
Get the Most Out Of Uptime History
The most valuable use of the history page isn't checking on past problems — it's establishing a baseline for your own monitoring. Cross-reference UniLink's uptime data with your own analytics. If you see a traffic drop in your UniLink analytics on a date that also has a yellow or red square in the history grid, you have a documented explanation. This is especially useful for e-commerce sellers on the Pro and Business plans who need to account for revenue dips in reporting.
SLA eligibility on Pro and Business plans is tied to confirmed incident durations as recorded on the status page. If a single incident caused more than the SLA threshold of downtime in a billing month, you may be eligible for service credits. The process starts with the exported CSV: find incidents that fall within your billing period, sum the durations for affected components, and compare against your plan's SLA terms. Contact support with the incident IDs and they can process the credit without requiring you to prove the outage independently.
For agencies managing multiple client pages, the history page is a shared resource — you don't need separate accounts to check it. Bookmark it, share the link with clients, and reference it proactively when discussing platform reliability. Clients who see that UniLink publishes transparent incident reports are generally more confident in the platform than clients who only hear about outages after the fact.
Scheduled maintenance windows appear in the history timeline marked distinctly from unplanned incidents. UniLink typically schedules maintenance during low-traffic hours (02:00–04:00 UTC) and announces windows at least 48 hours in advance via the status page and subscriber notifications. If you're running a time-sensitive campaign, check the status page for any upcoming windows before launch day so you can adjust your schedule if needed.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| History page shows no incidents but my page was slow | Degraded performance below the incident threshold is not always logged as an outage | Check the "Degraded Performance" entries in addition to outage entries; contact support with a timestamp if nothing matches |
| CSV export is empty or incomplete | No incidents occurred in the selected range, or a browser extension is blocking the download | Disable ad blockers temporarily, try a different browser, or select a wider date range |
| Not receiving incident email notifications | Subscription confirmation email was missed or notifications landed in spam | Re-subscribe on the status page and whitelist [email protected] in your email client |
| Uptime percentage seems lower than expected | The 90-day calculation includes all incidents, even very short ones under 5 minutes | Export the CSV and filter incidents under 5 minutes duration to see the "meaningful" uptime figure |
- Full 90-day rolling history is publicly accessible without a login
- Per-component tracking distinguishes dashboard issues from user-page outages
- Root cause analyses provide actionable explanations, not just status updates
- CSV export enables custom SLA calculations and stakeholder reporting
- SLA credits and guaranteed uptime are only available on Pro and Business plans
- History older than 90 days is not publicly accessible
- Short degradation events under the incident threshold may not appear in the log
Frequently Asked Questions
What does 99.9% uptime actually mean in practice?
99.9% uptime over a full year equals approximately 8.76 hours of total downtime. Over a single month, it equals roughly 43 minutes. UniLink's uptime history page shows your actual experienced uptime per component so you can compare it against this benchmark directly.
Does the history page show downtime for user pages specifically?
Yes. The "User Pages (unil.ink)" component is tracked separately from the dashboard and API. You can filter the history grid to show only that component, giving you an accurate view of what your visitors actually experienced.
How do I claim an SLA credit if I experienced significant downtime?
Export the 90-day incident CSV, identify incidents within your billing period, and sum the durations for the affected component. Then contact UniLink support via the dashboard with the incident IDs and your account email. SLA credits are processed within one billing cycle and appear as a deduction on your next invoice.
Can I see historical uptime beyond 90 days?
The public history page shows 90 days. If you need older records — for example, for a contractual audit — contact UniLink support directly. Enterprise-tier Business accounts can request extended incident history as part of their account documentation.
Are scheduled maintenance windows counted as downtime?
No. Scheduled maintenance windows that were announced at least 24 hours in advance are excluded from uptime calculations. They appear in the history timeline with a distinct "Maintenance" label so you can distinguish them from unplanned incidents.
- The full 90-day uptime history is available publicly at status.unilink.us/history — no account needed.
- 99.9% uptime means up to ~8.7 hours of downtime per year; the history page shows your actual figure per component.
- Export the incident CSV to calculate SLA eligibility and produce stakeholder-ready reliability reports.
- Subscribe to notifications so you learn about incidents immediately rather than discovering them from visitors.
- Root cause analyses linked from each major incident explain what changed so you can assess whether the fix holds.
Check UniLink's current status and browse the full incident history at status.unilink.us. Ready to get started with a plan that includes SLA guarantees? Compare plans at unilink.us/pricing.