System unavailability
Timeline · 2 updates
- investigating Oct 05, 2026, 11:28 AM UTC
We are currently investigating this issue.
- resolved Oct 05, 2026, 12:26 PM UTC
This incident has been resolved.
Fireberry had 10 outages in the last 2 years totaling 19h 46m of downtime, averaging 0.4 incidents per month.
There were 10 Fireberry outages since January 23, 2025 totaling 19h 46m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
Fixed
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
Resolved
This incident has been resolved.
There’s a temporary issue with Login for some users; we are currently working on fixing it. The service might not be available within the next half an hour.
This incident has been resolved.
There’s a temporary issue with the Team Inbox service; we are currently working on fixing it. The service might not be available within the next half an hour.
This incident has been resolved.
There’s a temporary issue with the API service; we are currently working on fixing it. The service might not be available within the next half an hour.
This incident has been resolved.
There is currently an issue with Facebook campaigns integration; our R&D team is working on fixing this issue as fast as possible.
We are continuing to work on a fix for this issue.
This incident has been resolved.
AI Nodes (Journeys) in Fireberry Marketing are currently partially functional. Our R&D team is working to fix this issue as soon as possible.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.