Open the System Status page in my.cubepath.com to see the live operational status of CubePath services. The page refreshes on its own every couple of minutes.
Overview
At the top, a banner sums up the platform: All Systems Operational, Minor Issues, Service Degradation or Critical Issues, alongside the 30-day uptime percentage and a count of active incidents and upcoming maintenance.
Below it, an Uptime bar shows the last 90 days per service — VPS, Dedicated Servers, Network, DNS and API. Each day is a coloured cell:
| Cell | Meaning |
|---|---|
| Operational | No issues |
| Maintenance | A maintenance window touched the service |
| Degraded | A minor or medium incident |
| Outage | A high or critical incident |
Hover any cell to see that day's incident and maintenance count.
Tabs
- Current Status — active incidents and maintenance happening right now.
- Scheduled Maintenance — upcoming planned windows, with start and end times (UTC), affected services and location.
- History — resolved incidents from the last 30 days and recently completed maintenance.
Reading an incident
Each incident shows its severity (low to critical), its state (Investigating, Identified, Monitoring or Resolved), the affected services, the location and when it started. Expand it to read the chronological updates posted by our team.
NoteMaintenance can be planned or flagged Emergency. All event times are shown in UTC.
Check here first
When something breaks, this page answers "is it me?" before you spend an hour on it. If your service is listed as degraded, the fix is already in progress and there's nothing to report. If everything is operational, the problem is on your side — start with the resource's own Activity tab, which records every change made to it.
Contacting support
| Channel | Best for |
|---|---|
| Support ticket in the dashboard | Technical issues, billing, account requests |
| [email protected] | Technical support and general inquiries |
| [email protected] | Pre-sales questions, custom plans, partnerships |
Opening a ticket from the dashboard is the better path for anything account-related: it arrives already tied to your organization, so nobody has to establish who you are before helping you.
Writing a request that gets answered fast
Most of the delay in support is the round trip to gather basic facts. Include them up front:
- Which resource — the server name or ID, the IP, the zone.
- What you expected and what happened instead, with the exact error message.
- When it started, and whether anything changed just before.
- What you already tried.
"VPS #12345 (203.0.113.10) stopped answering on port 443 at 14:20 UTC today, right after I applied a firewall group. Nothing in the Activity log since. Rules attached." beats "my server is down" by hours.
Support levels and response times
Requests are classified by complexity and urgency. The SLA is the maximum response time for each level:
| Level | Availability | First response | Business hours | After hours | Weekends |
|---|---|---|---|---|---|
| Urgent (paid) | 24/7 | 5 min | 15–60 min | 15–60 min | 15–60 min |
| Level 1 | 24/7 | 5–15 min | up to 30 min | up to 30 min | up to 30 min |
| Level 2 | Per schedule | 5–15 min | 1–2 h | 6–8 h | up to 12 h |
| Level 3 | Per schedule | 5–15 min | up to 12 h | 12–24 h | 24–48 h |
| Datacenter | Per schedule | 5–15 min | 1–2 h | 4–8 h* | 8–10 h* |
Business hours are Monday–Friday 09:00–18:00; after hours are Monday–Friday 18:00–09:00; weekends are Saturday and Sunday. *Datacenter response outside business hours varies by location.
What lands at each level
| Level | Typical requests |
|---|---|
| Urgent | Complete production outage, critical security incidents, business-critical issues needing immediate attention |
| Level 1 | General questions, basic connectivity, service status, basic configuration guidance |
| Level 2 | OS reinstalls, IPMI access, network routing, performance tuning, DDoS profile adjustments |
| Level 3 | Major outages, critical infrastructure failures, core network problems, complex architectural changes |
| Datacenter | Hardware replacement and repairs, physical interventions on site |
TipSay plainly in the ticket what the business impact is. "Production is down for all customers" and "a staging box won't boot" get triaged very differently, and only you can tell us which one it is.