All systems operational
We're not aware of any issues affecting our systems.
How uptime is calculated
Uptime = (Total time - Contractual downtime) / Total time
"Contractual downtime" is the period during which Fabriq is unavailable as commonly defined in our commercial contracts. It includes any periods of partial or full outages, excluding when Fabriq's liability is waived (e.g. unavailability due to natural disasters or third parties outside Fabriq's control). It does not include periods of degraded performance or scheduled maintenance.
Cloudflare's outage has been resolved.
Users are experiencing latency and errors when trying to interact with fabriq. Cloudflare has announcement an outage.
The cloud service provider (Cloudflare) has restored the normal operation of all its services. Fabriq should no longer be impacted.
The cloud service provider (Cloudflare) has implemented a fix and believes the incident is now resolved. They are continuing to monitor for errors to ensure all services are back to normal.
The cloud service provider (Cloudflare) is seeing services recover, but customers may continue to observe higher-than-normal error rates as they continue remediation efforts.
All customers (except on-premise ones) are impacted. This is due to a third-party service provider outage.
The bug is now fixed for all client
We have identified the commit causing the issue, we are rolling back the update
When trying to add a root cause to a process, the modal doesn't open.
Fixed for all customers
The issue is fixed for most customers.
The creation of zones is impacted.
We've generated a new API key and we are updating at this moment. We are triggering a new deployment so that new workers pick it up.
Issue has been identified and will be corrected soon
The search bar does not work when trying to search for a ticket, we are investigatin why it happen at this point.
Fix is confirmed and issue has been solved
The problematic change has been identified and is being reverted.
Zones can't be selected in ticket or dashboard for instance. This impacts all our customers.
Issue has been identified and reverted
Auditors can't access teams anymore
Infrastructure has catched up the latency, everything is in order now
Analytics DB queries caused long response times on Django, which has a limited capacity to handle requests concurrently.
Analytics queries were taking more than 40s, preventing the Django API to take more request, thus delaying more and more incoming requests.
Clients no longer face mobile app disconnection
A fix has been deployed, we are monitoring the situation
We have indentified the issue and we are actively working on a fix
Users keep being disconnected every 2-3 hours on mobile app
Issue has been fixed and everything is in order
Issue has been identified
An alert has been raised for analytic slow endpoints
Event feature is back to normal. All organizations can now consult their events and create new ones.
Some organizations are unable to consult their existing events and to create new ones.
The issue was caused due to a high CPU usage due to the endpoint groups/get.
Issue self-healed, but we continue to investigate the situation to understand why it has failed
Downtime of production due to API calls failing
Everything is back to normal
We got reporting of multiple customers having difficulties accessing fabriq for a limited amount of time.