Tipalti Outage History

Started Sep 17, 2026, 05:36 PM UTC· resolved Sep 17, 2026, 07:50 PM UTC

1. investigating Sep 17, 2026, 05:36 PM UTC

   Our Engineering team is actively investigating an issue affecting the Procurement, Expenses, and Cards modules. We will provide our next update by 11:00 a.m. PT.

2. investigating Sep 17, 2026, 05:59 PM UTC

   Our Engineering team continues to investigate the issue affecting the Procurement, Expenses, and Cards modules. We will provide our next update by 12:00 p.m. PT.

3. identified Sep 17, 2026, 07:02 PM UTC

   Our Engineering team has identified the issue affecting the Procurement, Expenses, and Cards modules and is actively working to resolve it. Next update: 12:15 p.m. PT

4. identified Sep 17, 2026, 07:18 PM UTC

   Our Engineering team is actively working to resolve the issue affecting the Procurement, Expenses, and Cards modules. Next update: 12:30 p.m. PT

5. identified Sep 17, 2026, 07:30 PM UTC

   We verified that the left sidebar in Procurement is now functioning normally and available. Our Engineering team continues to work toward resolving the issue affecting the Expenses and Cards modules. Next update: 12:45 p.m. PT

6. resolved Sep 17, 2026, 07:50 PM UTC

   We have resolved the issue affecting the Procurement, Expenses, and Cards modules. All services are now operating normally as of 12:45pm PT.

Read the full incident report →

Started Feb 06, 2026, 05:09 PM UTC· resolved Feb 06, 2026, 08:22 PM UTC

1. investigating Feb 06, 2026, 05:09 PM UTC

   We are currently investigating reports of some users experiencing issues receiving their two-factor authentication (2FA) codes via SMS. In some cases, users may receive a voice call with their authentication code instead of an SMS message. Our engineering team is actively working to identify the root cause and restore normal SMS delivery as quickly as possible. We will provide updates as more information becomes available. Thank you for your patience.

2. investigating Feb 06, 2026, 05:50 PM UTC

   Our engineering team is actively working with our 2FA service provider to identify the root cause and implement a resolution for the intermittent issues affecting SMS delivery of two-factor authentication (2FA) codes. This issue is being treated as a high priority. In the meantime, some users may receive their authentication code via voice call instead of SMS. We will continue to provide updates as progress is made. Thank you for your patience.

3. identified Feb 06, 2026, 06:20 PM UTC

   The root cause of the issues affecting SMS delivery of two-factor authentication (2FA) codes has been identified. Our engineering team is actively working with our 2FA service provider to implement a solution. This issue remains a high priority, and work is underway to restore normal SMS delivery as quickly as possible. Some users may continue to receive their authentication code via voice call instead of SMS during this time. Further updates will be shared as progress continues.

4. identified Feb 06, 2026, 07:22 PM UTC

   Our engineering team and our 2FA service provider are actively working to implement a solution to restore normal two-factor authentication (2FA) SMS delivery. This issue continues to be treated as a high priority, and efforts are underway to bring the system back to normal as quickly as possible. Some users may still receive their authentication code via voice call during this time. We will provide further updates as progress continues.

5. monitoring Feb 06, 2026, 07:54 PM UTC

   The issue affecting SMS delivery of two-factor authentication (2FA) codes has been resolved. Our engineering team, in collaboration with our 2FA service provider, has implemented a fix and normal service has been restored. Users should now receive their 2FA codes via SMS as expected. We will continue to monitor the system to ensure ongoing stability. Thank you for your patience while we worked to resolve this issue.

6. resolved Feb 06, 2026, 08:22 PM UTC

   We have received confirmation from users that the issue affecting SMS delivery of two-factor authentication (2FA) codes is resolved. Normal 2FA SMS delivery has been restored and the system is operating as expected. We will continue to monitor to ensure stability. Thank you for your patience and understanding.

Read the full incident report →

Started Dec 10, 2025, 10:09 PM UTC· resolved Dec 10, 2025, 11:20 PM UTC

1. investigating Dec 10, 2025, 10:09 PM UTC

   We are currently investigating reports of issues affecting bill uploads to the Tipalti Hub. Our engineering team is actively working to identify the root cause and restore full functionality as quickly as possible. We will provide updates as more information becomes available. Thank you for your patience and your partnership. Your Tipalti Team

2. monitoring Dec 10, 2025, 11:05 PM UTC

   A fix has been implemented by our engineering team and we are seeing an overall improvement with bill uploads. We are continuing to monitor the upload of bills. Thank you for your patience and your partnership. Your Tipalti Team

3. resolved Dec 10, 2025, 11:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 12:31 PM UTC· resolved Nov 18, 2025, 05:54 PM UTC

1. investigating Nov 18, 2025, 12:31 PM UTC

   Tipalti has been experiencing service disruptions today within the Tipalti Hub due to a Cloudflare issue. We apologize for any impact this may have on your operations and appreciate your understanding. We will keep you updated as we learn more. Thank you for your patience and partnership. The Tipalti Team

2. monitoring Nov 18, 2025, 04:13 PM UTC

   Our system is showing signs of stabilization as Cloudflare continues working toward a full resolution of the issue. We are actively monitoring performance and will provide another update once the system is fully stable.

3. resolved Nov 18, 2025, 05:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 07, 2025, 02:24 PM UTC· resolved Nov 07, 2025, 03:43 PM UTC

1. investigating Nov 07, 2025, 02:24 PM UTC

   We are investigating reports of some users having issues accessing Tipalti Hub.. Our engineering team is actively investigating the cause and working to resolve it as quickly as possible. Thank you for your patience and your partnership. Your Tipalti Team

2. resolved Nov 07, 2025, 03:43 PM UTC

   Our team has implemented a fix, and access to the Tipalti Hub should now be restored. Please clear your browser cache before logging in to ensure you’re viewing the latest version. If issues persist, contact Tipalti Support for assistance. Thank you for your patience.

Read the full incident report →

Started Oct 20, 2025, 03:09 PM UTC· resolved Oct 20, 2025, 10:34 PM UTC

1. investigating Oct 20, 2025, 10:03 AM UTC

   We are currently experiencing service disruptions as a result of a global outage affecting Amazon Web Services (AWS). This may cause certain features or services to be intermittently unavailable or degraded in performance. Our engineering team is actively monitoring the situation and will provide updates as additional information becomes available from AWS. We appreciate your understanding and patience.

2. investigating Oct 20, 2025, 03:09 PM UTC

   We are continuing to monitor the ongoing AWS service disruptions. Our engineering team is actively engaged and working to mitigate any potential impact. We’ll share additional updates as more information becomes available from AWS. You can follow the Global AWS outage here https://health.aws.amazon.com/health/status. Thank you for your patience and understanding.

3. investigating Oct 20, 2025, 05:32 PM UTC

   We are continuing to monitor the ongoing AWS service disruptions. Our engineering team remains actively engaged and is working to mitigate any potential impact. Amazon has reported that they are applying mitigation steps to address network load balancer issues and restore impacted services. We’ll share additional updates as more information becomes available from AWS. You can follow the global AWS outage here: https://health.aws.amazon.com/health/status Thank you for your patience and understanding.

4. investigating Oct 20, 2025, 07:33 PM UTC

   We are continuing to monitor the ongoing AWS service disruptions. Our engineering team remains actively engaged and is working to mitigate any potential impact. Amazon has reported ongoing service recovery, with intermittent errors persisting due to residual network connectivity issues. We’ll share additional updates as more information becomes available from AWS. You can follow the global AWS outage here: https://health.aws.amazon.com/health/status

5. resolved Oct 20, 2025, 10:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2025, 03:14 PM UTC· resolved Jul 01, 2025, 04:48 PM UTC

1. identified Jul 01, 2025, 03:14 PM UTC

   Tipalti has been experiencing intermittent slowness today within the Tipalti Hub. Our engineering team is actively working on the issue. We apologize if this slowness has affected your ability to work efficiently. Rest assured that we are dedicating as many resources as necessary to resolve it as quickly as possible. Thank you for your patience and your partnership! Your Tipalti Team

2. identified Jul 01, 2025, 04:17 PM UTC

   We are continuing to work on a full fix for this issue. We expect to provide another update in the next 30 minutes.

3. resolved Jul 01, 2025, 04:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 22, 2025, 06:52 PM UTC· resolved May 22, 2025, 08:59 PM UTC

1. investigating May 22, 2025, 06:52 PM UTC

   We are currently investigating an issue with our two-factor authentication (2FA) provider that is preventing SMS verification codes from being delivered. This is affecting users who have not previously saved their session (i.e., “Remember this device for 30 days” was not selected). Users with an active saved session are not impacted and can continue logging in normally. We are actively working with our 2FA provider to resolve the issue. In the meantime, affected users are advised to wait and try again later. We appreciate your patience and will provide updates here hourly until issue is resolved. Tipalti Support

2. investigating May 22, 2025, 07:55 PM UTC

   We are continuing to work with our two-factor authentication (2FA) provider to resolve an issue that is preventing SMS verification codes from being delivered. This is affecting users who have not previously saved their session (i.e., did not select “Remember this device for 30 days”). Users with an active saved session remain unaffected and can log in as usual. Our teams are actively working on a resolution. We will share the next update within one hour. Thank you for your continued patience. Tipalti Support

3. investigating May 22, 2025, 08:49 PM UTC

   We are continuing to investigate this issue.

4. monitoring May 22, 2025, 08:52 PM UTC

   The issue preventing SMS verification codes from being delivered has been resolved. Affected users should now be able to receive 2FA codes and log in successfully. We are actively monitoring the system to ensure continued stability. Thank you for your patience while we worked to resolve this.

5. monitoring May 22, 2025, 08:58 PM UTC

   We are continuing to monitor for any further issues.

6. resolved May 22, 2025, 08:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 27, 2024, 05:17 PM UTC· resolved Nov 27, 2024, 06:31 PM UTC

1. identified Nov 27, 2024, 05:17 PM UTC

   Tipalti has been experiencing intermittent issues today within the Tipalti Hub. Our engineering team is actively working on the problem. We apologize if this has affected your ability to work efficiently. Rest assured that we are dedicating as many resources as necessary to resolve it as quickly as possible. Thank you for your patience and your partnership. Your Tipalti Team

2. monitoring Nov 27, 2024, 06:21 PM UTC

   The issue has been resolved for most users. Our Engineering team is still working diligently to ensure all users are able to access the Hub as normal. We will provide another update when it is fully resolved.

3. monitoring Nov 27, 2024, 06:21 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Nov 27, 2024, 06:31 PM UTC

   This incident has been resolved.

Read the full incident report →