Cloud Services

One row per cloud service your office depends on — Webex, Zoom, Slack, Ubiquiti, Cloudflare, GitHub, Microsoft 365, Google Workspace, AWS, Claude and OpenAI — read from each service’s own public status page.

Trouble sorts to the top. A major outage outranks a minor issue, and both outrank everything healthy, so the row that matters is never hidden behind a “+N”. When all is quiet the card shows your own chosen order. A degraded service prints one line per incident — when Microsoft has three products down, you see all three without tapping.

Tap anywhere on the card for the full ledger: troubled services first with their status text in full, everything healthy in quiet columns beneath. The card always opens, whether or not it is showing a “+N” count, because the ledger is the only place a service’s status text appears uncut.

Microsoft 365 advisories

Microsoft separates its own service issues into two kinds. An incident is a live problem people can feel, such as mail not arriving. An advisory is a narrower known issue, and Microsoft often leaves one open for weeks or months.

Only incidents color the Microsoft 365 row. Advisories are listed under their own heading when you tap the card, with the workload, the feature Microsoft names, and the date each one opened. Without that split the row would report a problem more or less permanently, because there is nearly always an advisory open somewhere in Microsoft 365.

A service interruption is never quieted this way. If Microsoft says people cannot reach a service, the row says so whatever the issue is labelled.

Sizing

The card suggests a height that fits the services you follow, and you can drag it taller than that. A single service having a bad day prints a line per affected product, so the room a card needs depends on what its services are saying, not just how many you track.

Configure

Settings → Cloud Services. Toggle services on and off. The card starts with Webex, Slack and Microsoft 365.