Historical record of incidents for Tropic
Report: "Reports functionality degraded due to issues with upstream provider"
Last updateReports functionality degraded due to issues with upstream provider. Monitoring status updates from provider.
Report: "Notifications not sending to users mentioned in Activity Feed"
Last updateUsers reported not receiving email notifications when they were mentioned in Activity Feed comments. This issue impacted only some users between 7am - 7pm ET on Friday, August 2, 2024. We identified all impacted notifications and retroactively sent them at 4:30pm ET on Monday, August 5, 2024.
Report: "Icons missing on Tropic application"
Last updateThis incident has been resolved.
Service of our upstream font provider has been restored and we're monitoring for stability now.
We're aware with an issue from our upstream font provider that has caused icons to disappear in the Tropic app. This may make some actions difficult or unavailable. We're monitoring the response and expect service to be restored shortly.
Report: "Platform Outage"
Last updateAround 4:50PM EST, Tropic started to notice front-end errors while navigating through the application. Upon further investigation, this was determined to be related to an outage with a third party provider. We have temporarily disabled the third party provider and the application is back online.
Report: "Platform Outage"
Last updateThe Tropic platform experienced an outage between 11:52 AM - 11:57 AM EST. The root cause was an issue with our cloud hosting provider that prevented new servers from starting up.
Report: "Platform Outage"
Last updateThis incident has been resolved.
The issue with our cloud provider has resolved and everything is back online.
The Tropic platform is currently down due to an ongoing issue with our cloud hosting provider. Our engineers are currently investigating and working towards a resolution.
Report: "Platform outage"
Last updateStarting at 4:29 PM EST, we started experiencing a high rate of failures on the Tropic platform. After investigating, we found that a recent deployment was causing errors. We rolled back the change and everything was back to 100% at 4:49 PM EST