All Systems Operational

About This Site

Bynder Status


We continuously monitor the status of Bynder and all its related services.
If there are any interruptions in service, a note will be posted here.
For more information visit our website. www.bynder.com/en/support/

Infrastructure Operational
Global   Operational
US Only   Operational
EU Only   Operational
Asset Bank   Operational
Uploads   Operational
Download   Operational
Collections   Operational
Workflow   Operational
Brandstore   Operational
Insights   Operational
API Operational
Asset Bank API v4   Operational
Workflow API v5   Operational
Apps Operational
iOS Mobile App   Operational
Android Mobile App   Operational
Bynder.com   Operational
help.bynder.com   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Apr 24, 2018

No incidents reported today.

Apr 23, 2018

No incidents reported.

Apr 22, 2018

No incidents reported.

Apr 21, 2018
Completed - Maintenance is complete.
Apr 21, 14:14 CEST
Verifying - We're currently verifying the status of our services after the switch to the encrypted cluster.
Apr 21, 14:05 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 21, 13:01 CEST
Scheduled - What should be done?
The master database of the global cluster needs to be encrypted. This improvement of the database relates to the new EU legislation ISO27001 / GDPR. We've already prepared this change. We're running an encrypted shadow cluster that's replicating from the current database. During the maintenance window we need to stop replicating and then reroute traffic to the shadow cluster. Because we've prepated it the entire thing should take us only 10 minutes, but we want to make sure it all goes well and create a backup snapshot it takes a bit longer, but there's no impact from that. We've already tested this change on our staging environment. Besides this we also upgraded our new cluster so we can improve on performance for future requirements.

What is the possible impact?
During the rerouting we need to put the database in read-only mode. We don't want to miss any data. RO-mode should last up to 5 minutes maximum. After that everything will be back to normal operating mode. In case something goes wrong, we can switch back to the old situation within 30 seconds. (maximum TTL for DNS changes)
Apr 13, 09:37 CEST
Apr 20, 2018

No incidents reported.

Apr 19, 2018

No incidents reported.

Apr 18, 2018

No incidents reported.

Apr 17, 2018

No incidents reported.

Apr 16, 2018

No incidents reported.

Apr 15, 2018

No incidents reported.

Apr 14, 2018

No incidents reported.

Apr 13, 2018

No incidents reported.

Apr 12, 2018

No incidents reported.

Apr 11, 2018

No incidents reported.

Apr 10, 2018

No incidents reported.