TaxBit Outage History
11 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded TaxBit Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 8, 2026 | Intermittent API errorsThis incident has been resolved. | 10h 36m | Resolved |
| May 8, 2026 | Elevated API errors and latencyThis incident has been resolved. | 3h 51m | Resolved |
| Mar 12, 2026 | Taxbit reporting database maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Mar 11, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 22, 2026 | Elevated Application Login ErrorsThis incident has been resolved. | 19 min | Resolved |
| Feb 11, 2026 | Taxbit reporting database infra upgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 1, 2026 | Elevated 5xx on /transactions APIThis incident has been resolved. | 25 min | Resolved |
| Jan 14, 2026 | Dashboard eligibility page data delayedThe system fully recovered from the backlog at 2:45 AM PT. Normal operational behavior and monitoring has resumed. | 16h 37m | Resolved |
| Dec 22, 2025 | Transaction data visibility in Taxbit Dashboard impactedThis incident has been resolved. The data backfill is complete, and we have confirmed that all transaction data is now correctly appearing on the Transactions Page and in Dashboard reports. | 276h 55m | Resolved |
| Dec 15, 2025 | Transaction API write failuresAPI calls to write transactions to Taxbit failing with 5xx errors. Transaction CSV file ingestion also affected. | 0 min | Resolved |
| Nov 16, 2025 | Dashboard Authentication ErrorsThis incident has been resolved. | 16 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next TaxBit incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This TaxBit Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before TaxBit acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single TaxBit outage in this window ran 11d 12h, against a mean recovery of 1d 4h. If you depend on TaxBit in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.