Status

Tallywyrm is degraded.

At-a-glance banner for every subsystem plus a reverse-chronological incident log with the resolution note for each entry. The same operational view finance and platform leads read before they adopt.

Degraded performanceLast updated 2026-08-06
At a glance
Four subsystems. One log.
Discovery, the rightsizing PR bot, the scheduler and the weekly report generator — each with a current-state pill and a plain-text resolution note in the log below. Every line in the log is keyed to the same audit-trail row the deployed feature rests on.
Overall

Degraded performance

One or more subsystems are running slower than usual or returning partial results. Customers can still onboard, run inventories and read the weekly audit trail.

Last updated 2026-08-06

By subsystem

One row per subsystem.

The current state of every Tallywyrm subsystem, in the same vocabulary the incident log below uses.

Discovery

24/7 cloud inventory across AWS, GCP and Azure — projects, accounts, billing exports.

All systems operational

Last 30 days · operational 29/30

Rightsizing PR bot

Opens sized-down IaC pull requests in your repos with the audit-trail row attached.

Degraded performance

Last 30 days · operational 28/30

Scheduler

Weekly + on-demand run windows that drive report shipment and re-read cadences.

All systems operational

Last 30 days · operational 29/30

Weekly report generator

Composes the weekly audit-trail CSV + savings PDF that finance signs off on.

All systems operational

Last 30 days · operational 29/30

Incident log

Recent incidents

Last 10 incidents, newest first. Each row shows the customer-visible summary; click to expand the resolution note.

Want to dig further?

The same audit trail the deployed feature rests on.

Every incident on this page names the audit-trail row it rests on, so the customer symptom and the deployed fix share one record. /methodology names the pillars that row satisfies; /security names the controls; /contact is where the same row becomes a conversation.