SaaS Status
Everything is up.
Business software rarely fails all at once. These products are assemblies of features, and an incident normally takes out one of them: search stops returning results, automations stop firing, notifications stop arriving, or exports stop completing, while the parts you happen to be looking at behave perfectly. That partiality is what makes a single up or down verdict least useful in this category.
Aggressive client-side caching hides problems further. Recently viewed documents and boards keep rendering from local state, so the first symptom is usually that your edits are not reaching anyone else rather than an error on screen. Suites that share an identity provider fail in the opposite direction: a single sign-in incident locks users out of several apparently unrelated products at once.
Automations and integrations are the quietest failure of all. They stop running without anyone receiving an error, and the absence is normally noticed downstream, when a record that should exist does not.
- up
- slow
- down
- no reading
AhrefsUp
AirtableUp
AsanaUp
Auth0Up
CalendlyUp
CanvaUp
ClerkUp
ConfluenceUp
DropboxUp
FigmaUp
Google MapsUp
Google Play StoreUp
HubSpotUp
JiraUp
monday.comUp
NotionUp
SalesforceUp
ShopifyUp
TrelloUp
ZapierUpCommon questions about SaaS products
Hard-refresh to bypass a stale cached asset, then try an incognito window to rule out an extension or a cookie. If it works in incognito, the service is fine and something in your normal browser session is the cause. Failing identically on another device and network points at the service.
Often yes. These clients cache heavily and queue writes, so a sync failure shows up as your edits looking saved locally while never reaching anyone else. Reload in a private window to see the server's actual state, and avoid making further edits until sync recovers, so you do not build on work that may be lost.
They almost certainly share an identity provider. A single sign-on outage blocks new logins across every product that depends on it, while people with a valid session often carry on unaffected, which is why the problem can look like it is only happening to some colleagues.