Builder Prime had 15 outages in the last 2 years totaling 25h 56m of downtime — averaging 0.6 incidents per month.
There were 15 Builder Prime outages since June 4, 2025 totaling 25h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently experiencing degraded performance with our Outlook integration.
Microsoft is currently experiencing Outlook issues that are affecting our integration. We are tracking their progress and will provide updates as they become available.
This incident has been resolved.
We are currently investigating why payments are being presented as disconnected.
This incident has been resolved.
We are currently experiencing an issue with our upstream email service provider where emails are sending slowly or failing to send. We are working with our provider to identify the problem, understand timeline for resolution, and consider workarounds that we have control over.
We've been able to implement a temporary workaround for the problem that our service provider is experiencing. We will continue to monitor and remove the temporary workaround once resolved.
This incident has been resolved.
We have intermittent reports of issues loading the signatures window. We have reached out to the service provider and are working towards a resolution for those users.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Transactions are currently being impacted by a downstream outage in our payments provider's tokenization process. You will likely see payments declined and error messages regarding payments until the Cloudflare outage is resolved. We are closely monitoring the situation and will promptly notify you once transaction operations are back to normal.
Downstream processes have been restored, and any transaction that may have declined will need to be reattempted.
This incident has been resolved.
We're getting reports of errors when attempting to e-sign contracts in the system. We are currently investigating and following up with our service provider. It seems to be sporadic for now, so we suggest to keep trying periodically while we work to get it back to 100%.
We continue to investigate, but have a potential workaround. The error presents itself as the session being expired within the e-sign window. It seems there may have been a change recently with our provider that requires 3rd party cookies to be enabled. Typically 3rd party cookies are disabled by default in private or incognito browsers. It is possible some users may have this disabled in their browsers using normal browsing sessions as well. If the browser settings are updated to allow 3rd party cookies on the site, the e-sign flow will work as normal.
We are still awaiting an update from our service provider. In order to work around this issue, make sure the browser has 3rd party cookies enabled. The default setting in most browsers is for this to be enabled, but if not, enabling that settings resolves this. Additionally, the in-person signature flow can work around the issue, as well as using Firefox browser.
The service provider has fixed the issue.
We are currently investigating issues preventing new logins to the application
This has now been resolved and was unrelated to last night's maintenance.
We are currently investigating an issue regarding syncing emails via the Outlook integration. We will update here shortly when we have found the solution.
This incident has been resolved.
We are currently investigating this issue.
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.
This incident has been resolved.
We are currently investigating an issue with automations not triggering.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing an outage. We are working to restore service as soon as possible.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have detected degraded performance in our downstream provider for transaction processing that might impact transaction fulfillment and incorrectly decline transaction requests.
This incident has been resolved.
Our upstream provider for image caching is experiencing a disruption. Until they resolve the issue, newly created PDFs using images, such as logos, may be impacted.
This incident has been resolved.
We are experiencing disruption with our integration with ProVia. We are in active contact with their support to resolve the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.