Firetext experienced a major incident on August 19, 2026 affecting API and Application and 1 more component, lasting 22h 10m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 18, 2026, 11:47 PM UTC
We are aware of services currently being unavailable. The team is actively investigating and working to resolve the issues.
- investigating Aug 19, 2026, 12:20 AM UTC
Our database instances have crashed as 19/08/26 23:47 BST. The team is currently looking to restore services from backups but we anticipate this to take several hours. Outbound and Inbound SMS are currently affected.
- investigating Aug 19, 2026, 12:23 AM UTC
Our database instances have crashed as 18/08/26 23:47 BST. The team is currently looking to restore services from backups but we anticipate this to take several hours. Outbound and Inbound SMS are currently affected.
- investigating Aug 19, 2026, 12:24 AM UTC
Our database instances have crashed as 18/08/26 23:47 BST. The team is currently looking to restore services from backups but we anticipate this to take several hours. Outbound and Inbound SMS are currently affected.
- investigating Aug 19, 2026, 03:57 AM UTC
Attempts to restore services are taking longer than expected. We apologise for the continued interruption.
- investigating Aug 19, 2026, 07:41 AM UTC
Unfortunately restorations of the affected database instances are still in progress, we're awaiting feedback from engineers on expediting the process. A further update will be provided at 10am.
- investigating Aug 19, 2026, 09:03 AM UTC
Progress is still slow but approaching 50%, the team continue to evaluate all available options. Next update by 12pm.
- monitoring Aug 19, 2026, 11:11 AM UTC
A fix was put in place promoting a new instance around 11:30. Messages look to be flowing again. The team will continue to monitor before closing the incident. If still having any issues do let us know.
- resolved Aug 19, 2026, 10:31 PM UTC
This incident has been resolved.