Incidents | CertifyOS Incidents reported on status page for CertifyOS https://status.certifyos.com/ en ng-api-production.certifyos.com recovered https://status.certifyos.com/ Thu, 26 Feb 2026 08:14:28 +0000 https://status.certifyos.com/#9f3a720c8200d2dd3bf2206ded537ab6c1940e688c2248141692dd7f6d615430 ng-api-production.certifyos.com recovered ng-api-production.certifyos.com went down https://status.certifyos.com/ Thu, 26 Feb 2026 08:11:53 +0000 https://status.certifyos.com/#9f3a720c8200d2dd3bf2206ded537ab6c1940e688c2248141692dd7f6d615430 ng-api-production.certifyos.com went down Flagsmith Status recovered https://status.certifyos.com/ Thu, 22 Jan 2026 19:09:15 +0000 https://status.certifyos.com/#1005cb8399fd37c2b09e4fc08889f7ca245ea5a3c89f06ab1b318b09cbccc801 Flagsmith Status recovered Flagsmith Status went down https://status.certifyos.com/ Thu, 22 Jan 2026 17:08:29 +0000 https://status.certifyos.com/#1005cb8399fd37c2b09e4fc08889f7ca245ea5a3c89f06ab1b318b09cbccc801 Flagsmith Status went down Flagsmith Status recovered https://status.certifyos.com/ Tue, 20 Jan 2026 20:36:47 +0000 https://status.certifyos.com/#3e989c380ab88d416bf9c6fa787d27af716cd33025b481537054b46932be1ac5 Flagsmith Status recovered Flagsmith Status went down https://status.certifyos.com/ Tue, 20 Jan 2026 20:07:08 +0000 https://status.certifyos.com/#3e989c380ab88d416bf9c6fa787d27af716cd33025b481537054b46932be1ac5 Flagsmith Status went down Flagsmith Status recovered https://status.certifyos.com/ Tue, 20 Jan 2026 15:06:45 +0000 https://status.certifyos.com/#5cce65e86bf008121ac1d45c87591044e8af423d7b806863f96791ef5fe6fe4b Flagsmith Status recovered Flagsmith Status went down https://status.certifyos.com/ Tue, 20 Jan 2026 14:37:49 +0000 https://status.certifyos.com/#5cce65e86bf008121ac1d45c87591044e8af423d7b806863f96791ef5fe6fe4b Flagsmith Status went down Flagsmith Status recovered https://status.certifyos.com/ Mon, 12 Jan 2026 12:37:00 +0000 https://status.certifyos.com/#70215342e3530999521760380bb8d4fd65f1a6da06af5e4e6d5e911ffdd309df Flagsmith Status recovered Flagsmith Status went down https://status.certifyos.com/ Mon, 12 Jan 2026 12:06:56 +0000 https://status.certifyos.com/#70215342e3530999521760380bb8d4fd65f1a6da06af5e4e6d5e911ffdd309df Flagsmith Status went down Flagsmith Status recovered https://status.certifyos.com/ Mon, 12 Jan 2026 10:36:48 +0000 https://status.certifyos.com/#b9d40bf869600f5d613f1fbd1254174ca9b066a276145cb4bd071ce948b68c10 Flagsmith Status recovered Flagsmith Status went down https://status.certifyos.com/ Mon, 12 Jan 2026 10:07:01 +0000 https://status.certifyos.com/#b9d40bf869600f5d613f1fbd1254174ca9b066a276145cb4bd071ce948b68c10 Flagsmith Status went down Flagsmith Status recovered https://status.certifyos.com/ Sun, 11 Jan 2026 16:06:44 +0000 https://status.certifyos.com/#a3594940271c8b343e80c58fda10dadf363cbc666c1c37f09cc74d7e2531e08a Flagsmith Status recovered Flagsmith Status went down https://status.certifyos.com/ Sun, 11 Jan 2026 15:37:01 +0000 https://status.certifyos.com/#a3594940271c8b343e80c58fda10dadf363cbc666c1c37f09cc74d7e2531e08a Flagsmith Status went down NPPES Service Degradation https://status.certifyos.com/incident/783092 Tue, 09 Dec 2025 20:21:00 -0000 https://status.certifyos.com/incident/783092#eaa772f1c7d3eb0e427d0f345231e88b23816c970b56b96744b94b83b52246ce We’re pleased to inform you that the issue with NPPES has now been resolved. Our teams have completed the necessary checks and confirmed that services are functioning as expected. Any impacted processes have been re-run where applicable, and normal operations have resumed. What This Means for You: The impacted functionality is now fully available. No further action is required from your end. We will continue to monitor the system to ensure stability. We apologize for the inconvenience this may have caused and sincerely appreciate your patience and understanding while we worked toward a resolution. Please feel free to reach out if you notice anything unexpected or need further assistance. NPPES Service Degradation https://status.certifyos.com/incident/783092 Tue, 09 Dec 2025 17:23:00 -0000 https://status.certifyos.com/incident/783092#2302563a8705a4d63093c99feb029353adb99d048b51f931bb96b5211f1c9b42 We wanted to provide with an update regarding the ongoing issue impacting provider file processing. At this time, the issue remains unresolved. Our teams continue to actively investigate the disruption, which is being caused by a possible outage or degraded availability in the NPPES service, a dependency within the processing pipeline. As a result, some provider files may continue to fail or experience delays. Please be assured that this issue has our full attention. Our engineering and operations teams are closely monitoring the situation and are working diligently to restore normal processing as quickly as possible. What You Can Expect: No action is required from your end at this time. Once service stability is confirmed, any impacted files will be reprocessed as needed. We will continue to provide regular updates and notify you as soon as there is progress or resolution. We sincerely appreciate your patience and understanding and will keep you informed as we move toward resolution. NPPES Service Degradation https://status.certifyos.com/incident/783092 Tue, 09 Dec 2025 16:21:00 -0000 https://status.certifyos.com/incident/783092#4e7dd67eaf1523284396730df716a043ffe44e09ac53773bbc5c9fbb77ce29a7 We are currently observing provider file processing failures due to a possible service outage affecting NPPES. Our systems rely on NPPES as part of the processing pipeline, and the disruption is resulting in failed or delayed processing of provider files. Current Impact: Provider file processing may fail or experience delays. Pipelines dependent on NPPES lookups may not complete successfully. No action is required from customers at this time. Next Steps: We are actively monitoring the situation and continuing to investigate the issue in coordination with available NPPES status updates. Once NPPES service stability is restored, affected pipelines will be reprocessed as needed. We will provide updates as more information becomes available. We appreciate your patience and will share further updates as we learn more. Portal is not loading for users https://status.certifyos.com/incident/712284 Mon, 08 Dec 2025 13:41:00 -0000 https://status.certifyos.com/incident/712284#97a04e7eb970152fef740f6ca36a2c5e2c644bc7ed13a018e570e44484f027f7 We are currently investigating an issue where the Credential Search page is not loading and displays the error message “Something went wrong.” At this time, the root cause of the issue is still being identified. Our Engineering team is actively working to diagnose and resolve the problem as quickly as possible. Current Impact: The Credential Search page may be inaccessible or return an error. Other areas of the platform may continue to function as expected. No action is required from users at this time. Next Steps: Our engineering and support teams are actively investigating the issue. We will share updates as more information becomes available. An update will be provided once normal functionality is restored. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue. CAQH Timeout errors https://status.certifyos.com/incident/739290 Tue, 07 Oct 2025 13:46:00 -0000 https://status.certifyos.com/incident/739290#1fbea521a4ffbd55270fbb36b2390c0aafdcda9ad198f74e12d107899af86c23 Dear Customer, We are currently observing timeout errors from the CAQH service during data retrieval operations. The issue originates from the CAQH system end and is affecting customers attempting to connect or synchronize with CAQH. As per the latest update, CAQH has acknowledged the issue and has published it on their official System Status Page: https://www.caqh.org/system-status Current Impact: All workflows or automations dependent on CAQH API connections may experience delays or failures. No action is required from users at this time. Next Steps: We are actively monitoring CAQH’s updates on the incident. Once CAQH restores full functionality, we will re-trigger any impacted processes as needed. We will provide an update once normal operations resume. Portal is not loading for users https://status.certifyos.com/incident/712284 Thu, 21 Aug 2025 19:30:00 -0000 https://status.certifyos.com/incident/712284#06ecb5daa38f3af880cac7d1b9c01b77269019fae8c9c62fbfac5a2160bb6f72 Bubble.io restored their load balancer functionality, and access to our services returned to normal. Portal is not loading for users https://status.certifyos.com/incident/712284 Thu, 21 Aug 2025 19:01:00 -0000 https://status.certifyos.com/incident/712284#0bc8af037ea3cfe488b4cc768b25c6df09e24a9ca4e147ac50717460c1c9c2a3 Our hosting provider, bubble.io, has confirmed they are encountering network issues with their load balancers. This results in our domain being unavailable. https://status.bubble.io/incidents/7kzqtsldmvs4 Portal is not loading for users https://status.certifyos.com/incident/712284 Thu, 21 Aug 2025 18:40:00 -0000 https://status.certifyos.com/incident/712284#3770ead8ae5cf51502d5762fdfec90bea255c1290c2b3c5da7df2cd6999ecb09 Portal is unavailable to users. It appears to be an issue with our hosting provider. Application home page is not loading for some users https://status.certifyos.com/incident/515144 Fri, 07 Feb 2025 06:25:00 -0000 https://status.certifyos.com/incident/515144#e2f60aae0d8a92abce4110d72575d774702a88e7b190de4673b5d50739318ca4 We have deployed a fix to handle session expiration gracefully. Application home page is not loading for some users https://status.certifyos.com/incident/515144 Thu, 06 Feb 2025 15:45:00 -0000 https://status.certifyos.com/incident/515144#8caaa861b96baedac527d930e5fbf9dc0df2ffe1600369e9c740dea7de57b1b6 There is a workaround to log out and back in manually to regain full functionality. Application home page is not loading for some users https://status.certifyos.com/incident/515144 Thu, 06 Feb 2025 13:44:00 -0000 https://status.certifyos.com/incident/515144#36235260aafe91419764c3c601b3d09d55799a0047af91c078383f983e54ce10 Some users are reporting a Certify landing page with no content. This is due to an issue with authentication session expiration.