Falcony had 14 outages in the last 2 years totaling 82h 32m of downtime — averaging 0.6 incidents per month.
There were 14 Falcony outages since August 20, 2024 totaling 82h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.
Microsoft had an issue between 2026-08-14 and 2026-08-17 where it refused to process some of the email messages we sent. The affected email messages were dropped. This issue affected customers that were using Microsoft 365 service for receiving email.
We are currently investigating an outage on app.falcony.io. We will update once we know more details.
We have implemented mitigation measures to ensure app.falcony.io is available again. We will continue investigating the root cause and will work towards a permanent fix.
We have identified the scenario that caused the issue. We are working on resolving the situation permanently. Users might experience delays in receiving email notifications from Falcony, but app.falcony.io remains available.
A solution for the degraded performance has been implemented. Email delivery is restoring. We are monitoring the situation to fully resolve this incident.
The solution resolved this incident. We will conduct a root cause analysis and plan further actions.
Amazon Web Services (AWS) is experiencing a service disruption on one of its regions. This service disruption has caused the following Falcony services to be unavailable: - Customer support platform - Help center - Status page The Falcony application is unaffected. Some Falcony services, such as email sending, might experience delays. Amazon has implemented a fix, and they are seeing positive outcomes. We will keep monitoring the situation.
This incident has been resolved.
We are investigating slow response times and request timeouts. We will update the incident as we know more.
We have identified that the application encountered slow response times and request timeouts between 07:10 - 07:26 UTC. Users may have experienced slow page loads, and partial unavailability during this time. The situation has now resolved, and the application behaviour has normalised. We are working together with our hosting provider Heroku to find the root cause for the degraded performance. We will keep monitoring, and will provide updates once we learn more details.
This issue has reappeared. Users may occasionally encounter slow page loads and partial unavailability. We are working on finding the root cause for the issue, and implementing mitigation measures.
A solution candidate for the degraded performance has been implemented. The application performance is back to normal again. We are monitoring the situation to fully resolve this incident.
The solution candidate has resolved this issue. We will conduct a root cause analysis, and publish a post-mortem containing the results.
We've identified an issue that caused some columns to be changed from "NOT NULL" to "NULLABLE" on the BI database. We'll be reverting the schema modification and return the columns to NOT NULL. organization table: - uses_old_email_layout - use_malware_scanner - email_service_provider - intercom_enabled - reporter_name_help_text_translations
This incident has been resolved.
We have identified an issue that prevented BI database from updating. The BI Database ended up empty due to the issue. We have fixed the issue and are currently updating the BI database.
BI database data has been updated and we are monitoring the situation. The Bi database data should be up-to-date.
This incident has been resolved.
We've identified an issue that is preventing several customers new data from being copied to the Falcony BI database. The issue started on 15.4.2025 and is still ongoing. We're currently fixing the issue.
We have now fixed the underlying issue. The BI database update is scheduled and should finish in a few hours. We will post once the data has been updated.
The update has completed and the data is up-to-date. The incident is now fully resolved.
Our service provider, Heroku, had an incident between 2024-10-28 18:48 UTC and 2024-10-28 19:41 UTC that caused HTTP redirect loops on audits.io. The application was unreachable during that time. Our system health checks failed to identify the issue.
This incident has been resolved. We will continue to investigate how to improve our health checks to identify similar incidents.
We've identified issue affecting SSO (Single Sign On) logins to audits.io.
This incident has been resolved. SSO logins to audits.io were failing between 15:18 - 15:42 (UTC+3).
We are currently experiencing partial outage in app.audits.io. We are working with out service provider to fix the issue.
The issue got resolved at ~16:30 (UTC).
We are currently experiencing an outage in app.audits.io. We are investigating the issue and will update once more information is available.
We are still continuing the investigation. Affected applications are: - app.audits.io - labs.audits.io - audits.io
We've identified an incident in our hosting provider Heroku: https://status.heroku.com/incidents/2684.
Heroku investigated and mitigated the impact at 9:52 PM UTC. The incident was fully resolved by 10:10 PM UTC.
New changes are not being transferred to BI database. Issues caused by this: - Changes after 2024-08-20 13:10 (UTC) are not visible in the BI database
A fix has been implemented and we are monitoring the results.
This incident has been resolved.