TrueContext Outage History
TrueContext is up right nowPingoru has recorded 50 incidents for TrueContext: 3 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 5 of 720 (1%) |
| May 2026 | 1 | 6 of 744 (1%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 0 | 0 of 583 (0%) |
Incidents, newest first
Minor September 3, 2026 Page loading may be delayed 45m Admin Console, Form Builder, Mobile App Communications, Customer Feedback Forms and 1 more
Started Sep 03, 2026, 08:13 PM UTC· resolved Sep 03, 2026, 08:59 PM UTC
- investigating Sep 03, 2026, 08:13 PM UTC
The site is currently experiencing a higher than normal amount of load, and may be causing pages to be slow or unresponsive. We're investigating the cause and will provide an update as soon as possible.
- monitoring Sep 03, 2026, 08:27 PM UTC
Response times have returned to normal levels. We will continue to monitor the situation.
- resolved Sep 03, 2026, 08:59 PM UTC
This incident has been resolved.
Minor May 8, 2026 TrueContext Salesforce Integration Disruption 6h 13m Submission Processing, Scheduled Jobs
Started May 08, 2026, 12:48 PM UTC· resolved May 08, 2026, 07:01 PM UTC
- investigating May 08, 2026, 12:48 PM UTC
We are currently experiencing elevated error rates with Salesforce integrations. Our engineering team is working to identify the root cause and implement a solution.
- identified May 08, 2026, 01:09 PM UTC
We've had success restoring Salesforce connectivity by editing Salesforce Connections and reconnecting them. If you are still experiencing issues after reconnecting, please contact support.
- resolved May 08, 2026, 07:01 PM UTC
Salesforce connectivity has been restored. Customers with broken Salesforce Connections are required to reconnect their Connection, after which functionality will return. If you are still experiencing issues after reconnecting, please contact support.
Minor April 30, 2026 Document generation failures 5h 21m Document Generation
Started Apr 30, 2026, 01:11 PM UTC· resolved Apr 30, 2026, 06:33 PM UTC
- investigating Apr 30, 2026, 05:21 PM UTC
We are experiencing an elevated level of errors generating documents, and are looking into the issue.
- monitoring Apr 30, 2026, 06:17 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 30, 2026, 06:33 PM UTC
This incident has been resolved.
Minor October 20, 2025 Issue with our upstream provider 3h 14m Admin Console, Form Builder, Mobile App Communications, Submission Processing and 5 more
Started Oct 20, 2025, 07:15 AM UTC· resolved Oct 20, 2025, 10:29 AM UTC
- identified Oct 20, 2025, 09:44 AM UTC
An upstream provider, Amazon Web Services, is currently experiencing an issue. Degraded performance is occurring across the TrueContext platform. We are working continuously to bring the service back to fully operational status.
- monitoring Oct 20, 2025, 10:06 AM UTC
The TrueContext service is fully recovered and operational again. We will continue to monitor in case of any changes.
- resolved Oct 20, 2025, 10:29 AM UTC
This incident has been resolved.
Minor October 2, 2025 Slow System Response Times 4h 50m Admin Console, Form Builder, Mobile App Communications, Submission Processing and 3 more
Started Oct 02, 2025, 01:30 PM UTC· resolved Oct 02, 2025, 06:20 PM UTC
- investigating Oct 02, 2025, 02:37 PM UTC
We are currently investigating this issue.
- identified Oct 02, 2025, 02:37 PM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 02, 2025, 02:38 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 02, 2025, 05:26 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 02, 2025, 06:20 PM UTC
This incident has been resolved.
- postmortem Oct 02, 2025, 07:26 PM UTC
**Service Degradation Update - October 1-2, 2025** Given the service degradation over the past two days, we wanted to provide detail on what happened and our path forward. **Incident 1 - October 1** At 11:30am EDT, we detected excessive pressure on our persistence store. We immediately rolled back a change released earlier that morning and performed manual actions to reduce system pressure. Service incrementally recovered to normal operation within one hour. We removed all changes from the prior 24 hours to investigate further, and those changes currently remain removed. **Incident 2 - October 2** At 10:00am EDT, approximately 30 minutes after deploying a new changeset, we noticed degraded response times, though not as severe as the prior day. We immediately initiated a rollback, which did not resolve the issue. A second, more extensive rollback also had no effect. Further analysis indicated the issue was likely triggered by increased activity volume during weekday morning hours rather than our code deployments. Given the reduced severity of this incident, we were able to investigate more thoroughly while maintaining acceptable service levels. We manually restored full system operation by early afternoon. **Current Status and Next Steps** * We have identified potential root causes and are actively investigating * Out of an abundance of caution, all code deployments are paused until we conclusively identify the root cause * We are implementing additional monitoring to detect similar issues earlier * We have created an additional response playbook with mitigation measures to resolve this type of incident more quickly We apologize for the disruption this has caused. We are committed to identifying and safely resolving the underlying root causes to prevent recurrence.
Minor September 17, 2025 Increased Errors 29m Admin Console, Submission Processing, Public REST API
Started Sep 17, 2025, 02:35 PM UTC· resolved Sep 17, 2025, 03:05 PM UTC
- identified Sep 17, 2025, 02:35 PM UTC
Our team has identified an increase in errors and have applied a fix that is rolling out across our servers.
- monitoring Sep 17, 2025, 02:53 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 17, 2025, 03:05 PM UTC
This incident has been resolved.
Major August 27, 2025 Submission Processing Issue identified 1h 29m Submission Processing
Started Aug 27, 2025, 06:24 PM UTC· resolved Aug 27, 2025, 07:53 PM UTC
- identified Aug 27, 2025, 06:24 PM UTC
We've identified the cause of a submission processing issue and are now working to return the service to normal operation.
- monitoring Aug 27, 2025, 07:00 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 27, 2025, 07:53 PM UTC
This incident has been resolved.
Notice May 19, 2025 SSO Login Service Disruption 1h 28m Admin Console, Mobile App Communications
Started May 19, 2025, 03:32 PM UTC· resolved May 19, 2025, 05:00 PM UTC
- investigating May 19, 2025, 03:32 PM UTC
A downstream provider used for single sign-on (SSO) is currently experiencing a service disruption. This may impact access to corporate login functionality in TrueContext across the portal and mobile applications. We will continue to monitor the SSO provider's status and will provide an update as soon as possible. TrueContext log in service is not affected by this disruption.
- identified May 19, 2025, 03:32 PM UTC
A downstream provider used for single sign-on (SSO) is currently experiencing a service disruption. This may impact access to corporate login functionality in TrueContext across the portal and mobile applications. We will continue to monitor the SSO provider's status and will provide an update as soon as possible. TrueContext log in service is not affected by this disruption.
- monitoring May 19, 2025, 03:42 PM UTC
Our systems are reporting SSO login functionality has been restored. We will continue monitoring.
- resolved May 19, 2025, 05:00 PM UTC
This incident has been resolved.
Major April 9, 2025 Microsoft Connection Issues Resolved - Click below 1d 18h Submission Processing, Scheduled Jobs
Started Apr 09, 2025, 09:11 PM UTC· resolved Apr 11, 2025, 03:36 PM UTC
- identified Apr 09, 2025, 09:11 PM UTC
We are aware of and investigating an issue with establishing connections to Microsoft services. Our engineering team is actively working to resolve the issue.
- identified Apr 09, 2025, 09:22 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Apr 09, 2025, 10:12 PM UTC
We have deployed a fix that restores connectivity to Microsoft services and are monitoring activity. You may need to reconnect Microsoft connections configured for your team. Instructions on reconnecting can be found in our documentation here: https://support.truecontext.com/hc/en-us/articles/4406637825300-How-to-Re-Connect-an-Expired-Connection
- resolved Apr 11, 2025, 03:36 PM UTC
This incident has been resolved.
Minor March 5, 2025 Processing Delays 1h 11m Scheduled Jobs, Advanced Analytics
Started Mar 05, 2025, 02:52 PM UTC· resolved Mar 05, 2025, 04:03 PM UTC
- investigating Mar 05, 2025, 02:52 PM UTC
We have identified delays in processing scheduled exports, and are actively investigating. Messages are currently queued and will process once we resolve the issue.
- monitoring Mar 05, 2025, 02:59 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 05, 2025, 04:03 PM UTC
Delays in processing have been resolved and all scheduled jobs impacted by the incident have been processed successfully.
Critical December 10, 2024 TrueContext Service Disruption 45m Admin Console, Form Builder
Started Dec 10, 2024, 07:37 AM UTC· resolved Dec 10, 2024, 08:22 AM UTC
- investigating Dec 10, 2024, 07:37 AM UTC
We are currently experiencing a service disruption. Our engineering team is working to identify the root cause and implement a solution.
- identified Dec 10, 2024, 07:57 AM UTC
We have identified the root cause of the issue and are actively working to restore the service.
- monitoring Dec 10, 2024, 08:15 AM UTC
Services look to be recovered. We will monitor for a short time before marking the incident completely resolved.
- resolved Dec 10, 2024, 08:22 AM UTC
Services are completely operational and the issue is now resolved.