GoZen Host Status Page
How to check server uptime, view incident reports, subscribe to status alerts, and read the response time metrics for GoZen Host infrastructure.
5 min read
Our public status page shows live uptime data, incident reports and scheduled maintenance for GoZen Host infrastructure.
Checking Server Status
The status page shows:
- Current status of the main systems (web hosting, email, DNS, VPS, control panels)
- Response time graphs for each service over time
- Recent incidents, with a post-mortem for significant ones
- Scheduled maintenance windows
Green means the service is operational, yellow means degraded performance, and red means a disruption.
Services We Monitor
| Service | What It Covers |
|---|---|
| Web Hosting | Shared hosting, WordPress hosting, cPanel servers |
| VPS / Cloud | VPS, AMD EPYC VPS (Business Cloud), Dedicated Servers |
| IMAP, SMTP, Webmail, spam filtering | |
| DNS | Authoritative nameservers, DNS resolution |
| Control Panels | cPanel/WHM, Enhance panel |
| Client Area | Billing portal, domain management |
| Status Page | The monitoring system itself |
Subscribing to Status Alerts
Subscribe and you’ll get an email when something changes, so you don’t have to keep checking the page.
How to Subscribe
- Visit status.gozenhost.com
- Click the “Subscribe to Updates” button in the hero section
- Enter your email address and click Subscribe
- If a confirmation email arrives, click the verification link in it
What Emails Will You Receive?
| Alert Type | When It’s Sent | What It Contains |
|---|---|---|
| Outage Alert | When a critical service goes down | Affected service, time detected, impact, link to live status |
| Degraded Performance | When a service is up but having problems | Service name and expected impact |
| Scheduled Maintenance | Before a planned maintenance window | Title, description, start and end times, expected duration, affected services |
| Resolution Confirmation | When an incident is resolved | Service restored, incident duration, root cause (if known), what was done |
Who should subscribe? Anyone who manages websites, applications or client services hosted with GoZen Host. If you’re a reseller, subscribing lets you tell your clients about an issue before they ask.
Managing Your Subscription
- Unsubscribe: every alert email has an Unsubscribe link in the footer
- Re-subscribe: visit the status page and enter the same email address again
- Not receiving alerts? Check your spam/junk folder and add
[email protected]to your contacts
Understanding Response Time Metrics
Each monitored service has response time data on the status page.
What Is Response Time?
Response time is how long a server takes to answer a monitoring probe, measured in milliseconds (ms).
Typical Response Times
| Service | Expected Response Time |
|---|---|
| Web hosting (static content) | Under 200ms |
| Web hosting (dynamic / PHP / WordPress) | Under 500ms |
| DNS resolution | Under 10ms |
| Email (SMTP) | Under 100ms |
| Control panel | Under 300ms |
Reading the Graphs
- Sparklines: the small charts next to each service show response time over the last 24 hours. A flat line near the baseline is what you want to see.
- Spikes: a short spike that drops back to the baseline is usually a brief network blip. These are normal and don’t always lead to an incident.
- Sustained elevation: if response time stays high for more than a few minutes, there’s probably a real performance problem and an incident may be opened.
Uptime Percentage
Our target is 99.9% uptime:
| Uptime | Allowed Downtime (per month) |
|---|---|
| 99.9% | 43 minutes |
| 99.95% | 21 minutes |
| 99.99% | 4.3 minutes |
Scheduled maintenance that was announced in advance doesn’t count as downtime. The SLA has the full terms and service credits.
Incident Reports
When something goes wrong, we post an incident on the status page and update it as the work progresses.
Incident Lifecycle
Each incident moves through these stages:
- Investigating - we’ve detected or received a report about the issue and are looking into it
- Identified - we’ve found the cause and are working on a fix
- Monitoring - a fix is in place and we’re watching to make sure the problem doesn’t come back
- Resolved - the service is fully restored and the incident is closed
What’s Included in an Incident Report
| Field | Description |
|---|---|
| Title | Short description of the problem |
| Status | Current stage (Investigating → Identified → Monitoring → Resolved) |
| Affected services | Which systems are affected |
| Updates | Timestamped entries as the situation changes |
| Duration | Time from detection to resolution |
Post-Incident Reviews
For significant incidents we publish a post-mortem with:
- Timeline - what happened, in order
- Root cause - what failed and why
- Impact - who was affected and how
- Follow-up - the changes we’re making so it doesn’t happen again
During an Active Incident
If the status page shows an active incident:
- Our engineers are already working on it, so you don’t need to open a ticket for the same issue
- Check the incident updates for an estimated resolution time
- Avoid changing your site configuration until the incident is resolved, since changes made while a service is unstable can cause new problems
- Subscribe for updates if you haven’t already, so you hear as soon as the service is back
If the status page shows everything operational but your site still has problems, the issue may be specific to your account. In that case, contact our support team.
Scheduled Maintenance
We schedule maintenance for security patches, hardware upgrades and infrastructure work.
How We Announce Maintenance
- A notice appears on the status page at least 24 hours in advance (longer for major work)
- Subscribers get an email with the start and end times and the expected impact
- The window is shown on the status page timeline
What Happens During Maintenance
| Maintenance Type | Typical Duration | Downtime Expected? |
|---|---|---|
| Security patches | 5–15 minutes | Usually no (rolling updates) |
| Software upgrades | 15–60 minutes | Brief, for the affected services |
| Hardware maintenance | 1–4 hours | Possible for the affected nodes |
| Network maintenance | 30–120 minutes | Possible brief interruptions |
| Infrastructure migration | 2–8 hours | Planned and announced well in advance |
Most maintenance happens during off-peak hours (typically 02:00–06:00 UTC) and needs no downtime. When a window does need brief downtime, the announcement says so.
After Maintenance
When the work is finished:
- The status page entry is marked Completed
- A short summary of what was done is posted
- Subscribers get a completion email
Useful Links
Related Articles
Last updated 21 Oct 2026, 00:00 +0300.