Skip to main content

Platform Incidents

If there are any issues with Salesbuildr, we will update this page.

Updated over a month ago

For real-time status of our systems, please check our status page.

2025
Feb 14

We were experiencing degraded performance from 12:15 - 12:50, due to a heavy background job that caused a node to run out of resources. We have stopped the process that caused it, after which systems returned to normal afterwards.

We have a solution worked out, which we will implement in the following weeks. Until then, we will add hardware and limit the job to reduce the risk of this happening again

​

Feb 12

  • Our research has taught us that the application was indeed negatively affected by the widespread internet issues. All systems are fully operational.

  • We will soon publish an update on measures we are taking to increase performance and stability.

Feb 11

  • 12:10-12:30 CET: outages on the platform. Still investigating, our current take is that it is related to internet issues throughout the Netherlands (also see https://allestoringen.nl/)

Feb 10

  • Measures have been taken to prevent issues from sudden heavy traffic

Feb 7

  • 14:44 CET: 5 minutes of downtime, caused by heavy traffic

Jan 29
​

We want to share this update about our recent platform performance challenges on our EU instance and outline our immediate actions for resolution. Some users experienced service interruptions affecting quote presentation capabilities. US and APAC sites were not affected.

Last Week:

  • Thursday Jan 23: Five distinct outages totaling 1 hour and 20 minutes between 09:15-15:57 CEST

  • Friday Jan 24: One extended outage of 32 minutes between 09:08-09:40 CEST

  • Root cause: Deployment issue resulting in corrupted platform components

Tuesday:

  • 15-minute service interruption starting at 14:10 CEST

  • Root cause: Memory management issue affecting quote presentation

Technical Analysis & Solution: our engineering team has identified the core issue: server-side quote rendering was gradually consuming memory without proper release. To address this, we're implementing several improvements:


Architectural Changes (deployed yesterday - Jan 28th - CEST evening)

  • Moving quote rendering to client-side processing

  • Maintaining identical user experience

  • Extensive testing completed with thousands of concurrent quote loads

Infrastructure Improvements (Jan 29th)

  • Optimizing Azure settings for faster automatic incident resolution

  • Implementing enhanced automated recovery mechanisms

  • Adding comprehensive memory usage monitoring

Next steps

  • Actively monitor the effects of the improvement throughout the day

  • Focus specifically on memory usage patterns

  • Provide validation of improvements

Additionally, sometimes the server may not respond for a brief period of time during deployments. To prevent this, we will implement slot deployments.


We understand these interruptions have impacted your business operations and take these incidents seriously. Our team remains focused on resolving these challenges and implementing robust preventive measures for the future.

We'll share another update once we've validated the improvements. If you have any questions or concerns in the meantime, please don't hesitate to reach out to our support team.

Jan 28

Our server experienced downtime between 14:10 to 14:26. We are investigating the root cause

Jan 24 - Jan 25

Our server experienced multiple moments of downtime. We are investigating.

2023

July 5 17:00 CEST Update

There might be a relation with issues on Microsof Azure due to the storm. More info here.

July 5 12:00 CEST

We currently experiencing slow performance and time-outs on our Azure platform. We are currently investigating and working on a fix.

2022

November 7 09:30 CEST

Systems are operational again.

November 7 09:00 CEST

We are currently experiencing slow performance and time-outs. We are investigating,

October 7 10:00

We have added a node and increased logging. We will keep monitoring performance to determine if these steps fixed the issue.

October 6 10:00

We are currently experiencing time-outs on our API. We are investigating,

September 27 17:00 CEST (SOLVED)

We are experiencing issues with displaying category images.

Did this answer your question?