System status & incidents
The System status page (at /status) shows whether Themeasy Hub and its services are running
normally. Check it first whenever something seems off — if there's a known incident, you'll see it
here before you need to report it.
The status pill in the footer
You don't have to open the page to know how things are: the footer of every Hub page carries a live status pill. It reads All systems operational with a green dot when everything is healthy, and switches to Degraded performance, Partial outage or Major outage when something isn't. Click it to open the status page. You can also get here from Status in the sidebar, System status in the footer, or the Support page.
The overall banner
At the top of the page, a single coloured banner sums up the health of every service at a glance:
| Banner | What it means |
|---|---|
| All systems operational | Everything is running normally — no known issues. |
| Degraded performance / Partial outage | At least one service is slow or partly unavailable. |
| Major outage | At least one service is fully down. |
The banner always reflects the most serious component status, so if any single service is degraded or down, the overall banner changes colour to match.
Components
Under Components you'll find each service we monitor listed individually, each with its own status badge:
| Status | Meaning |
|---|---|
| Operational | Working normally. |
| Degraded performance | Available but slower or less reliable than usual. |
| Partial outage | Some requests or features are failing. |
| Major outage | The service is fully unavailable. |
This breakdown lets you tell at a glance whether the thing you're trying to do — sign in, download a file, manage a license — is the part that's affected.
Incidents
When something goes wrong, the team opens an incident and posts updates as they work through it.
- Active incidents appear in their own section near the top, each with a title, a severity label (Minor, Major, or Critical), and an update timeline read newest first. Each entry in the timeline is tagged with its phase — Investigating, Identified, Monitoring, or Resolved — and timestamped, so you can follow the response as it unfolds.
- Past incidents (last 30 days) lists incidents that have already been resolved, so you can see what recently happened. A closed incident is marked Resolved in its header.
No incidents is good news
If there's nothing wrong, the active-incidents section is hidden and Past incidents simply reads "No incidents in the last 30 days." That means every service is healthy.
Staying informed
You don't have to keep refreshing the page — there are two ways to be notified when an incident is opened or resolved:
- Subscribe by email. In the Get notified card at the bottom of the page, enter your email address (it's filled in for you when you're signed in) and press Subscribe. You'll then "receive email updates when an incident is opened or resolved." Every email includes an unsubscribe link. You don't need a Hub account to subscribe.
- Follow the RSS feed. Use the RSS button at the top of the page (or the feed at
/status/rss.xml) to track incidents in your feed reader.
Tip
Bookmark /status and check it the moment something feels off — a known incident here saves you from
opening a ticket for a problem the team is already on.
Status vs. a support ticket
The status page is for service-wide problems that affect everyone. If a service shows Operational but something still isn't working for you — a download that won't start, a license that won't activate, a charge you don't recognise — that's account-specific, so open a private support ticket rather than waiting on a status incident.
Related
Was this article helpful?