/Status
← HomeRSS

All systems operational.

No active incidents · updated 14 seconds ago · monitoring every 30 s from 4 regions
Last incident7 days ago
QBO API rate-limit · resolved in 22 min

Last 90 days

OperationalDegradedOutageNo data
Overall uptime
99.97%
Target 99.9% · met for 7 quarters
Incidents
3
2 minor · 1 informational · 0 major
Mean time to resolve
18 min
−42% vs prior quarter
Webhook delivery
99.92%
P99 latency 340 ms
Categorization inbox
Web app · keyboard inbox · ⌘K palette
99.99%
90 days
Public API
REST + webhooks · ledgerinbox.com/api/v1
99.97%
90 days
Plaid bank sync
Item refresh · transaction webhooks
99.92%
90 days
QBO write-back
OAuth · journal entries · bill match
99.94%
90 days
AI categorization
Anthropic Claude Sonnet · 0-retention
99.99%
90 days
Receipt OCR
Veryfi pipeline · auto-match queue
99.96%
90 days
Authentication
Magic links · WorkOS SSO · session cookies
100.00%
90 days
Database
Postgres · row-level security · PITR
99.98%
90 days

Incident history

Subscribe →
May 12, 2026Minor

QBO API rate-limit returning 429s for ~12% of write traffic

MinorQBO write-backResolved · 22 min
May 12 · 14:42 CTResolved. Throttle relaxed by Intuit after escalation. All queued writes drained within 4 minutes. No data loss.
May 12 · 14:28 CTIdentified. Intuit confirmed an in-region rate-limit applied to App Partner Silver-tier accounts. Workaround active: writes queued and replayed once 429s subside.
May 12 · 14:20 CTInvestigating. Several customers report categorizations not posting to QBO. Inbox UI remains responsive.
May 03, 2026Minor

Plaid Chase Bank itemization delayed for ~6 hours

MinorBank sync · PlaidResolved · 6h 12m
May 03 · 17:54 CTResolved. Plaid restored Chase itemization. All delayed transactions backfilled in correct date order.
May 03 · 12:30 CTPlaid acknowledged on their status page. Our transaction inbox is unaffected for other institutions; affected firms see a banner on their Chase-connected books.
May 03 · 11:42 CTInvestigating delayed bank-line ingestion for accounts at Chase. Other institutions unaffected.
Apr 28, 2026Info

Scheduled maintenance: Postgres point-in-time recovery upgrade

InformationalDatabaseCompleted
Apr 28 · 04:14 CTCompleted with no read/write downtime. Backup retention now 30 days on Pro, 1 year on Team.
Apr 28 · 02:00 CTMaintenance window begins. Read replica fail-over expected to introduce a 5-second write pause around 02:14 CT.

Get notified before your client does.

One email per incident — no marketing, no digests, no “we value your trust.” Used for the 3-5 incidents per quarter, not the 0 marketing reasons.

RSSJSON feedSlack webhookStatus API