api.kustiq.com/api/v1/health unreachable: Bad Gateway
api.kustiq.com/api/v1/healthResolved15mduration
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 2 public services with 99.99% 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
All systems operational
99.99% average uptime over the last 90 days across 2 services. No active incidents.
90-day uptime
99.99%
across 2 services
Incidents · 90d
5
3 minor · 2 major · all resolved
Mean time to detect
5m
5-min check, multi-region
Mean time to recover
11m
across 5 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.
api.kustiq.com/api/v1/healthOperational
https://api.kustiq.com/api/v1/health
100.00%30d
99.97%90d
May 10Today
kustiq.comOperational
https://kustiq.com
100.00%30d
100.00%90d
May 10Today
Recent incidents
Last 5 incidents from the UptimeRobot log payload, paired by monitor and sequential timestamps.
api.kustiq.com/api/v1/health degraded: Internal Server Error
api.kustiq.com/api/v1/healthResolved5mduration
api.kustiq.com/api/v1/health degraded: Bad Gateway
api.kustiq.com/api/v1/healthResolved5mduration
api.kustiq.com/api/v1/health degraded: Bad Gateway
api.kustiq.com/api/v1/healthResolved10mduration
api.kustiq.com/api/v1/health unreachable: Method Not Allowed
api.kustiq.com/api/v1/healthResolved20mduration
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.99%.
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.