Is TaxJar Down Right Now? Check if there is a current outage ongoing.

TaxJar API Users experienced a period of calculations returning $0 rates. The issue has been corrected. The duration of the issue was from 2:11 PM Eastern Time to 4:36 PM Eastern Time.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

TaxJar API users experienced a period of elevated API errors today around 12:13 pm Eastern time. The problem was identified and resolved by 12:26 pm Eastern time.

This incident has been resolved.

We are actively investigating an issue regarding account updates.

This incident has been resolved

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We have identified an issue with TaxJar Reporting UI performance and are implementing a fix.

This incident has been resolved.

We have identified an issue with TaxJar Reporting UI performance and are implementing a fix.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

This issue has been identified and a fix is being implemented.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

TaxJar API users experienced a period of elevated API errors today around 7:01 am EST. The problem was identified and resolved by 7:24 am EST.

This incident has been resolved.

A fix for Tax Calculations and TaxJar Reporting was applied at 8:33 EST. We will continue to monitor for additional issues.

We are continuing to monitor for any further issues.

We are currently monitoring 3rd party vendor issues. Hosting vendor is experiencing an outage.

We are investigating increased service errors.

Since the 3rd party hosting provider has implemented the fix, we have seen significant drop in errors for API Responses. At this time our services look like they have returned to normal. We will continue to monitor for additional issues.

Our 3rd party hosting provider has applied a fix relating to increased errors in API responses. We are continuing to monitor.

We are continuing to monitor the situation with our third party hosting provider that is causing elevated errors in API responses.. They have identified the root cause of the issue and are working towards resolution. At this time we still do not have an ETA for resolution.

Our 3rd party hosting provider has identified an issue that is causing elevated errors in API responses. We are continuing to monitor for additional issues.

We now see significant improvements in application and API response. At this time our services look like they have returned to normal. We will continue to monitor for additional issues.

We are continuing to monitor the situation with our third party hosting provider. They have identified the root cause of the issue and are working towards resolution. At this time we still do not have an ETA for resolution. We are continuing to see improvements in application and API response.

We are continuing to monitor the situation with our third party hosting provider. They have identified the root cause of the issue and are working towards resolution. At this time we still do not have an ETA for resolution. We can confirm that while our API success rate has improved, users are still experiencing increased error rates.

Hosting vendor is experiencing major outage.

We are currently monitoring potential 3rd party vendor issues.

TaxJar API users experienced a brief period of elevated API errors today around 2:35pm EST. The problem was immediately detected and resolved.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We've identified the issue and a fix has been implemented. We're monitoring the result.

We are currently investigating issues with TaxJar Reporting UI performance.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating degraded performance and intermittent errors on the TaxJar API.

This incident has been resolved.

AWS has implemented a partial fix and some of the affected services beginning to see recovery. They are continuing to work on resolving the underlying root cause and expect to be fully recovered within the next hour. Our services at this time have recovered but we are continuing to monitor the situation.

AWS is continuing to work on a fix for this issue.

AWS is continuing to work on a fix for this issue.

Amazon (AWS) is experiencing issues with EC2 & Elastic Load Balancing that is affecting our services. "We are working to resolve the issue resulting in increased error rates for the following EC2 APIs in the US-EAST-1 Region: RunInstances, *SecurityGroups, *NetworkInterfaces, *RouteTables, *AccountAttributes, and *NetworkAcls. These APIs will affect the ability to launch new EC2 instances and make mutating changes to Virtual Private Cloud (VPC) network configuration(s). Existing instances and networks continue to work normally. We have identified the root cause and are working towards resolution." See https://status.aws.amazon.com/ for more details.

We're investigating sporadic errors for some internal services.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We're investigating sporadic DNS errors for some internal services.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating an issue that is affecting performance when uploading or viewing transactions for some users.

During this incident, TaxJar customers were not able to access the TaxJar App or use the TaxJar API. We know this was impactful, and we are truly sorry it happened.  We have already implemented the following operational changes to ensure this type of failure does not happen again: * We updated our deployment pattern to a blue-green deployment pattern to allow us to better verify changes to production environments. * We are conducting a full audit of our vendor provided managed services that lack the acceptable level of rollback capabilities **Incident Root Cause Analysis**  * The incident started with a routine Kubernetes minor version upgrade using our vendor’s managed kubernetes service * This is a routine upgrade operation that we’ve completed 15 times in the past across 3 accounts and 2 regions. We perform this upgrade quarterly in order to keep pace with Kubernetes releases. * Immediately following completion of the upgrade of our production cluster, Kubernetes workers began reporting “Not Ready” status. * Within a few minutes all nodes were now in a state of “Not Ready” which caused all workloads to be marked as offline by our load balancers. * Kubernetes upgrades on our vendor’s managed Kubernetes service are not able to be rolled back. Furthermore new deployments and upgrades to the managed Kubernetes service can take 30-50 minutes to complete, leaving us forced to resolve the immediate issue rather than rolling back. * The vendor’s support team was able to identify the issue: * Clusters, starting with Kubernetes version 1.14 create a cluster security group when they are created.  * This security group is designed to allow all traffic from the control plane and[ ](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html)managed node groups to flow freely between each other.  * After the upgrade was completed, the vendor identified that the security group no longer had the required rules configured to allow this traffic to pass, even though this has always happened in prior instances of minor version upgrades. * We manually added the missing rule, which restored connectivity to our managed Kubernetes cluster. * At this point our services started coming back online. * Several other security groups, managed with cloudformation, which had utilized this rule for connectivity between our K8s workloads to other services provided by the vendor \(such as memory caches and databases\) were identified as being unexpectedly altered after this upgrade and also had to be repaired before all services could be restored. * We continue to work with the vendor to understand the root cause for the failure of the managed service to not operate as documented.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating elevated levels of errors for our address validation service.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating an issue with our /v2/validation endpoint used for validations of VAT identification numbers against VIES. All other endpoints are unaffected.

An outage at Cloudflare, a critical DNS provider for many services on the internet, had a documented outage causing intermittent issues for some of our customers.

An issue with a configuration change caused an increase in errors being returned for a small percentage of API requests between 2:11 and 2:45pm PDT. The error has been resolved and the API is now functioning normally.

Connectivity to the affected service has been restored, API errors have stopped and we are monitoring for further issues.

An issue with a backend service has caused increased error rates which may be impacting customers access to our API endpoints. We're monitoring situation and will update when the issue is resolved.

This issue was caused by a EC2 AZ failure. We've redirected SmartCalcs traffic to a different AZ and will continue to monitor system health.

We're currently investigating an issue with tax calculation endpoints.

This incident has been resolved.

We are beginning to see recovery for the elevated error rates and increased latency.

Amazon Cloudfront is experiencing increased latency and error rates which may be impacting some customers access to our API endpoints. We're monitoring situation and will update when the issue is resolved.

To ensure system reliability TaxJar will be performing brief database maintenance on database services that support our reporting application. Some users may see brief interruption when trying to view the transactions in the application during this time.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

There was a 5 minute window, around 15:30 CDT, where API users attempting to use the transaction endpoint would have experienced 500 error codes. This was caused by a 3rd party hosting provider incident that caused connectivity problems. The issue was quickly resolved.

There was a blip with our platform provider's infrastructure. All systems are now fully operational.

We are currently monitoring a short window of intermittent timeouts we had in the Transaction Push endpoints with our SmartCalcs API.

The underlying issue has been resolved by our hosting provider.

Our hosting provider is currently investigating platform issues. We are continuing to monitor the situation.

We are currently investigating this issue.

We experienced a decrease in database performance during a normal maintenance operation that impacted system availability for some users. Steps have been taken to ensure that this situation does not reoccur.

A database failover caused momentary performance degradation on TaxJar Reports (app.taxjar.com) and SmartCalcs' transaction endpoints. This incident was resolved almost immediately.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

Stripe has resolved their degraded service and all of TaxJar billing operations are available again.

We are currently monitoring an issue with a vendor having a partial outage around our account creation process. Users might have trouble creating new accounts in TaxJar Reporting at this time. Other services are all operational.

This issue has been resolved by Stripe our 3rd party vendor.

We are currently monitoring an issue with a vendor having a partial outage around our account creation process. Users might have trouble creating new accounts in TaxJar Reporting at this time. Other services are all operational.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

We resolved a database issue that was degrading the performance of some SmartCalcs requests.

We are currently investigating reports of slow response times on SmartCalcs.

This incident has been resolved.

The cause of the degraded performance has been identified and fixed. We are monitoring closely for any further issues.

We are currently investigating reports of degraded performance for TaxJar Reporting and the SmartCalcs API.

A faulty database instance has been identified and replaced. After monitoring the fix we believe this issue to be resolved.

We are currently investigating this issue.

This incident is now resolved.

Our engineering team has been able to restore service to TaxJar at this time. We will be monitoring the system and report back when all is resolved.

We are currently investigating slowness reports from TaxJar Reporting app, app.taxjar.com.

This incident has been resolved.

A fix has been implemented; performance has returned to normal. We're monitoring the app closely.

We've identified the source of the performance issues and are working towards a fix.

We're investigating reports of slow responses and timeouts from the main TaxJar application.

app.taxjar.com experienced a brief service disruption; requests to the SmartCalcs API may have failed as well. We have identified the cause was linked to a database update. Service is restored and we're continuing to monitor the site closely.