Tabby status: API, auth, latency & outage reports

DownForAI monitors Tabby via a single endpoint — Tabby Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 384 ms; p95: 608 ms.

No development tooling incidents have been tracked for Tabby since monitoring began, and no community reports were submitted in the last 24 hours. Automated checks continue on the configured schedule.

Network latency — last 20 probes

Incident history (30d)

Reported symptoms

No user reports for Tabby in the last 24 hours.

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Community Discussion

Still having issues with Tabby?

Let the community know and help others experiencing the same problem.