Is Synacl down? Checking platform status
If something looks wrong and you're not sure whether it's your device or Synacl, check the status page first: https://status.synacl.com. Bookmark it.
It runs on a separate server from the platform it watches, so it stays up when the platform doesn't. It checks every part of Synacl once a minute.
What each component means
| Component | What is checked | What you'd notice if it fails |
|---|---|---|
| Web app | app.synacl.com loads | The app won't open |
| API | The API answers its health check. Slower than 2 seconds counts as degraded | Pages load slowly or show errors; integrations and the mobile app fail |
| Live updates | The live connection that pushes new values to dashboards opens | Dashboards stop moving until you reload |
| MQTT broker | Devices can connect to mqtt.synacl.com on port 8883 (TLS). If only the WebSocket listener fails, it's degraded | Devices and gateways can't connect or keep reconnecting |
| Data ingest | A test reading is published over MQTT and must show up in the platform. Over 15 seconds is degraded; not there within 30 seconds is down | Devices are connected but new values don't appear |
| Website & docs | synacl.com loads | The website and these help pages are unavailable |
Each component is Operational, Degraded (working, but slow or partly failing), Outage, or No data (no check result for that time). A component is only marked down after two failed checks in a row, so a single blip doesn't open an outage.
If the status page's own checks stop running, it says its data is stale instead of showing green. Old data never counts as "all clear".
How availability is calculated
Each component shows its availability over the last 30 and 90 days, plus a bar per day coloured by the worst state seen that day.
- Availability = time up (including degraded) ÷ time with a check result.
- Time with no check result shows as no data. It's left out of the calculation, never counted as up.
- Next to each figure is its coverage: the share of the period that actually had check results. 99.9% with 40% coverage tells you less than 99.9% with 100% coverage.
This is the same rule Synacl uses for your own devices. See how uptime is measured.
Incidents and maintenance
An incident moves through these stages, and each update is posted on the page:
- Investigating: we know something is wrong and are looking into it.
- Identified: we've found the cause and are working on a fix.
- Monitoring: a fix is in place and we're watching to make sure it holds.
- Resolved: it's over.
Each incident has an impact (none, minor, major or critical) and lists the components it affects. When a check finds a component down, an incident opens automatically, without waiting for someone to notice. Once the component has been back for a few minutes, the incident resolves itself. If our team has posted updates on it, it goes to Monitoring first and resolves after a longer stretch without problems.
Scheduled maintenance is announced ahead of time as Scheduled, then becomes In progress and Completed. Upcoming windows are listed on the status page.
Resolved incidents from the last 14 days stay on the page, and each one keeps its full timeline.
Getting notified
- Atom feed: https://status.synacl.com/feed.atom has one entry per incident or maintenance window, updated with every post. Add it to a feed reader or a chat tool's RSS integration.
- JSON: https://status.synacl.com/api/status.json returns everything on the page, for your own monitoring or dashboards. A smaller /api/summary.json returns just the overall state and anything active or coming up.
- In the app: while an incident or maintenance window is active, or maintenance is coming up soon, the web app shows a banner at the top with a link to the details.
If the status page is all green but your device is still offline, the problem is probably on your side. Work through my device shows offline.