System statusRefreshes every 5 min · UptimeRobot
Live status, no spin.
Uptime for every Kustiq service, pulled from independent health checks. Refreshes every 5 minutes. For an active incident, refresh again 5 min later for the next reading.
Kustiq runs — public services with — average uptime over the last 90 days, monitored every 5 minutes from independent regions.
1 profile a week anonymous3 a week with a free account, no cardIndependent monitor: UptimeRobot
System status
Live metrics paused. See the UptimeRobot mirror while we reconnect.
90-day uptime
—
across 0 services
Incidents · 90d
0
0 minor · 0 major · all resolved
Mean time to detect
5m
5-min check, multi-region
Mean time to recover
—
no recent incidents
Monitor breakdown
Each Kustiq service runs an independent health check every 5 minutes. Bars show the last 30 days; ratios are 30 and 90 day rolling windows.
No monitors to display right now. Try again in a few minutes.
Recent incidents
Last 1 incidents from the UptimeRobot log payload, paired by monitor and sequential timestamps.
0
No incidents in the last 90 days.
Questions about uptime, SLA, and comms.
How often does this page refresh?
Every 300 seconds the page re-fetches from UptimeRobot, so the worst-case staleness during an incident is the 5-minute check window plus a few seconds for the page to rebuild. The “Updated Nm ago” timestamp renders client-side from the cache fetch time, not the page-render time, so freshness is honest across timezones and visibly stale when the cache is cold.
Does Kustiq publish an SLA?
Pro and Enterprise contracts carry a 99.9% monthly uptime commitment with a service-credit schedule documented in /trust. The Free and Insight tiers run on the same infrastructure, surface the same uptime, and report against the same monitors, but are best-effort with no contractual remedy. Past 90 days have averaged 99.9%+.
What counts as “operational” on this page?
A monitor is “operational” when its 5-minute health check returned 2xx within the configured timeout. “Degraded” means UptimeRobot flagged a likely-down state but a follow-up check has not confirmed. “Down” means two consecutive failed checks. The overall status rolls up: operational only when every non-paused monitor is operational.
Where can I find postmortems and historical incidents past 90 days?
Major incidents get a postmortem under /blog tagged
postmortem, linked from the incident row above when available.Try Kustiq
Reading the status page does not get a contact verified.
If you came here because something looked off, open a ticket. If you came here from a vendor review, the rest of Kustiq is two clicks away.