Skip to content
Trellis

Status

All systems operational

Live component state, and an honest history of what has gone wrong. If you are seeing something this page does not show, tell us and we will update it.

Last checked

Aug 8, 2026, 5:44 AM Pacific

Incidents are posted here and mailed to workspace owners on the Startup and Growth plans.

Web applicationtrelliscore.coOperational
Readiness engineMapping and draftingOperational
Model routingPrimary provider healthyOperational
AuthenticationEmail and GoogleOperational
Evidence storeEncrypted at restOperational
BillingStripeOperational

99.94%

Uptime, 90 days

14.2s

Median readiness run

0

Runs failed, 90 days

History

What has gone wrong

Including the ones customers did not notice. A status page that only lists outages you already saw is not worth reading.

July 9, 2026

14:10 to 16:05 Pacific

Elevated latency on readiness runs

Resolved

Runs took 40 to 70 seconds instead of the usual 12 to 20 for around two hours, caused by rate limiting at our primary model provider. The fallback chain routed the affected runs to a second model and no run failed. We have raised our committed throughput and added a routing alarm at the 30 second mark.

May 27, 2026

09:22 to 10:00 Pacific

Sign in with Google unavailable

Resolved

A rotated client secret was applied to production before the identity provider finished propagating it, so Google sign in failed for 38 minutes. Email and password sign in was unaffected. Secret rotation now happens behind a health check rather than on deploy.

March 15, 2026

22:00 to 23:20 Pacific

Scheduled maintenance, evidence store

Resolved

Planned migration of the evidence store to encrypted volumes with customer-scoped keys. Readiness runs were queued rather than dropped, and the longest queue wait was four minutes.

Seeing something wrong that is not listed? Write to support@trelliscore.co or open a ticket.