TaxJar Outage History

4 incidents recorded over the last 365 days, 2 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 TaxJar Incident

TaxJar incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 30, 2026Database MaintenanceThe scheduled maintenance has been completed.10h 0mScheduled
Jul 26, 2026Database MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Mar 26, 2026Our Intuit Quickbooks integration is reporting errors / disconnectedThis incident is resolved.1h 59mResolved
Feb 28, 2026Degraded TaxJar APIStarting at around 6pm EST today TaxJar customers making calls to /v2/customers or other endpoints with a customer_id included received 5xx errors. This was caused by a networking issue that was resolved around 10:50pm…0 minResolved

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 TaxJar 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 TaxJar 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 TaxJar 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 TaxJar outage in this window ran 10h, against a mean recovery of 3h 45m. If you depend on TaxJar 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.