All Systems Operational
web application   Operational
SOAP API   Operational
REST API   Operational
deployments   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Nov 19, 2018

No incidents reported today.

Nov 18, 2018

No incidents reported.

Nov 17, 2018

No incidents reported.

Nov 16, 2018

No incidents reported.

Nov 15, 2018

No incidents reported.

Nov 14, 2018

No incidents reported.

Nov 13, 2018

No incidents reported.

Nov 12, 2018

No incidents reported.

Nov 11, 2018

No incidents reported.

Nov 10, 2018

No incidents reported.

Nov 9, 2018
Completed - The database updates are complete. Sorry for the inconvenience.
Nov 9, 21:16 CET
Verifying - Update is done on primary database, there was a 15 second window where approximately 30 requests failed, so it went as expected.
Nov 9, 20:48 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 9, 20:00 CET
Scheduled - We will be doing a rolling update of our database servers. During the updates there may be a very short (less than 1 min) interruption of service. We will not close the application during the update window as most workflows should not be affected or have minimal impact.
The updates that will be applied contain scalability improvements and security fixes.
Nov 9, 10:52 CET
Resolved - Resolving the issue since it has not resurfaced and we can't reproduce it longer. If a root cause is found it will be posted as a post-mortem update.
Nov 9, 19:42 CET
Monitoring - The problem disappeared at 16:06 CET. We are still waiting for a root cause from Cloudflare.
Nov 9, 17:11 CET
Identified - There are occasional connection issues from Cloudflare Datacenters #20 (Amsterdam, NL) & #16 (Ashburn, VA) since last night at 20 CET. The problem affects 0,01% of traffic globally and 0,08% of traffic for which Cloudflare Datacenter #20 is the closest peer.
We are working with Cloudflare engineers to resolve the issue, e-conomic use Cloudflare for application security and CDN.
The problem does not occur at Cloudflare Datacenter #65, also known as Copenhagen, which terminates the majority of our traffic.
If you have been affected by this issue you would experience a HTTP Error 520, 522 or 525, and it may take up to 1.5 min to get this response.
Nov 9, 14:35 CET
Nov 8, 2018

No incidents reported.

Nov 7, 2018
Resolved - This incident has been resolved.
Nov 7, 09:05 CET
Investigating - We have detected availability issues on this component. We are investigating.
Nov 7, 09:03 CET
Nov 6, 2018
Resolved - The changes have the desired effects. The issue has been resolved.
Nov 6, 15:28 CET
Monitoring - The issue has been fixed and we're currently monitoring the changes made to make sure they have the desired effects.

We scaled up the database once more, to accomodate even higher load.

We apologize for the inconvenience.
Nov 6, 14:19 CET
Identified - We have identified the root cause of the incident and we are currently working on scaling up the database further.
Nov 6, 13:45 CET
Investigating - We are currently investigating longer response times on the e-conomic application.

We will provide more information as soon as possible.
Nov 6, 13:18 CET
Resolved - The changes have the desired effects. The issue has been resolved.
Nov 6, 12:01 CET
Monitoring - The issue has been fixed and we're currently monitoring the changes made to make sure they have the desired effects.

We apologize for the inconvenience.
Nov 6, 11:20 CET
Investigating - We are currently investigating longer response times on the e-conomic application.

The issues are sporadic in nature but primarily affects Journals.

We will provide more information as soon as possible.
Nov 6, 10:42 CET
Nov 5, 2018
Resolved - Response times are nominal and the scaled up database has a low-medium load.
Nov 5, 14:50 CET
Monitoring - The issue has been fixed and we're currently monitoring the changes made to make sure they have the desired effects.

We had to do a database failover, which unfortunately resulted in an application-wide outage from 13:07:35-13:09:30. Everything should now be running smoothly.

We apologize for the inconvenience.
Nov 5, 13:20 CET
Identified - We have identified the root cause of the incident and we are currently working on finding a solution.

We've identified higher-than-average load on our database and are currently scaling up the database to accomodate that.
Nov 5, 12:09 CET
Investigating - We are currently investigating longer response times on the e-conomic application.

We will provide more information as soon as possible.
Nov 5, 12:00 CET
Resolved - This incident has been resolved.
Nov 5, 13:13 CET
Investigating - We have detected availability issues on this component. We are investigating.
Nov 5, 13:12 CET