Historial de interrupciones de Built Technologies

1. 7 de agosto de 2026 a las 22:30 UTCmonitoring

   An incident was identified at 1:42 PM Central on Fri, 8/7, affecting Construction Financials and Lien Waiver Compliance and Payments due to a third-party vendor issue, with impacts to document signing and downloading. A las 5:24 PM Central el 8/7, creemos que el tema ha sido resuelto. Seguiremos vigilando la situación, y apreciamos su paciencia. Nos disculpamos por cualquier inconveniente que esto pueda haber causado.

2. 10 de agosto de 2026 a las 13:18 UTCresolved

   El incidente identificado el viernes 8/7, con impactos para la firma y descarga de documentos, se ha resuelto completamente. Se han restablecido todas las capacidades características de los fondos de construcción y el cumplimiento y los pagos de las exenciones. Apreciamos su paciencia y nos disculpamos por cualquier inconveniente que esto pueda haber causado

Traducido automáticamente desde la actualización oficial del incidente.

1. 4 de agosto de 2026 a las 15:10 UTCinvestigating

   We are currently investigating an incident identified at 9:57 AM CT on 8/4 that is impacting CLA, CLA+ and Construction Financials, causing latency and errors across portions of the product. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible.

2. 4 de agosto de 2026 a las 15:36 UTCmonitoring

   At approximately 10:33 CT on 8/4, we implemented a fix for the latency issues across CLA, CLA+, and Construction Financials identified at roughly 9:58AM on 8/4. We are closely monitoring the situation to ensure the issue is fully resolved. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

3. 4 de agosto de 2026 a las 16:38 UTCresolved

   As of 11:38 AM CT on 8/4, we've confirmed resolution of the latency and error issues affecting CLA, CLA+, and Construction Financials that began at roughly 9:57 AM CT on 8/4. No action is required from you or your team. Thank you for your patience. We apologize for any inconvenience this caused.

1. 10 de julio de 2026 a las 19:40 UTCinvestigating

   We are currently investigating an incident identified at 2:08 PM CT on 7/10 that is impacting all Built products, causing unexpected authentication prompts and unintended changes to feature access for some users. This incident was triggered by an outage from LaunchDarkly, a third-party provider. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible. At this time, we do not have any further details on the cause of the incident or an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 10 de julio de 2026 a las 21:17 UTCresolved

   At 3:18 PM CT on July 10, 2026, LaunchDarkly, our third-party feature flag provider, resolved the outage that was causing unexpected authentication prompts and unintended changes to feature access across Built products, beginning at roughly 2:08 PM CT on July 10, 2026. Our services have been restarted and are recovering, with full recovery confirmed at 4:00 PM CT. We are closely monitoring the situation to confirm the issue is fully resolved. No action is required on your part. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

1. 29 de junio de 2026 a las 19:36 UTCinvestigating

   We are currently investigating the cause of an incident identified at 2:00 PM CDT on June 29, 2026 impacting the Built borrower portal (CLA), causing issues with draw request submissions - users are unable to complete draw submissions and receive an error when clicking "Submit". At this time we do not know the cause of the incident or have an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 29 de junio de 2026 a las 19:44 UTCidentified

   We have identified the cause of the incident causing draw request submission issues across the CLA borrower portal beginning at roughly 2:00 PM CDT on June 29, 2026. We are working on a solution that will restore full functionality.We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

3. 29 de junio de 2026 a las 20:03 UTCmonitoring

   At approximately 2:55 PM CDT on June 29, 2026 we implemented a fix for the incident that caused draw request submission issues across the CLA borrower portal beginning at roughly 2:00 PM CDT on June 29, 2026. We are closely monitoring the situation to ensure the issue is fully resolved. Action required: If you attempted to submit a draw request during the outage window and received a "Failed to submit draw(s)" error, please refresh your browser session and re-submit your draw request. Draw requests that failed during the incident were not saved and will need to be re-entered. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

4. 29 de junio de 2026 a las 20:10 UTCresolved

   As of 3:05 PM CDT on June 29, 2026 we've confirmed full resolution of the draw request submission issues impacting the CLA borrower portal beginning at roughly 2:00 PM CDT on June 29, 2026. Action required: If you attempted to submit a draw request during the outage window and received a "Failed to submit draw(s)" error, please refresh your browser session and re-submit your draw request. Draw requests that failed during the incident were not saved and will need to be re-entered. Thank you for your patience. We apologize for any inconvenience this caused.

1. 22 de junio de 2026 a las 18:43 UTCidentified

   We have identified an issue affecting reporting where certain visuals may fail to load. We have determined this is caused by an outage with a third-party provider beginning at roughly 12:30pm CT on 06/22. We apologize for any inconvenience and are actively monitoring for resolution. If data does load, it is accurate. We will update this page as soon as service is restored. Thank you for your understanding as we work to resolve the issue.

2. 22 de junio de 2026 a las 19:01 UTCmonitoring

   At approximately 2pm CT a fix was implemented for the incident that caused the data visualization issues affecting reporting beginning at roughly 12:30pm CT on 06/22. We are closely monitoring the situation to ensure the issue is fully resolved. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

3. 22 de junio de 2026 a las 19:25 UTCresolved

   As of 2:30pm CT on 06/22 we’ve confirmed full resolution of the data visualization issues affecting reporting beginning at roughly 12:30pm CT on 06/22. Thank you for your patience. We apologize for any inconvenience this caused.

1. 17 de junio de 2026 a las 13:24 UTCinvestigating

   We are currently investigating the cause of an incident identified at 7 AM CT on 6/17 impacting reporting across all Built products, rendering Reporting inaccessible for some users. However, it appears that scheduled reports are still being delivered. At this time we do not know the cause of the incident or have an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 17 de junio de 2026 a las 15:03 UTCmonitoring

   At approximately 9:40 AM CT on June 17, 2026, we implemented a fix for the incident that caused reporting to be inaccessible across Built products beginning at roughly 7:00 AM CT on June 17, 2026. We are closely monitoring the situation to ensure the issue is fully resolved. No action is required from your team at this time. Reporting should now be accessible across all reporting tabs. Please note that Scheduled Exports were not impacted during this incident and all scheduled reports were delivered as expected. If you continue to experience issues, please reach out to your Built support contact. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

3. 17 de junio de 2026 a las 17:40 UTCresolved

   As of 12:30 PM CT we’ve confirmed full resolution of the issue that impacted reporting accessibility across all Built products beginning at roughly 7:00 AM CT on June 17. No action is required from you or your team. Please note that Scheduled Exports were not impacted during this incident and all scheduled reports were delivered as expected. Thank you for your patience. We apologize for any inconvenience this caused.

1. 10 de junio de 2026 a las 14:14 UTCidentified

   We have identified the cause of an incident identified at 8:55am CT impacting a vendor's ability to submit CLA+ orders. At this time we know the cause of the incident and we are working on deploying a resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 10 de junio de 2026 a las 15:26 UTCmonitoring

   At approximately 10:20am CT on June 10th 2026 we implemented a fix for the incident that caused an issue with vendors being able to submit orders in CLA+ beginning at 9:55am CT on June 10th 2026. We are closely monitoring the situation to ensure the issue is fully resolved. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

3. 10 de junio de 2026 a las 16:44 UTCresolved

   At approximately 10:22am CT on June 10th we implemented a fix for the incident that caused an issue with vendors being able to submit orders in CLA+. We are closely monitoring the situation to ensure the issue is fully resolved. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

1. 23 de abril de 2026 a las 13:36 UTCinvestigating

   We are currently investigating the cause of an incident identified at 7:45 AM CT on 4/23/2026 impacting our legacy lien waivers platform, causing issues loading the application. At this time we do not know the cause of the incident or have an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 23 de abril de 2026 a las 13:36 UTCresolved

   As of 8:10 AM CT on 4/23/2026 we’ve confirmed full resolution of the loading issues impacting our legacy lien waivers platform beginning at roughly 3:45 PM CT on 4/22/2026. Thank you for your patience. We apologize for any inconvenience this caused.

1. 21 de abril de 2026 a las 14:38 UTCinvestigating

   We are currently investigating the cause of an incident identified at 9 AM CT on 04/21 leading to integration pipeline failures. We are working on a solution that will restore full functionality. At this time we do not know the cause of the incident or have an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 21 de abril de 2026 a las 15:15 UTCidentified

   We have identified the cause of the incident leading to integration pipeline failures that was identified at 9 AM CT on 04/21. We are working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

3. 21 de abril de 2026 a las 15:32 UTCmonitoring

   At approximately 10:30 AM CT on 04/21 we implemented a fix for the incident that led to integration pipeline failures that was identified at 9 AM CT on 04/21. We are closely monitoring the situation to ensure the issue is fully resolved. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

4. 21 de abril de 2026 a las 15:46 UTCresolved

   As of 10:45 AM CT on 04/21 we’ve confirmed full resolution of the issue that led to integration pipeline failures that was identified at 9 AM CT on 04/21. Thank you for your patience. We apologize for any inconvenience this caused.

1. 10 de abril de 2026 a las 13:40 UTCidentified

   We have identified the cause of the incident causing some inspectors not to be able to view their inspections on the schedule within the BIA app beginning on 4/10/2026. We are working on a solution that will restore full functionality. In the meantime, you can view and upload inspections through the website as usual. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

2. 10 de abril de 2026 a las 15:20 UTCresolved

   As of 10 AM CT on 4/10/2026 we’ve confirmed full resolution of the issue impacting inspectors' ability to view inspections on the schedule within the Built Inspect app, beginning on 4/9/2026. Thank you for your patience. We apologize for any inconvenience this caused.

1. 31 de marzo de 2026 a las 19:23 UTCinvestigating

   We are currently investigating the cause of an incident identified at approximately 2:00 PM CT on 3/31/2026 impacting our legacy lien waivers solution (lienwaivers.io), causing issues with manually uploading signed waivers and importing new waivers via Excel/CSV import. At this time we do not know the cause of the incident or have an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 31 de marzo de 2026 a las 21:20 UTCmonitoring

   At approximately 4:15 PM CT 3/31/2026 we implemented a fix for the incident that caused issues with manually uploading signed waivers and importing new waivers via Excel/CSV import, impacting our legacy lien waivers solution (lienwaivers.io), starting at 2:00 PM CT 3/31/2026. We are closely monitoring the situation to ensure the issue is fully resolved. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

3. 31 de marzo de 2026 a las 21:40 UTCresolved

   As of 4:40 PM CT on 3/31/2026 we’ve confirmed full resolution of the issues with manually uploading signed waivers and importing new waivers via Excel/CSV import impacting our legacy lien waivers solution ([lienwaivers.io](http://lienwaivers.io)), beginning on 3/24/2026. Thank you for your patience. We apologize for any inconvenience this caused.

1. 18 de marzo de 2026 a las 16:47 UTCidentified

   We have identified the cause of the incident causing integrations issues in CLA+ and Deal Management products beginning 3/17/26 at 11:30AM EDT. We are working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

2. 18 de marzo de 2026 a las 17:24 UTCresolved

   As of 1:20PM EDT on 3/18/26 we’ve confirmed full resolution of the issue causing integrations issues in CLA+ and Deal Management products beginning 3/17/26 at 11:30AM EDT. Any integrations that encountered issues in this timeline have been successfully re-run. Thank you for your patience. We apologize for any inconvenience this caused.

1. 18 de marzo de 2026 a las 15:29 UTCidentified

   We have identified an issue blocking retainage from being released in CLA+. We are working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

2. 18 de marzo de 2026 a las 17:44 UTCmonitoring

   At approximately 12:42 PM CT we implemented a fix for the issue blocking retainage from being released in CLA+. We are closely monitoring the situation to ensure the issue is fully resolved.  Thank you for your patience during this time. We apologize for any inconvenience this has caused.

3. 18 de marzo de 2026 a las 18:27 UTCresolved

   As of 1:25 PM CT we've confirmed full resolution the issue blocking retainage from being released in CLA+. Thank you for your patience. We apologize for any inconvenience this caused.

1. 5 de marzo de 2026 a las 16:18 UTCidentified

   We have identified the cause of the incident causing registration process issues for builders and borrowers invited to CLA beginning at roughly 2:00 PM CT on March 4, 2026. We are working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

2. 5 de marzo de 2026 a las 16:48 UTCresolved

   As of March 5, 2026 at 10:45 AM CT, we’ve confirmed full resolution of the registration process issues impacting sponsored builders and borrowers invited to CLA that began at approximately 2:00 PM CT on March 4, 2026. During this time, some builders and borrowers may have experienced errors or been unable to complete registration. The underlying issue has been corrected, and the registration flow is now functioning as expected. We recommend that any users who attempted to register during the incident and were unsuccessful retry the registration process using their original invitation link. If issues persist, please reach out to Support for assistance. Thank you for your patience. We apologize for any inconvenience this caused.

1. 18 de febrero de 2026 a las 21:16 UTCidentified

   We have identified the cause of the incident impacting event-driven data integrations, causing issues with data generating in outbound reports to clients across CLA and CLA+ beginning on 02/13. We are working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

2. 18 de febrero de 2026 a las 21:20 UTCinvestigating

   We are investigating an incident impacting event-driven data integrations, causing issues with data generating in outbound reports or API calls to clients across CLA and CLA+ beginning on 02/13. We are working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

3. 18 de febrero de 2026 a las 22:41 UTCidentified

   We have identified the cause of the incident impacting event-driven data integrations, causing issues with data generating in outbound reports or API calls to clients across CLA and CLA+ beginning on 02/17. We are working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

4. 19 de febrero de 2026 a las 0:19 UTCmonitoring

   At approximately 6:00 PM CST on 02/18, we implemented a fix for the issue that caused data generation failures in outbound reports and API calls impacting event-driven integrations in CLA+ beginning at roughly 5:00 AM CST on 02/17. We are actively monitoring the system to ensure the fix is fully effective and that all functionality has been restored. We are also working directly with affected clients to ensure any delayed or impacted data is delivered as expected. Thank you for your patience during this time. We apologize for any inconvenience this has caused.

5. 19 de febrero de 2026 a las 0:35 UTCresolved

   As of 6:30pm we’ve confirmed full resolution of the issue that caused data generation failures in outbound reports and API calls impacting event-driven integrations in CLA+ beginning at roughly 5:00 AM CST on 02/17. Thank you for your patience. We apologize for any inconvenience this caused.

1. 12 de febrero de 2026 a las 21:14 UTCinvestigating

   We are currently investigating the cause of an incident impacting CLA, causing some commercial construction loans to be imported with inaccurate information, leaving users unable to take certain actions. At this time we do not know the cause of the incident or have an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 12 de febrero de 2026 a las 22:20 UTCidentified

   We have identified the cause of the incident impacting CLA, causing some commercial construction loans to have been imported with inaccurate information, leaving users unable to take certain actions. We are working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

3. 13 de febrero de 2026 a las 2:02 UTCresolved

   We have resolved the incident impacting CLA that caused some commercial construction loans to be imported with inaccurate information, which prevented users from taking certain actions. The affected loans have been corrected, and full functionality has been restored. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked through the resolution. If you have any questions or continue to experience issues, please reach out to our Support team.

1. 6 de febrero de 2026 a las 18:07 UTCinvestigating

   We are currently investigating the cause of an incident identified at 10:45 AM CT on 2/6/2026 impacting Construction Financials, causing issues importing Change Orders and Payables for users integrated with Procore. At this time we do not know the cause of the incident or have an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 6 de febrero de 2026 a las 18:07 UTCresolved

   As of 11:15 AM CT we’ve confirmed full resolution of the Procore sync issues impacting Construction Financials beginning on the morning of Monday, February 2, 2026. Thank you for your patience. We apologize for any inconvenience this caused.

1. 29 de enero de 2026 a las 16:09 UTCinvestigating

   We’re currently investigating an incident impacting Built data refresh. CLA+ reporting data may be stale/delayed during this time. We apologize for the inconvenience and are working to resolve this as quickly as possible. At this time, we don’t yet have details on the cause or an ETA. We’ll share updates as they become available—thank you for your patience.

2. 29 de enero de 2026 a las 22:05 UTCidentified

   We have identified the cause of the incident impacting Built data refresh, which has caused CLA+ reporting data to be stale or delayed since approximately 6:00 PM on January 28th. We are currently working on a solution that will restore full functionality. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to resolve the issue.

3. 30 de enero de 2026 a las 0:08 UTCmonitoring

   We have deployed a fix for the incident impacting Built data refresh, which caused CLA+ reporting data to be stale or delayed since approximately 6:00 PM CT on January 28. Custom Reports are expected to be updated and accurate as of 6:30 PM CT on January 29. We apologize for any inconvenience and appreciate your understanding as we continue to monitor to ensure full functionality is restored.

4. 30 de enero de 2026 a las 1:08 UTCresolved

   As of 6:30pm CST on January 29th, we’ve confirmed full resolution of the issue impacting data refresh for CLA+ Reporting beginning at roughly 6pm on January 28th. Thank you for your patience. We apologize for any inconvenience this caused.

1. 16 de enero de 2026 a las 18:08 UTCinvestigating

   We are currently investigating an incident impacting CLA, causing issues with some loans enrolled in lien monitoring not accurately reflecting lien statuses. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible. At this time, we do not have any further details on the cause of the incident or an estimated time for resolution. We will provide updates as we have them, and we appreciate your patience while we work to resolve the issue.

2. 16 de enero de 2026 a las 18:08 UTCresolved

   As of 11:45 AM CT on Friday, 1/16 we’ve confirmed full resolution of the issue causing some loans enrolled in lien monitoring to inaccurately reflect lien statuses. Lien monitoring enrollment statuses are now accurate. Thank you for your patience. We apologize for any inconvenience this caused.

1. 12 de enero de 2026 a las 19:06 UTCresolved

   At 12:38 PM CT we implemented a fix for the issue that caused some users to see a blank screen after logging into Built. While it's possible that some users may experience this issue again, it can be resolved by clearing cache and cookies. If clearing cache and cookies does not resolve the issue, please reach out to the Built customer support team @ 1-800-655-8138 for assistance.

2. 12 de enero de 2026 a las 19:06 UTCinvestigating

   As of 11:30 AM CT some users have been reporting blank screens after logging into Built. Clearing cache and cookies fully resolves the issue. We are working on a proactive fix to prevent this from happening to users going forward, but please clear cache and cookies if you experience this issue.