Skip to main content
When something isn’t working as expected, the status page is always your first stop. fsckmsft publishes real-time service health information and detailed incident updates so you always know what’s happening and when to expect a fix.
Check the live status page at status.fsckmsft.org before filing a support ticket — your issue may already be a known incident under active investigation.

​
The fsckmsft status page

Visit status.fsckmsft.org to see the current operational status of every fsckmsft service component, including:
  • Web application — the main app at app.fsckmsft.org
  • API — REST and webhook endpoints
  • Automations — background workflow execution
  • Authentication — login, SSO, and 2FA
  • Notifications — email and in-app alerts
  • Data exports — export pipeline and delivery
Each component displays one of four states: Operational, Degraded Performance, Partial Outage, or Major Outage.

​
Subscribe to incident notifications

Stay informed without having to refresh the status page manually.
1

Open the status page

Go to status.fsckmsft.org.
2

Click 'Subscribe to Updates'

Find the Subscribe to Updates button in the top-right corner of the page.
3

Choose your notification channel

Select Email to receive updates in your inbox, or select Slack to post updates to a Slack channel of your choice. For Slack, you’ll be prompted to authorise the fsckmsft status app in your workspace.
4

Confirm your subscription

For email, confirm your address by clicking the verification link we send you. For Slack, choose the channel where you want notifications posted and click Allow.
Business plan customers can subscribe a shared team email address (e.g. ops@yourcompany.com) so your entire on-call team receives incident alerts simultaneously.

​
How to read incident updates

Every incident goes through a defined lifecycle. Understanding each status helps you gauge severity and expected resolution time.
StatusWhat it means
InvestigatingWe have detected a problem and are actively diagnosing the root cause. Impact scope is not yet fully known.
IdentifiedThe root cause has been identified. We are working on a fix or mitigation.
MonitoringA fix has been deployed. We are monitoring the system to confirm the issue is fully resolved.
ResolvedThe incident is fully resolved. All systems are back to normal operation. A post-mortem may be published for major incidents.
Each status update includes a timestamp and a plain-language description of what our team has found and what action is being taken. Updates are posted at least every 30 minutes during active incidents.

​
What to do during an incident

1

Check the status page first

Before doing anything else, visit status.fsckmsft.org. If an incident is already posted, our team is aware and working on it.
2

Subscribe for updates

Subscribe via email or Slack so you receive updates automatically rather than having to check manually.
3

Avoid filing duplicate tickets

If the incident is already listed on the status page, do not file a separate support ticket for the same issue. Duplicate tickets consume support capacity that our team needs to focus on resolution.
4

File a ticket only if your issue is not listed

If you’re experiencing a problem that doesn’t match any active incident — or if your issue persists after an incident is marked Resolved — then file a support ticket with details. See Contact Support for guidance on writing an effective request.
If you are on a Business plan and experiencing a critical production outage that is not reflected on the status page, contact your account manager or use your dedicated Slack channel immediately rather than waiting for the standard ticket queue.

​
Post-mortems

For significant incidents (Partial Outage or Major Outage lasting more than one hour), fsckmsft publishes a post-mortem report within five business days of resolution. Post-mortems are linked from the incident entry on the status page and include:
  • A timeline of events
  • Root cause analysis
  • Impact summary
  • Remediation steps taken
  • Measures implemented to prevent recurrence