BetterProblems
Patchwork problems
A structured issue lifecycle, not a complaint board. Every problem carries a state, the company's own response, the time it took, and whether an affected user confirmed the fix.
The seven states a problem can be in
Reported and not yet acknowledged
Company has responded
Company is working on it
Resolution committed or scheduled
Company says it is fixed
Affected user confirms the fix
Company provides a reason, shown publicly
2
Problems in view
76%
Platform resolution rate
10h
Median first response
21
Users affected
Webhook retries deliver a duplicate payload
A failed webhook is retried without an idempotency key, so downstream systems process the same event twice.
API responses omit rate-limit headers
There is no way to see remaining quota before being throttled, so clients can only back off after a 429.