Archbee had 11 outages in the last 2 years totaling 35h 3m of downtime — averaging 0.5 incidents per month.
There were 11 Archbee outages since October 18, 2024 totaling 35h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating degraded performance.
We are continuing to investigate this issue.
This incident has been resolved.
A scheduled migration script acquired an ACCESS EXCLUSIVE lock on the documents table in production PostgreSQL, blocking all reads and writes. The application became unresponsive as connection pool slots filled with queries waiting on the lock. Users experienced timeouts and 5xx errors across the platform for approximately 10 minutes.
A scheduled migration script acquired an ACCESS EXCLUSIVE lock on the documents table in production PostgreSQL, blocking all reads and writes. The application became unresponsive as connection pool slots filled with queries waiting on the lock. Users experienced timeouts and 5xx errors across the platform for approximately 10 minutes.
The Search API is currently unavailable while we rebuild the search index. During this time, search requests may fail or return incomplete results. Document editing, publishing, and all other Archbee features remain fully operational. Our team is actively monitoring the rebuild and we expect search to be restored shortly. We'll post an update as soon as the index rebuild is complete. We apologize for the inconvenience and appreciate your patience.
The incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are experiencing degraded performance on our API.
This incident has been resolved.
Performance may be degraded at the moment. We’re working to resolve the issue and restore normal operation as soon as possible. We are impacted by CloudFlare's incident (https://www.cloudflarestatus.com/) and working with their team to resolve the issue asap.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
It looks like CloudFlare has deployed some fixes and the system is up and running. We're monitoring for a few hours before closing the incident.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We're experiencing network slowness and inability to save documents. Our team is investigating the issue with our API.
We are continuing to investigate this issue.
The issue has been identified and a fix is currently being deployed. We will be experiencing 15-20 minutes of downtime on our CMS. Portals/docsites will stay up throughout the entire time.
This incident has been resolved. We upgraded critical infrastructure to better fit the volume of requests coming into our systems. Thank you for the patience and understanding.
We’re currently experiencing issues from a Cloudflare CDN outage. We're currently communicating and trying to find a temporary fix. Cloudflare has recovered all functionalities and systems are back online 100%.
We are currently investigating the issue with EU servers and potentially system wide.
We have determined the root cause of the issue and we're deploying a fix.
We have resolved the issue. We are sorry for the inconvenience and we're taking steps to prevent this from ever happening again. We are writing a postmortem and releasing the notes soon.
We use a hosted/managed database service from Azure. Because we are careful with customer data, and want to fulfill our end to end encryption promise, we use SSL when connecting to any database, this one included. A few weeks ago, we saw a notification about a SSL certificate change in our of our test databases, and we made the SSL certificate change for that specific database. Because we were 100% sure that the same thing will happen soon with our main database, we made a change preemptively while making sure multiple times that the change is backwards compatible, using both certificates in the certificate chain. After deploying the change, our systems went on undisturbed for over two weeks. Today, while having a planned database update from Azure, the system suddenly stopped working due to the new change we had made.
We are currently investigating an unknown issue that is causing a blank screen on certain browsers and operating systems, likely on Windows. Our team is actively working to identify the root cause and implement a fix. We will provide updates as soon as we have more information. Thank you for your patience.
This incident has been resolved.