System Status
Updated · Multi Post Social guide
This page shows the current state of each part of Multi Post Social and the history of incidents. It is updated by the team during an incident and reviewed after every release. If a scheduled post did not go out and everything here is operational, the cause is usually a channel that needs a reconnect; the customer care guide walks through that fix.
Current status
All systems operational.
| Component | Status | What it covers |
|---|---|---|
| Website and sign-in | Operational | The marketing site, login, registration and password flows |
| Publishing | Operational | The queue, scheduled posts and reminders |
| Inbox sync | Operational | Collecting comments, messages and mentions from connected channels |
| Analytics collection | Operational | Fetching metrics from networks and building reports |
| Listening | Operational | Stream updates and alerts |
| API and webhooks | Operational | REST endpoints, webhook deliveries and the MCP server |
| Billing | Operational | Checkout, invoices and plan changes |
| Network | Status | Note |
|---|---|---|
| Operational | Direct publishing; some formats by reminder | |
| Operational | Direct publishing; some formats by reminder | |
| TikTok | Operational | Direct publishing |
| Operational | Direct publishing | |
| X (Twitter) | Operational | Direct publishing |
| YouTube | Operational | Direct publishing |
| Threads | Operational | Direct publishing |
| Operational | Direct publishing | |
| Google Business Profile | Operational | Direct publishing |
| Bluesky | Operational | Direct publishing |
| Mastodon | Operational | Direct publishing |
| Substack | Operational | Direct publishing |
A network marked degraded means that network's own API is slow or rejecting requests; posts are retried automatically and you are notified if a retry fails.
Incident history
No incidents reported since launch (October 27, 2026).
When an incident occurs, this section lists the date, the affected components, what users saw, the timeline of the response and what we changed afterwards. Scheduled maintenance is announced here at least 48 hours in advance.
Subscribe to updates
- Account owners receive incident emails automatically for the components their workspace uses; adjust in Settings → Notifications.
- Webhook users receive a
channel.disconnectedevent when a network connection fails, independent of platform-wide incidents. - Releases and improvements are listed on the changelog, not here.
How status is measured
Each component is checked from several regions every minute. Publishing is marked degraded when more than 2% of posts due in the last 15 minutes failed for a platform reason rather than a network token problem. Inbox sync and analytics collection are marked degraded when data is more than 30 minutes behind. A network connection is marked degraded when that network’s API returns errors for more than 5% of requests, which usually means the network itself is having trouble; we link to the network’s own status page in those incidents when one exists.
If something looks wrong for you but this page shows Operational, the cause is usually local: an expired channel token, a rejected file or a browser extension blocking requests. The customer care guide lists those fixes first.