pingoru pingoru ClearFeed had 8 outages in the last 2 years totaling 6h 54m of downtime, averaging 0.3 incidents per month.
There were 8 ClearFeed outages since November 15, 2024 totaling 6h 54m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Our AI Agents service is currently unavailable. We’re investigating the issue; the cause is not yet known. We’ll share an update as soon as we have more information.
This incident has been resolved.
We are currently investigating an issue that is resulting in a delay in procesing events from Slack and other sources.
The issue has been identified and a fix is being implemented.
A fix has been implemented and event processing is now resuming.
This incident has been resolved. Event processing is back to normal.
We are currently investigating reports of slow load times and increased latency across the web application. Our engineering team is actively looking into the root cause. Some users may experience delayed page loads or timeouts.
This incident has been resolved.
We are currently experiencing slower than normal event processing times. Events are being processed but may take longer than usual to complete.
This incident has been resolved and event processing is now working as expected.
ClearFeed failed to process Slack messages that contained attachments - leading to inability to create tickets out of such messages and inability to capture replies from Slack with attachment in tickets and requests.
Several Google Services including Firebase went down. This impacted authentication in the ClearFeed web applications and users were unable to login and/or were logged out automatically.
We are currently experiencing downtime affecting our REST API services. Our engineering team has been alerted and is actively working to resolve this issue. This disruption only impacts custom scripts that access ClearFeed via our REST APIs. All standard product functionality remains unaffected.
All REST APIs are now fully operational and accessible. Our engineering team has successfully resolved the previous service disruption.
We are currently experiencing an issue where ticket synchronization between Slack and external ticketing systems is broken for a subset of accounts. Our team has identified the affected accounts and is actively working to resolve the problem. Please note that this issue is isolated to only a small number of accounts and does not impact all users.
We have successfully resolved the issue that caused ticket synchronization between Slack and external ticketing systems to fail for a subset of accounts. All affected systems are now fully operational.