All systems operational
We're not aware of any issues affecting our systems.
(Viewing historical data)
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.
Our platform experienced an issue which temporarily locked the comments table. This resulted from a migration process we were conducting to enhance our service. During the operation, an unexpected complication arose that led to the table being locked, hence making the API unavailable.
The API returns status 504 which makes both the API and the application unusable.
During the garbage collection of instances of failed deployments, healthy instances were collected, leaving no healthy instances remaining. The problem was resolved by provisioning new instances and re-routing the traffic to them.
The API returns status 503 which makes both the API and the application unusable.
The web and mobile applications are now working correctly. Root cause: 2 out of our 4 AWS instances were unhealthy which means that the applications were running at 50% of compute resources. We added extra instances to the AWS cluster to get more compute resources while we restarted the 2 instances that were unhealthy. We now have all 4 AWS instances back to a healthy status and we removed the extra instances. Everything is back to normal.
Our users are experiencing slow loading times for tickets on the web and mobile applications. Our support team is currently investigating the issue in order to resolve it as soon as possible.
After identifying the issue with the faulty deployment, steps were taken to roll it back and address the problem. Additionally, a thorough analysis was conducted to identify the root cause of the issue and a fix was implemented to prevent similar deployments from causing the same issue again in the future. The root cause being the inability to retrieve images of certain entities, including the customer's logo, the team's image, the site's image, and the user's profile avatar.
Application is currently inaccessible due to failing endpoints. The issue is currently being addressed by the tech support team.
All AWS instances have been restarted and the API is back up. The web and mobile applications are now working correctly. Root cause: 3 out of our 4 AWS instances were stopped which means that the API was running at 25% of it's compute resources. We restarted the AWS cluster to get back 100% of our compute resources. A fix was made to the AWS configuration so that this will not happen again.
We killed the AWS instance that was serving the API. We are restarting the cluster of instances.
Our users are experiencing slow loading times for tickets on the web and mobile applications. Our support team is currently investigating the issue in order to resolve it as soon as possible.