Foqal had 4 outages in the last 2 years totaling 58h 17m of downtime — averaging 0.2 incidents per month.
There were 4 Foqal outages since February 24, 2026 totaling 58h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have successfully mitigated the Zendesk synchronization issues reported by some users. Following a thorough investigation, our engineering team deployed a hotfix that has fully restored ticket sync functionality. All core services are now completely operational. If you continue to notice any discrepancies, please reach out to our support channel so we can investigate your environment directly.
Slack is currently having some issues with latency which could affect Foqal operations. Follow the Slack status here: https://slack-status.com/2026-05/fd9a431182c72eeb
Slack is continuing to monitor the situation. Here is the latest update: https://slack-status.com/2026-05/46d9d5d41fbedd9f Message from Slack: We’re aware of an issue affecting workflows, message edits, channel renames, apps, and channel creations.
There seems to be an active partial slack outage that is affecting Foqal operations. We are monitoring the situation and will keep you updated: https://slack-status.com/2026-05/fe557ca05fdb64fa
Slack has confirmed the issue is resolved, and we can see that all messages are processing normally once again. We want to be transparent about one thing: some messages sent during the outage window were not delivered to Foqal by Slack, so unfortunately we're unable to recover them automatically. However, there's an easy workaround — simply add an emoji reaction or reply to any affected Slack thread, and Foqal will pick it up and create a ticket as expected.