GoZen Host Status Page
How to check server uptime, view incident reports, subscribe to status alerts, and understand response time metrics for GoZen Host infrastructure.
We maintain a public status page that shows real-time uptime data, incident reports, and scheduled maintenance for all GoZen Host infrastructure.
Checking Server Status
The status page shows:
- Current status of all major systems (web hosting, email, DNS, VPS, control panels)
- Response time graphs showing server performance over time
- Recent incidents with full post-mortems
- Scheduled maintenance windows
A green indicator means the service is operational. Yellow means degraded performance. Red means a service disruption.
Services We Monitor
| Service | What It Covers |
|---|---|
| Web Hosting | Shared hosting, WordPress hosting, cPanel servers |
| VPS / Cloud | Cloud VPS, Dedicated VPS, 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
Don’t check the page manually - subscribe and get notified automatically.
How to Subscribe
- Visit status.gozenhost.com
- Click the “Subscribe to Updates” button in the hero section
- Enter your email address and click Subscribe
- Check your inbox for a confirmation email (if double opt-in is enabled, click the verification link)
What Emails Will You Receive?
| Alert Type | When It’s Sent | What It Contains |
|---|---|---|
| Outage Alert | Immediately when a critical service goes down | Affected service, time detected, impact description, link to live status |
| Degraded Performance | When a service is still up but experiencing issues | Service name, expected impact, what to expect |
| Scheduled Maintenance | In advance of planned maintenance windows | Title, description, start/end times, expected duration, affected services |
| Resolution Confirmation | When an incident is resolved | Service restored, incident duration, root cause (if available), resolution summary |
Who should subscribe? Anyone who manages websites, applications, or client services hosted with GoZen Host. If you’re a reseller, subscribe so you can proactively inform your clients.
Managing Your Subscription
- Unsubscribe: every alert email includes 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
status@gozenhost.comto your contacts
Understanding Response Time Metrics
The status page displays response time data for each monitored service. Here’s how to read it.
What Is Response Time?
Response time measures how long it takes our servers to respond to a monitoring probe - essentially, how fast the server acknowledges a request. It’s 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: small inline charts next to each service showing response time over the last 24 hours. A flat line near the baseline is ideal.
- Spikes: short upward spikes followed by a return to baseline usually indicate transient network conditions that resolved automatically. These are normal and do not always trigger an incident.
- Sustained elevation: if the response time stays elevated for more than a few minutes, it typically indicates a real performance issue and an incident may be opened.
Uptime Percentage
Our target is 99.9% uptime across all services:
| Uptime | Allowed Downtime (per month) |
|---|---|
| 99.9% | 43 minutes |
| 99.95% | 21 minutes |
| 99.99% | 4.3 minutes |
Scheduled maintenance windows are not counted as downtime.
Incident Reports
When something goes wrong, we publish incident reports on the status page so you always know what’s happening.
Incident Lifecycle
Every incident follows this process:
- Investigating - we’ve detected or received a report about the issue and are looking into it
- Identified - we’ve found the root cause and are working on a fix
- Monitoring - a fix has been applied and we’re watching to make sure the problem doesn’t return
- Resolved - the service is fully restored and the incident is closed
What’s Included in an Incident Report
| Field | Description |
|---|---|
| Title | Brief description of what’s happening |
| Status | Current phase (Investigating → Identified → Monitoring → Resolved) |
| Affected services | Which systems are impacted |
| Updates | Timestamped entries as the situation evolves |
| Duration | Total time from detection to resolution |
Post-Incident Reviews
For significant incidents, we publish a detailed post-mortem including:
- Timeline - detailed sequence of events
- Root Cause Analysis - what failed and why
- Impact Assessment - who was affected and how
- Lessons Learned - what we’ll do differently
- Action Items - specific improvements we’re making
During an Active Incident
If the status page shows an active incident:
- Don’t panic. Our engineering team is already working on it
- Check the incident updates for an estimated resolution time
- Avoid making changes to your site configuration while an incident is active - changes during instability can create additional problems
- Subscribe for updates if you haven’t already, so you know the moment service is restored
If the status page shows all systems operational but your site is still having issues, the problem may be specific to your account. In that case, contact our support team.
Scheduled Maintenance
We periodically perform maintenance for security patches, hardware upgrades, and infrastructure improvements.
How We Communicate Maintenance
- A notice appears on the status page at least 24 hours in advance (longer for major maintenance)
- Subscribers receive an email notification with start/end times and expected impact
- The maintenance window is visible 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 affected services |
| Hardware maintenance | 1–4 hours | Possible for affected nodes |
| Network maintenance | 30–120 minutes | Possible brief interruptions |
| Infrastructure migration | 2–8 hours | Planned, communicated well in advance |
Most maintenance is performed during off-peak hours (typically 02:00–06:00 UTC) and requires zero downtime. If a maintenance window requires brief downtime, it will be clearly communicated in advance.
After Maintenance
Once maintenance is complete:
- The status page is updated to Completed
- A brief summary is posted describing what was done
- Subscribers receive a resolution notification
Useful Links
Related Articles
Last updated 21 Apr 2026, 08:08 +0300.