Overview

Before opening a support ticket about the dashboard being slow, a finder not running, or a fixer not executing, check the CloudFix status page — it's the fastest way to find out whether an issue is already known and being worked. This article explains what's published there and when to check it.

Information

Where to Check

Current status is published at trust.cloudfix.com/status, on the CloudFix Trust Center.

What's on the Status Page

• Overall status — a single indicator (All Systems Operational, Degraded, or Outage) for CloudFix as a whole.
• Service components — individual status and 30-day uptime for each core piece of the platform (for example, the CloudFix Dashboard, the Finder engine, Fixer execution via AWS Systems Manager, AWS account integration, and the Reporting & Analytics API), so you can tell whether a problem is platform-wide or limited to one area.
• 30-day uptime history — a day-by-day bar showing operational, degraded, or outage status over the trailing 30 days.
• Incident history — write-ups of past incidents and scheduled maintenance windows, including what happened, the time window affected, root cause where known, and resolution.
• Service Level Agreement summary — the target uptime commitment and what's excluded from it (scheduled maintenance, AWS infrastructure issues, force majeure).

When to Check It

• Before filing a ticket for something that looks like an outage or broad slowdown — the status page updates within 30 minutes of a confirmed service incident, so if something has already been detected, it will usually show there before you finish writing a ticket.
• While an incident is in progress, to follow updates without needing a reply on your own ticket.
• After an incident, to read the resolution write-up and confirm whether it affected the specific service component you use.
• Around a scheduled maintenance window — maintenance is announced at least 72 hours in advance and typically runs 02:00–04:00 UTC.

If the status page shows all systems operational but you're still seeing a problem, it's likely account- or configuration-specific rather than a platform-wide issue — open a support ticket via support.cloudfix.com so it can be investigated directly. See CloudFix Support: SLA, Severity Levels, and Escalation for response and resolution targets.

Frequently Asked Questions

Q: Do I need an account to view the status page?
A: No. trust.cloudfix.com/status is public and doesn't require logging in to CloudFix.

Q: How current is the information on the status page?
A: The overall indicator reflects current status, and confirmed service incidents are posted within 30 minutes of detection. The 30-day uptime bar and incident history are historical records, not live monitoring feeds.

Q: Is the status page the same as getting notified about an incident?
A: Not automatically — the status page is something you check. If you're directly affected by a P1/P2 service incident, CloudFix also notifies you via in-app notification and/or email, separately from the status page update.

Q: Should I still open a support ticket if I see an incident already listed?
A: If your issue matches an incident already posted, you don't need to file a separate ticket for it — the write-up will be updated as it's resolved. If what you're seeing doesn't match anything listed, open a ticket so it can be looked at individually.