Synacl platform status

Checking…
Reading the latest checks from the status monitor.

Components Uptime, last 90 daysUptime, last 30 days

Platform
Web appThe dashboard app at app.synacl.com
APIREST API at api.synacl.com, with its database, cache and broker links
Live updatesThe WebSocket channel that streams live values to dashboards
Devices & data
MQTT brokerDevice connections to mqtt.synacl.com:8883 (TLS) and over WebSocket
Data ingestA canary device publishes every minute; this checks the value lands in the platform
Website
Website & docssynacl.com: guides, Help Center and browser tools

Past incidents Last 14 days

Loading incident history…

How this page works

Every minute, monitoring that runs on separate infrastructure from the platform loads the web app, calls the API, opens a live-updates connection, connects to the MQTT broker the way a device does, and publishes a value from a canary device, then checks that the value arrives. A problem is reported once two checks in a row fail, so a single dropped request never shows as an outage.

Uptime counts only time we have measurements for. Time the monitor itself wasn't running shows as no data; it is not counted as up. Incidents appear here automatically when a check fails, and our team adds the details.

These checks started on 9 October 2026. For the 30 days before that, the Web app, API, Live updates and Website bars are reconstructed from our internal monitoring: the API server's health, scraped every 15 seconds from inside our network, and whether the web server containers were running. The MQTT broker and Data ingest have no reconstructed history. Their internal signals can show that they worked, but not that they failed, so reconstructing them would overstate their uptime.