diumSystem status, without the guesswork.
Which parts of Dium we watch, how we tell you about problems, and where live status will appear.
What we will monitor.
Six components, matching how Dium is built. Several depend on services shared with other TAO.ai products, named here so you know where a problem might start.
| Component | What it covers | Public status |
|---|---|---|
| Web app | Flows, Waves, replies, Pages and search at dium.io. Depends on: Dium servers and our database service | Not yet monitored publicly |
| API | The partner API and the calls the app makes behind the scenes. Depends on: Dium servers and our database service | Not yet monitored publicly |
| Real-time (Echo) | Instant updates for new replies, messages, typing and live banners. If it is down, the app falls back to checking every 60 seconds. Depends on: Echo real-time service | Not yet monitored publicly |
| Email delivery | Email invitations and daily or weekly digests. Depends on: Our email delivery service | Not yet monitored publicly |
| Sign-in (Moat and Werify) | Email code sign-in, single sign-on, and profile names and photos. Depends on: Moat (identity) and Werify (sign-in) | Not yet monitored publicly |
| Payments (Werify Paywall) | Upgrading a Flow and confirming payments. Depends on: Werify Paywall | Not yet monitored publicly |
How we tell you about an incident.
Every incident moves through four stages. Each update says what we know, who is affected and when the next update comes.
Investigating
We know something is wrong and are finding out what. We say which parts of Dium seem affected.
Identified
We found the cause and are working on a fix. We say what you can do in the meantime.
Monitoring
A fix is in place and we are watching to make sure it holds.
Resolved
Service is back to normal. For larger incidents we publish a short write-up of what happened and what we changed.
Times in UTC
All incident times are in UTC, so there is one clock for everyone, wherever your members are.
Until the page is live
We email the owners of affected Flows directly and answer questions at [email protected].
Security issues
Report a suspected vulnerability privately to [email protected], not on a public page.
Get incident updates by email.
Leave your address and we will add you to status notifications when status.dium.io goes live. Until then, we will email you about incidents ourselves.
Prefer a feed? The changelog has an Atom feed for product updates.
You are subscribed
We will email you when an incident affects Dium, and when it is resolved.