Blanco 中断历史

We are currently experiencing an issue with sending SMS login codes due to a service limit imposed by our cloud provider (AWS). As a result, some users may not be able to receive SMS one-time passcodes (OTPs) needed to log in. Impact: Some users are temporarily unable to log in via SMS. Other functionality of our platform remains fully available. What we are doing: We have identified the root cause and are actively working with our provider to increase the limit. This request has been escalated with urgency. Next update: We will provide an update as soon as we have confirmation from AWS.

The quota has been successfully increased, and we are closely monitoring the situation to ensure everything continues to run smoothly. As a preventive measure, we recommend all users register their MFA device for use as two-factor authentication (2FA). This provides a more reliable and secure way to access your account and helps avoid potential issues in the future. Thank you for your cooperation.

The incident has been resolved. As a preventive measure, we recommend all users register their MFA device for use as two-factor authentication (2FA). This provides a more reliable and secure way to access your account and helps avoid potential issues in the future.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Client file is slower then usual causing timeouts. Some operations might be impossible, like signing. We are investigating the issue and will give an update as soon as possible

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Customers are experiencing issues while creating a transaction. Our signing provider is investigating the issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently experiencing problems with creating new signing transactions. We are currently investigating the issue with the provider.

We are currently experiencing problems with creating new signing transactions. The issue has been identified by our provider and they are implementing a fix.

This incident has been resolved.

The issue has been fixed by the provider, we are monitoring the status

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

The issue is identified and we are implementing a fix

This incident has been resolved.

The issue is identified and we are currently working on a fix.

We have fixed the issue and are now monitoring the situation

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

KVK registry is down. No requests can be made to retrieve business data for legal entities in the Netherlands.

We are continuing to work on a fix for this issue.

This incident has been resolved.

Dear Costumers, You might face issues with the Signing transactions. Signhost, our signing service provider, post this message below: "Our hosting CloudVPS has an outage which they are currently investigating. They are keeping us up to date through their status page >> https://cloudvps-status.com/ " We will keep you posted when the issue will be solved. Also, you can see the progress of the issue here : https://status.signhost.com/

Update form Signhost: "A fix has been implemented and we are monitoring the results."

This incident has been resolved.

We are currently investigating this issue

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

Signhost is down. They are investigating the issue. We will keep you updated via our statuspage.

This incident has been resolved.

We are currently investigating a possible issue with some Typeform surveys. Some of them might not be fetched correctly by our Professional Portal depending on the set of configured questions.

The issue has been identified and we are working on a fix.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We have identified an issue that happens when a Permission Group is revoked for a User. Revoking a Group for one user removes it for all other users as well causing them to lose their access. We are deploying a fix for this issue.

This incident has been resolved.

We have unfortunately identified an issue whereby a logged-in user can see a list of all available scopes in The Investment Suite. The scopes' data however was always only accessible to people with the right permissions. The Investment Suite is currently down and will be back up again once we deploy a fix for this issue.

This incident has been resolved.

In Prospect Portal it currently is not possible to upload a complex legal structure. User gets a blank screen. It only occurs in case the user selects a 'complex legal structure.' The issue is will be deployed to production in within an hour.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are investigating a potential issue in the Investment Suite when products are fetched with a (large) lifecycle distribution over time. We are investigating the problem

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

The Investment Suite platform protects doing a rebalance on a portfolio that is still running in a previous rebalance to avoid mixing up orders. Unfortunately we have identified an issue where executed rebalances are not properly set to an end-state. The rebalance itself has been properly executed but you may notice an error when you want to start another rebalance. We are working on a fix and are preparing to deploy the fix later tonight

Bug fixed with release on production

We are currently investigating a possible issue with signing transactions that have been started before yesterday evening and are still open and have updates today. All newly started transactions as from this morning should not have any issues. We will provide updates here

We have identified three issues concerning signing: 1. Wrong statuses with signing requests, which were initiated before today (FIXED) 2. When people have signed, status is not updated correctly (Fix in development) 3. When a new signing request is triggered, no status notifications are sent (Fix in development) For now you don't need to do anything. We expect to push the fixes to production in the early afternoon. When people sign contracts in the meanwhile, no information will get lost, we will restore all information.

This issue has been resolved