Tripleseat Outage History

Started Oct 10, 2026, 11:10 AM UTC· resolved Oct 10, 2026, 11:55 AM UTC

1. resolved Oct 10, 2026, 11:13 AM UTC

   We have received reports of Users being unable to login to Tripleseat. Affected Users report a large loading spiner that never completes upon entering their email. Condition: Degraded Our Development team is actively investigating this issue to identify the root cause and apply a fix. At this time, the following features may be impacted or unavailable: Login We will post another update on this page within the hour if not sooner.

2. resolved Oct 10, 2026, 11:27 AM UTC

   Our Developers have identified the root cause of the issue preventing users from logging into Tripleseat and have taken corrective action. We are monitoring performance to ensure Users can login as expected. We will post another update here within the hour if not sooner.

3. resolved Oct 10, 2026, 12:22 PM UTC

   Following the fix implemented by our Development team, Users are able to login as expected. If you have any questions please do not hesitate to reach out to [email protected].

Read the full incident report →

Started Sep 30, 2026, 03:29 PM UTC· resolved Sep 30, 2026, 04:02 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Sep 30, 2026, 03:22 PM UTC· resolved Sep 30, 2026, 04:02 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Sep 24, 2026, 01:04 PM UTC· resolved Sep 25, 2026, 01:42 PM UTC

1. resolved Sep 24, 2026, 01:20 PM UTC

   Our Development team has identified the source of the issue causing USers to be Auto CC'd on discussions, and have a fix in reivew to prevent this going forward. We will post another update here within the hour if not sooner.

2. resolved Sep 24, 2026, 03:27 PM UTC

   Our Development team has deployed an update to address the issues causing users to be auto cc'd on discussion messages. We will continue to monitor to ensure no further issues arise following this update. We will post another update here once we have confirmed full resolution.

3. resolved Sep 24, 2026, 04:09 PM UTC

   Following the fix implemented by our Development team, users are no longer automatically copied on Discussions emails. The fix applies to new Discussions sent after it was released; it does not change emails sent before then, which may have been affected. Going forward, users will only be copied if they're configured for auto-CC or the sender adds them manually. If you have any questions please do not hesitate to reach out to [email protected].

4. resolved Sep 24, 2026, 08:54 PM UTC

   We have identified an additional related issue following the previous deployment. Some Users are being copied on existing and new discussions, despite being manually removed. Our Developers have found the root cause of the secondary issue and are working on corrective measures. We will post another update here when we have additional information to share.

5. resolved Sep 24, 2026, 09:35 PM UTC

   Thank you for your patience. Our Developers have released a fix for the secondary issue discovered this afternoon. Our teams are actively monitoring Tripleseat to ensure there are no residual impacts following this update. We will post another update here when we have confirmed that there are no further related issues.

6. resolved Sep 25, 2026, 01:42 PM UTC

   After monitoring performance and further testing we have confirmed full resolution of the issue causing some users to be Auto-CC'd on discussions. Going forward, Users will only be auto-cc'd on Discussions they are the Owner/Manager of, and manually removing users from the recipients list will stop them from receiving the message as expected. If you have additional questions or need further assistance, please reach out to [email protected].

Read the full incident report →

Started Sep 14, 2026, 02:52 PM UTC· resolved Sep 14, 2026, 08:42 PM UTC

1. resolved Sep 14, 2026, 02:59 PM UTC

   Our Engineering team has identified a performance issue with Lead Reports in Tripleseat and are working to resolve it. In the meantime, Lead Reports may take longer to load than normal, or timeout before loading fully. We will post another update here within the next hour if not sooner.

2. resolved Sep 14, 2026, 05:00 PM UTC

   Our Development team is still investigating the issues impacting Lead Reports in Tripleseat. Some users may experience delays/timeouts when loading Lead Reports in Tripleseat. We will post another update here when we have additional information to share.

3. resolved Sep 14, 2026, 05:12 PM UTC

   Our Development team has identified the root cause of the issues impacting Lead Report performance in Tripleseat, and are working on a potential fix to mitigate this. We will post another update here when we have additional information to share.

4. resolved Sep 14, 2026, 07:53 PM UTC

   Our Development team has deployed an update to address the issues impacting lead reports in Tripleseat. Our teams will continue to monitor Tripleseat to ensure performance improves.

Read the full incident report →

Started Sep 11, 2026, 01:22 PM UTC· resolved Sep 11, 2026, 02:36 PM UTC

1. resolved Sep 11, 2026, 01:31 PM UTC

   We have received reports of degraded performance in Tripleseat. Our Development team is actively investigating this issue to identify the root cause and apply a fix. At this time, users may experience slow load times while navigating Tripleseat. We will post another update on this page within the hour if not sooner.

2. resolved Sep 11, 2026, 01:45 PM UTC

   Our Development team has isolated the cause of the performance degradation in Tripleseat and have applied corrective measures. Following this update, we are seeing performance levels return to normal. Users should be able to use Tripleseat as expected. We will continue to monitor performance to ensure that there are no residual issues following this update.

Read the full incident report →

Started Aug 15, 2026, 05:08 PM UTC· resolved Aug 17, 2026, 03:55 PM UTC

1. resolved Aug 15, 2026, 05:26 PM UTC

   Our Engineers have Identified an issue with our third-party email delivery provider, SendGrid. Microsoft's mail servers are blocking an increased volume of messages across SendGrid's platform, not specific to Tripleseat. SendGrid has escalated to Microsoft and is awaiting a resolution. Tripleseat users sending to Microsoft 365-hosted emails may experience elevated Bounces/Blocks. All messages are landing in the guest portal as expected and can be viewed there in the meantime. We're monitoring the situation and will post updates here as we learn more. More information can be found on Sendgrid's Status Page (https://status.twilio.com/incidents/r2gvsly2y5ty).

2. resolved Aug 17, 2026, 01:47 PM UTC

   SendGrid has confirmed that the issue causing an increased block rate to Microsoft 365 has been resolved. Block rates across SendGrid's platform industry-wide have returned to normal levels. During the incident, Tripleseat users sending to Microsoft 365-hosted emails may have experienced elevated Bounces/Blocks. All messages continued to land in the guest portal as expected and could be viewed there in the meantime. We're monitoring delivery closely to ensure no residual issues arise following resolution. More information can be found on SendGrid's Status Page (https://status.twilio.com/incidents/r2gvsly2y5ty).

3. resolved Aug 17, 2026, 03:55 PM UTC

   We've confirmed no residual impacts following the resolution on Sendgrid's end. Emails sent via Tripleseat to MS365 hosted servers are sending as expected. If you notice anything or need assistance, please reach out to [email protected].

Read the full incident report →

Started Aug 07, 2026, 01:14 PM UTC· resolved Aug 10, 2026, 02:34 PM UTC

1. resolved Aug 07, 2026, 01:32 PM UTC

   We have received reports of degraded performance when accessing and editing Tripleseat Documents. Our Development team is actively investigating this issue to identify the root cause and apply a fix. We will post another update on this page within the hour if not sooner.

2. resolved Aug 07, 2026, 02:51 PM UTC

   We've identified the cause of the slow load times affecting document templates, including cases where the document editor failed to load entirely and blocked edits and saves. The issue is related to how certain editor resources load for some users. We're actively working on a fix and will share another update as soon as we have more information.

3. resolved Aug 07, 2026, 07:58 PM UTC

   We've confirmed the root cause of the performance issues affecting document templates in Events & Bookings and our Developers have a potential fix under review to mitigate this going forward. We will post another update here once this fix is deployed.

4. resolved Aug 07, 2026, 10:26 PM UTC

   Our Development team has deployed an update to address the issues impacting performance in Tripleseat Documents. We will continue to monitor performance to ensure that there are no residual issues following this update. We will post another update here once we have confirmed full resolution.

Read the full incident report →

Started Aug 03, 2026, 03:09 PM UTC· resolved Aug 03, 2026, 07:23 PM UTC

1. resolved Aug 03, 2026, 03:15 PM UTC

   We have received reports of degraded performance and timeouts in Insights. Our Development team has confirmed that this stems from an issue with a third-party provider, Snowflake, whose engineers are currently investigating the root cause. Our team is actively monitoring the situation and will provide updates here as progress is made. More information can be found on the Snowflake Status Page: (https://status.snowflake.com/incidents/xfv4kdj30rcb).

2. resolved Aug 03, 2026, 04:16 PM UTC

   The Snowflake Engineering team has identified the root cause of the issue and is working towards a fix. We are continuing to monitor the situation and performance in Insights closely, and will provide additional updates here as progress is made. For more information, visit the Snowflake Status Page: https://status.snowflake.com/incidents/xfv4kdj30rcb

3. resolved Aug 03, 2026, 04:39 PM UTC

   Following the update made by Snowflake's Engineers, Insights reports are beginning to load as expected. User's should start noticing an improvement in performance shortly. We will continue monitoring Insights to ensure no further issues arise going forward. If you need assistance, please reach out to [email protected].

Read the full incident report →

Started Jul 29, 2026, 04:03 PM UTC· resolved Jul 30, 2026, 02:42 PM UTC

1. resolved Jul 29, 2026, 04:03 PM UTC

   Title: INC-82- Login page unresponsive/missing credential fields Status: acknowledged Condition: Degraded We are investigating reports of issues in Tripleseat. The following services may be affected: Login Standard Login We will post another update here in 60 minutes or when we have additional information to share.

2. resolved Jul 29, 2026, 04:09 PM UTC

   Our Development team is still investigating the issues impacting Tripleseat. Condition: Degraded At this time, the following features may be impacted or unavailable: Login We will post another update here within the hour if not sooner.

3. resolved Jul 29, 2026, 05:07 PM UTC

   We're continuing to investigate the sign-in issue affecting some users. Our development team is actively working through this, and we'll share another update within the hour, if not sooner.

4. resolved Jul 29, 2026, 07:28 PM UTC

   Our Development team is still investigating the issues impacting the login page for certain users. We will post another update here within the hour if not sooner.

5. resolved Jul 29, 2026, 08:55 PM UTC

   Our team has identified that this issue is related to a third-party service provider and is deploying a fix intended to resolve it for affected users. We're continuing to monitor as this rolls out. We'll share our next update here as the rollout develops.

6. resolved Jul 30, 2026, 02:41 PM UTC

   This issue has been resolved, and users should now be able to sign in as normal. If you're still experiencing trouble signing in, please reach out to [email protected] and our team will be glad to help.

Read the full incident report →

Started Jul 25, 2026, 12:00 AM UTC· resolved Jul 25, 2026, 02:02 AM UTC

1. resolved Jul 25, 2026, 02:02 AM UTC

   Today’s maintenance is complete. The Tickets and EventUp Planner platforms are available and functioning as expected. If you have any questions please do not hesitate to reach out to [email protected].

Read the full incident report →

Started Jun 19, 2026, 04:54 PM UTC· resolved Jun 19, 2026, 11:38 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jun 11, 2026, 02:04 AM UTC· resolved Jun 11, 2026, 02:49 AM UTC

1. resolved Jun 11, 2026, 02:04 AM UTC

   Today’s maintenance has begun. During this time, users may be logged out of Tripleseat and prompted to log back in. We will post another update when maintenance is complete.

2. resolved Jun 11, 2026, 02:49 AM UTC

   Today’s scheduled maintenance is complete, and Users can access Tripleseat as expected. We will continue monitoring Tripleseat to ensure optimal performance.

Read the full incident report →

Started May 13, 2026, 11:00 AM UTC· resolved May 13, 2026, 12:00 PM UTC

1. resolved May 13, 2026, 11:03 AM UTC

   The EventUp platform will be undergoing scheduled maintenance today May 13th, 2026 from 7 AM - 8 AM EDT (UTC-4). During this time, EventUp may be unavailable to Users and Guests. This will not impact the Tripleseat platform. We will post another update here when maintenance is complete. If you have any questions, please reach out to [email protected].

2. resolved May 13, 2026, 12:05 PM UTC

   Today's maintenance on the EventUp Platform is complete. Users and Guests can now access listings as expected.

Read the full incident report →

Started Apr 22, 2026, 01:36 PM UTC· resolved Apr 23, 2026, 01:14 PM UTC

1. resolved Apr 22, 2026, 01:44 PM UTC

   We have received reports of SmartScreen warnings when accessing PDFs in Tripleseat for Users in Microsoft Edge. Condition: Operational We have confirmed that this is a false positive and have submitted a delisting request to Microsoft. We are currently monitoring for resolution. In the meantime, Users can bypass this message by clicking 'More Information' > 'Continue to Site' within the warning screen. Alternatively, we recommend temporarily using another browser such as Chrome or Safari. We will continue to post updates on this page as new information becomes available.

2. resolved Apr 23, 2026, 01:14 PM UTC

   We received word from Microsoft this morning that s3.amazonaws.com and Tripleseat assets hosted there should no longer trigger SmartScreen warnings in Microsoft Edge. In testing this morning, PDFs are viewable and downloadable in Edge as expected, without receiving any warnings. We will continue to monitor Tripleseat in MS Edge to ensure no further false reports are triggered. If you have any questions, please reach out to [email protected].

3. resolved Apr 23, 2026, 01:14 PM UTC

   We received word from Microsoft this morning that s3.amazonaws.com and Tripleseat assets hosted there should no longer trigger SmartScreen warnings in Microsoft Edge. In testing this morning, PDFs are viewable and downloadable in Edge as expected, without receiving any warnings. We will continue to monitor Tripleseat in MS Edge to ensure no further false reports are triggered. If you have any questions, please reach out to [email protected].

Read the full incident report →

Started Apr 17, 2026, 03:40 PM UTC· resolved Apr 17, 2026, 08:12 PM UTC

1. resolved Apr 17, 2026, 03:48 PM UTC

   We are currently investigating an issue in Dark Mode where text within Discussions and Documents is displaying in grey instead of white, impacting visibility and contrast. Our Development team is actively working to identify the root cause and implement a fix. We will provide updates here as more information becomes available.

2. resolved Apr 17, 2026, 04:18 PM UTC

   Our Development team has identified the root cause of the issues impacting Dark Mode in Tripleseat and are currently testing potential mitigations. Condition: Bug At this time, the following features may be impacted: Discussions Documents We will post another update here within the hour if not sooner.

3. resolved Apr 17, 2026, 04:52 PM UTC

   At this time, our Development team is actively working on potential mitigations for this issue. Development work is underway to deploy a fix. The following features may be impacted: Discussions Documents We will post another update here within the hour if not sooner.

4. resolved Apr 17, 2026, 05:27 PM UTC

   Our team has prepped a fix for this issue and is in the process of testing, before deployment. At this time the following features may be impacted: Discussions Documents We will post another update here within the hour if not sooner.

5. resolved Apr 17, 2026, 06:31 PM UTC

   Our team has identified a potential fix and is currently screening, vetting, and thoroughly testing the solution. Once testing is complete and we’ve confirmed stability, the update will be deployed to resolve the issue. We will continue to provide updates here as progress is made.

6. resolved Apr 17, 2026, 07:45 PM UTC

   Our Development team has deployed an update to address the issues impacting Dark Mode in Tripleseat and text is displaying as expected in discussions and documents. Users should be able to use Dark Mode as expected. We will continue to monitor Tripleseat to ensure that there are no residual issues following this update. We will post another update here once we have confirmed full resolution.

7. resolved Apr 17, 2026, 08:12 PM UTC

   Following the fix implemented by our Development team, Dark mode in Tripleseat is displaying text as expected. Condition: Operational If you have any questions please do not hesitate to reach out to [email protected].

Read the full incident report →

Started Feb 27, 2026, 03:01 PM UTC· resolved Mar 02, 2026, 02:00 PM UTC

1. resolved Feb 27, 2026, 03:29 PM UTC

   We’ve received reports of issues loading the Discussions and Documents pages that may be limited to users accessing Tripleseat through Safari. Our Development team is actively investigating to determine the root cause. In the meantime, if you experience any issues, we recommend accessing Tripleseat using another browser such as Google Chrome, Firefox, or Microsoft Edge. We will post another update here within the hour if not sooner.

2. resolved Feb 27, 2026, 04:44 PM UTC

   We are continuing to investigate reports of issues loading the Discussions and Documents when accessed from Safari. We've confirmed that this behavior is specific to Safari version 18.6 and earlier. Our Development team is actively reviewing options to mitigate these issues. In the meantime, if using Safari, we recommend updating to the latest version. Alternatively, as a temporary workaround, we suggest using another browser such as Chrome, FireFox or Microsoft Edge. We will post another update here within the hour if not sooner.

3. resolved Feb 27, 2026, 06:01 PM UTC

   We are continuing to investigate reports of issues loading Discussions and Documents when accessed from Safari. At this time, we’ve confirmed that this behavior is impacting legacy Safari systems. Updating Safari to the latest available version — or at minimum version 16.4 — appears to resolve the issue. If you are experiencing this behavior, please navigate to System Settings > General > Software Update on your Apple device to ensure your software is up to date. As an alternative workaround, you may also use another browser such as Chrome, Firefox, or Microsoft Edge. We will post another update here within the hour if not sooner.

4. resolved Feb 27, 2026, 06:58 PM UTC

   Our Developers are testing potential mitigations for Legacy Safari Users experiencing issues with Documents and Discussions. Updating Safari to version 16.4 or later appears to resolve the issue. If you are experiencing this behavior, please navigate to System Settings > General > Software Update on your Apple device to ensure your software is up to date. As an alternative workaround, you may also use another browser such as Chrome, Firefox, or Microsoft Edge. We will post another update here within the hour if not sooner.

5. resolved Feb 27, 2026, 09:18 PM UTC

   Our Developers have a fix in testing for Legacy Safari/iOS Users experiencing issues with Documents and Discussions. If you are experiencing this behavior, please navigate to System Settings > General > Software Update on your Apple device to ensure your Safari and OS are updated to version 16.4 or later. As an alternative workaround, you may also use another browser such as Chrome, Firefox, or Microsoft Edge. We will post another update here when we have additional information to share.

6. resolved Feb 27, 2026, 10:06 PM UTC

   Our Developers have completed testing a fix for legacy Safari/iOS users experiencing issues with Documents and Discussions. The fix is being deployed tonight and will be rolled out to all customers. **In the meantime we recommend either:** - Updating to version 16.4 or later via System Settings > General > Software Update - Using an alternative browser such as Chrome, Firefox, or Microsoft Edge We'll provide another update once the deployment is complete. Thank you for your patience.

7. resolved Feb 27, 2026, 11:09 PM UTC

   Our Development team has deployed an update to mitigate the loading issues for Discussions and Documents on legacy Safari/iOS versions. We will continue to monitor performance in Tripleseat to ensure no further issues arise.

8. resolved Mar 02, 2026, 02:00 PM UTC

   Following the fix implemented by our Development team, Discussions and Documents are now loading as expected in legacy Safari/iOS systems. We will continue monitoring Tripleseat to ensure optimal performance going forward. If you have any questions please do not hesitate to reach out to [email protected].

Read the full incident report →

Started Feb 26, 2026, 07:41 PM UTC· resolved Mar 06, 2026, 03:53 PM UTC

1. resolved Feb 26, 2026, 08:27 PM UTC

   We've been notified that our third-party email provider, Sendgrid, is conducting scheduled maintenance through March 6, 2026. (Sendgrid Status Page: https://status.sendgrid.com/) During this time, Discussion Messages are still being delivered as expected and Tripleseat Discussions remain fully operational. The Delivery Status shown in-app may be delayed while SendGrid’s services are temporarily unavailable each day. In some cases, the status may take up to 12 hours to appear. Once the maintenance window closes each day, those updates will sync automatically. Our Team is actively monitoring the situation and will continue to post updates here as new information becomes available.

2. resolved Feb 27, 2026, 02:27 PM UTC

   Our third-party email provider, Sendgrid, is conducting scheduled maintenance through March 6, 2026. (Sendgrid Status Page: https://status.sendgrid.com/) During this time, Discussion Messages are still being delivered as expected and Tripleseat Discussions remain fully operational. The Delivery Status shown in-app may be delayed while SendGrid’s services are temporarily unavailable each day. In some cases, the status may take up to 24 hours to appear. Once the maintenance window closes each day, those updates will sync automatically. Our Team is actively monitoring the situation and will continue to post updates here as new information becomes available.

3. resolved Mar 02, 2026, 02:48 PM UTC

   Our Development team made an update to how Delivery Status updates from Sendgrid are handled. The Delivery Status will populate as expected for messages sent going forward despite the ongoing Sendgrid maintenance. Missing statuses for messages sent between 2/26 around 12 AM EST to Friday, 2/27 around 5 pm EST that have not synced will not populate. However, we can confirm messages were processed and sent successfully on our end. We're sorry for any inconvenience. Our teams will continue to monitor discussions and Sendgrid's Maintenance to ensure no further issues arise. If you have any questions, please do not hesitate to reach out to [email protected].

Read the full incident report →

Started Feb 10, 2026, 09:08 PM UTC· resolved Feb 10, 2026, 10:36 PM UTC

1. resolved Feb 10, 2026, 09:09 PM UTC

   We have received reports of degraded performance and missing style assets in Tripleseat. This has been escalated to our Development team to investigate further. We will post another update on this page within the hour if not sooner.

2. resolved Feb 10, 2026, 09:28 PM UTC

   Our Developers have confirmed that the missing style assets and the degraded performance in Tripleseat is a result of an issue with a third-party provider, Cloudfront. The Cloudfront team is currently investigating DNS failures on their platform. More information about this can be found on their status page (https://health.aws.amazon.com/health/status) At this time, Users may see pages rendering as plain text and some missing style assets when navigating Tripleseat. Our team is continuing to monitor Tripleseat and explore potential mitigations while the Cloudfront team works on restoring service to their platform. We will post another update here within the hour if not sooner.

3. resolved Feb 10, 2026, 10:06 PM UTC

   The Cloudfront team has deployed an update to mitigate the issues reported on their Status Page (https://health.aws.amazon.com/health/status). They are still working on some affected regions. Some users may still encounter style discrepancies until Cloudfront's services are fully restored, however we are noticing an overall improvement in performance and previously missing assets are beginning to render as expected. We will continue monitoring Tripleseat to ensure this trend continues and that there are no residual impacts following Cloudfront's mitigations.

Read the full incident report →

Started Feb 06, 2026, 02:02 PM UTC· resolved Feb 06, 2026, 06:29 PM UTC

1. resolved Feb 06, 2026, 02:03 PM UTC

   We have received reports of issues with Menu Item Totals missing from Billing widgets in Tripleseat. This has been escalated to our Development team to investigate further. We will post another update on this page within the hour if not sooner.

2. resolved Feb 06, 2026, 03:06 PM UTC

   Our Engineers are still investigating reports of Menu Item Category totals missing from Document layouts in Tripleseat. Users may notice the totals correct when editing Document templates, but that they are not displayed on the Live Document Layouts and Grand Total Previews on the Docs, Details, and Payments tabs may be skewed. We will post another update here within the hour if not sooner.

3. resolved Feb 06, 2026, 03:46 PM UTC

   Our Engineers have identified the root cause of the issues impacting document grand totals and line items. They have since reverted the update that caused it. Documents that were updated or accessed during this time may be impacted and require another update to resync the data from the Billing Widget to the affected layouts and fields. To do this, Users will need to open the Document Template Editor and Click 'Update' at the bottom, forcing an update. To find out what Documents may have been impacted, Users can pull an 'Activity Report' in Reports for 'Document Updated' actions on 2/6/26, and review for any documents with skewed totals and missing items. We are so sorry for the disruption. Our teams are actively monitoring performance for any residual impacts; We will post another update here within the hour if not sooner.

4. resolved Feb 06, 2026, 05:00 PM UTC

   Our Developers are still exploring options to resync affected Documents on the back-end. In the meantime, manual updates made to impacted event/booking documents are restoring the missing line items and correcting skewed totals on the Details, Docs, and Payments tabs of affected events/bookings. Users can make this update by viewing the Docs tab of the affected events/bookings, opening the Contract & Event Order template and clicking 'save' in the bottom left. We will post another message here when we have additional information on the resync.

5. resolved Feb 06, 2026, 06:29 PM UTC

   Our Engineers have finished resyncing line item and grand total information to their respective document layouts and fields. Previously missing line item totals have been restored and grand totals are calculating as expected. We are sorry for the disruption. Our Teams are continuing to monitor performance and outreach to ensure no further issues arise as a result of this. If you have any questions please do not hesitate to reach out to [email protected].

Read the full incident report →

Started Feb 04, 2026, 09:38 PM UTC· resolved Feb 05, 2026, 02:33 PM UTC

1. resolved Feb 04, 2026, 09:45 PM UTC

   We have received reports of formatting discrepancies on PDFs generated in Tripleseat, such as duplicate headers and skewed descriptions. Our Developers have identified the root cause of the issues impacting Documents in Tripleseat and are exploring potential mitigation options. As a temporary workaround, Users can enable the 'Advanced PDF Converter' setting for the affected layouts in Settings > Documents > Edit Layout > Layout Properties. We will post another update here within the hour if not sooner.

2. resolved Feb 04, 2026, 10:35 PM UTC

   Our Development team has deployed an update to address the issues reported with Documents, we are starting to see newly generated PDFs populate with their expected formatting. For PDFs generated today with formatting discrepancies, making a content change to the Document Template (such as adding a space) will force the PDFs to regenerate the next time they are opened from the Docs Tab. Our team will continue to monitor Tripleseat and PDF generation to ensure this continues and no residual issues are reported.

3. resolved Feb 05, 2026, 02:35 PM UTC

   Following the fix implemented by our Development team, PDFs are now generating with their expected formatting. We will keep monitoring to ensure this continues. If you have any questions please do not hesitate to reach out to [email protected].

Read the full incident report →

Started Jan 22, 2026, 08:51 PM UTC· resolved Jan 23, 2026, 04:25 PM UTC

1. resolved Jan 22, 2026, 08:57 PM UTC

   We have received reports of email deferrals for messages sent to Microsoft/Outlook Servers from Tripleseat. We have confirmed that this stems from an infrastructure outage at Microsoft. At this time, deferred messages are still being processed by Tripleseat, and will be resent to Microsoft and Outlook servers once they have restored service to the platform. These messages are still available to Guests and Users in the Tripleseat Discussions tab as well as the guest portal. We appreciate your patience while we work through this. We will post another update here in 60 minutes if not sooner.

2. resolved Jan 22, 2026, 10:06 PM UTC

   At this time, Microsoft is still reporting Service Degradation on their Status Page (https://status.cloud.microsoft/m365/) and their Engineers are working on potential mitigations. Messages from tripleseat to MS servers are still being deferred and will send once performance is restored to Microsoft's platforms. Deferred messages are still available in the Guest Portal and Discussions center. We are continuning to monitor Email Processing on our end to ensure no failures occur and that messages are queued to send as expected upon resolution.

3. resolved Jan 23, 2026, 02:20 PM UTC

   Service has been restored to Microsoft's Platforms, and deferred messages from Tripleseat are currently being processed as expected. Our team is monitoring Deliverability to ensure deferred mail catches up and that there are no residual issues following the MS Outage. We will post another update in 60 minutes if not sooner.

4. resolved Jan 23, 2026, 03:17 PM UTC

   Following Microsoft's Service Restoration, previously deferred Discussions are currently being processed and sent as expected. We are continuously monitoring Tripleseat Deliverability to ensure there are no lingering impacts from the Microsoft Outage. If you have any questions please do not hesitate to reach out to [email protected].

5. resolved Jan 23, 2026, 04:25 PM UTC

   Thank you for your patience while we worked through the issues caused by the Microsoft Outage. Following Microsoft's Service Restoration, previously deferred Discussions and emails from Tripleseat to Outlook servers are being successfully processed and sent as expected. Once these are accepted by Microsoft's servers the delivery status will update to reflect the server response in Tripleseat. We're so sorry for the disruption and the frustration this has caused. We are continuing to monitor Tripleseat to ensure there are no lingering impacts from this issue. If you have any questions please reach out to [email protected].

Read the full incident report →

Started Oct 20, 2025, 03:17 PM UTC· resolved Oct 20, 2025, 09:04 PM UTC

1. resolved Oct 20, 2025, 03:32 PM UTC

   At this time, Tripleseat Insights+ is experiencing degraded performance. This currently impacts the ability to view, run and export reports in Tripleseat Insights+, and users may experience delays in accessing ths Insights+ page. We've confirmed that the issue derives from a third-party cloud platform, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes.

2. resolved Oct 20, 2025, 04:35 PM UTC

   Our third-party cloud platform has identified network connectivity issues and isolated the root cause. They are working to mitigate the issue, and we are continuing to monitor performance in-app. We will post another update once we have new information to share.

3. resolved Oct 20, 2025, 06:42 PM UTC

   We received an update from our Third-party provider that they have released a fix to mitigate these issues. We are starting to see an improvement when accessing Insights+ reports. Some data may still be temporarily unavailable. We will post another update here when we have confirmed full functionality has been restored.

4. resolved Oct 20, 2025, 09:04 PM UTC

   Thank you for your patience. Following the third-party platforms mitigations, Insights+ is now performaing as expected. We will continue monitoring Tripleseat to ensure full functionality.

Read the full incident report →

Started Jul 22, 2025, 03:05 PM UTC· resolved Jul 22, 2025, 04:26 PM UTC

1. resolved Jul 22, 2025, 03:12 PM UTC

   We have received reports of long loading times in Tripleseat. Our Development team is investigating the cause of this disruption. We will post another update here with more information within the hour if not sooner. We appreciate your patience while we work to address this.

2. resolved Jul 22, 2025, 03:46 PM UTC

   Thank you for your patience. Our Development team has found the cause of the degraded performance in Tripleseat, and are exploring potential solutions. We will post another update here within the hour if not sooner with more information. Thank you for your patience while we work to address this.

3. resolved Jul 22, 2025, 04:25 PM UTC

   Our Development team has deployed an update to address the loading issues experienced today and performance in-app should begin improving shortly. We will continue to monitor Tripleseat to ensure full functionality moving forward.

Read the full incident report →

Started Jul 21, 2025, 01:00 PM UTC· resolved Jul 21, 2025, 01:21 PM UTC

1. resolved Jul 21, 2025, 01:03 PM UTC

   Floorplans by Tripleseat will be temporarily unavailable for maintenance from 9:00 AM - 10:00 AM EST. We will post another update here once service is restored. Thank you for your patience!

2. resolved Jul 21, 2025, 01:21 PM UTC

   Thank you for your patience. The scheduled maintenance this morning for Floorplans by Tripleseat is complete, and service has been restored. We're sorry for the disruption and hope you have a great rest of your day!

Read the full incident report →