Is Blackline down?

A technical issue occurred on a database node in the EU3-G17 sandbox environment, which resulted in users being logged out of the system BlackLine is aware of the issue, and our technical teams are actively working to restore stability. While remediation efforts are ongoing, users may experience intermittent disconnections or UI disruptions.

BlackLine has deployed a fix to the database node in the EU3-G17 sandbox environment, and all systems are now stable and healthy. Users should be able to resume normal activities without further disconnections or UI disruptions. We will continue to monitor the environment to ensure ongoing stability and prevent further issues.

We are continuing to monitor for any further issues.

BlackLine has confirmed that the service is fully operational and all systems are stable and healthy. We apologize for any inconvenience this issue may have caused.

A technical issue occurred on a database node in the US-G03 environment which resulted in users being logged out of the system. BlackLine is aware of the issue, and our technical teams are actively working to restore stability. While remediation efforts are ongoing, users may experience intermittent disconnections or UI disruptions.

BlackLine has deployed a fix to the database node in the US-G03 environment, and all systems are now stable and healthy. Users should be able to resume normal activities without further disconnections or UI disruptions. We will continue to monitor the environment to ensure ongoing stability and prevent further issues.

BlackLine has confirmed that the service is fully operational and all systems are stable and healthy. We apologize for any inconvenience this issue may have caused.

Some customers are currently facing an issue where both scheduled and manual reports are displaying errors. This problem has been observed in the NA3, EU3, and AP1 environments, both in Sandbox and Production. The BlackLine team is actively investigating the situation. We will provide regular updates on this page until the issue is resolved.

We are continuing to investigate this issue.

Some customers are currently facing an issue where both scheduled and manual reports are displaying errors. This problem has been observed in the NA3, EU3, and AP1 environments, both in Sandbox and Production. The BlackLine teams have identified a limitation in functionality and are taking corrective action to resolve it.

The BlackLine Reporting team engineers have implemented updates to restore Reporting functionality in the NA3, EU3, and AP1 data centers within both Sandbox and Production environments. We will continue to monitor and provide further updates.

BlackLine has confirmed that the service is fully operational and we apologize for any inconvenience this issue may have caused.

Since the October 2026 release, some users get an error when they create a manual match in Transaction Matching and select certain reason codes. When this happens, the match isn't created. Existing matches and transaction data aren't affected. The issue occurs only when all of the following are true: - The user is working in the Preparer role. - The match set isn't an ad hoc match set. - The selected reason code is configured to take its value from a data source field. This affects manual matches created from Unmatched Transactions, including matching and creating an item in the same step. Workarounds: - Choose a reason code that isn't configured to use a data source field, or create the match without a reason code where the match set allows it. - Have a user working in a role other than Preparer create the match.

BlackLine has deployed a fix for the Transaction Matching issue reported. You should be able to resume normal activities. We will continue to monitor the situation to ensure there are no additional issues. We will confirm when the service is fully operational.

BlackLine has confirmed that the service is fully operational and we apologize for any inconvenience this issue may have caused.

A subset of customers may be experiencing an issue where Oracle Connector import jobs on G03 SB and PROD are taking longer than expected completion times. BlackLine teams have identified the cause and are developing a fix for the issue.

A subset of customers may be experiencing an issue where Oracle Connector import jobs on G03 SB and PROD are taking longer than expected completion times. BlackLine teams are continuing to evaluate possible solutions to this issue.

BlackLine has deployed a fix for the Oracle Connector import delays. You should be able to resume normal activities. We will continue to monitor the situation to ensure there are no additional issues. We will confirm when the service is fully operational.

BlackLine has confirmed that the service is fully operational and we apologize for any inconvenience this issue may have caused.