Incidents reported on status page for Cerebrum https://status.cerebrum.com/ https://d1lppblt9t2x15.cloudfront.net/logos/eb7a5ea5e12a69d074b673d72b5bfb8f.png https://status.cerebrum.com/ en https://status.cerebrum.com/ Fri, 17 Jul 2026 16:38:32 +0000 https://status.cerebrum.com/#8e399c01664ca8d81da10b92110db3e45cf4794aea41962989e87e614649a6a6 Authentication API recovered https://status.cerebrum.com/ Fri, 17 Jul 2026 16:36:17 +0000 https://status.cerebrum.com/#9afd3da8183d573816f0ab9d41e8f9e98cbe3419667274799f3f3be5277d647e Cerebrum vID API recovered https://status.cerebrum.com/ Fri, 17 Jul 2026 16:34:17 +0000 https://status.cerebrum.com/#9afd3da8183d573816f0ab9d41e8f9e98cbe3419667274799f3f3be5277d647e Cerebrum vID API went down https://status.cerebrum.com/ Fri, 17 Jul 2026 16:33:23 +0000 https://status.cerebrum.com/#8e399c01664ca8d81da10b92110db3e45cf4794aea41962989e87e614649a6a6 Authentication API went down https://status.cerebrum.com/ Wed, 08 Jul 2026 18:11:12 +0000 https://status.cerebrum.com/#8c245a2a319887a4cb90e8fab6369704e21370997391d241352d3b6df443d6db Cerebrum vID API recovered https://status.cerebrum.com/ Wed, 08 Jul 2026 18:09:56 +0000 https://status.cerebrum.com/#8c245a2a319887a4cb90e8fab6369704e21370997391d241352d3b6df443d6db Cerebrum vID API went down https://status.cerebrum.com/ Wed, 08 Jul 2026 03:10:11 +0000 https://status.cerebrum.com/#1bade6a449cdc765c23e5b04b27f2b1938b452f63548be4173c2691e5f6ed80b Cerebrum vID API recovered https://status.cerebrum.com/ Wed, 08 Jul 2026 03:08:08 +0000 https://status.cerebrum.com/#1bade6a449cdc765c23e5b04b27f2b1938b452f63548be4173c2691e5f6ed80b Cerebrum vID API went down https://status.cerebrum.com/incident/941798 Thu, 02 Jul 2026 16:59:00 -0000 https://status.cerebrum.com/incident/941798#afb2712ec74dc4b69069b1a01187d2c1a38bb401d828b277f3d7446acca10cd5 We have deployed a fix to our production systems resolving the cause of the issue. https://status.cerebrum.com/ Thu, 02 Jul 2026 16:56:58 +0000 https://status.cerebrum.com/#51ce86cb2e383317c335fe164d9f4b3d1551047b00301b3746c80ba76c0c88e1 Document Verification API recovered https://status.cerebrum.com/ Thu, 02 Jul 2026 16:52:09 +0000 https://status.cerebrum.com/#79153a4821492a53df1c4a60001f8ccee5b536b3dfedf0752b50f57b0d3108a2 Cerebrum vID API recovered https://status.cerebrum.com/incident/941798 Thu, 02 Jul 2026 16:49:00 -0000 https://status.cerebrum.com/incident/941798#6b0195732421559c4b31b9fdd9673fddd446d8ef930f324052e9664980da8501 Our API services are currently under heavy load and failing to respond to requests. The engineering team is investigating. https://status.cerebrum.com/ Thu, 02 Jul 2026 16:48:27 +0000 https://status.cerebrum.com/#77405ad7ccfd941b68ed8ed79e5cfd73642b9c940233e302f70b32252be05ea9 Authentication API recovered https://status.cerebrum.com/ Thu, 02 Jul 2026 16:46:57 +0000 https://status.cerebrum.com/#51ce86cb2e383317c335fe164d9f4b3d1551047b00301b3746c80ba76c0c88e1 Document Verification API went down https://status.cerebrum.com/ Thu, 02 Jul 2026 16:43:27 +0000 https://status.cerebrum.com/#77405ad7ccfd941b68ed8ed79e5cfd73642b9c940233e302f70b32252be05ea9 Authentication API went down https://status.cerebrum.com/ Thu, 02 Jul 2026 16:42:46 +0000 https://status.cerebrum.com/#79153a4821492a53df1c4a60001f8ccee5b536b3dfedf0752b50f57b0d3108a2 Cerebrum vID API went down https://status.cerebrum.com/ Thu, 02 Jul 2026 15:16:58 +0000 https://status.cerebrum.com/#a19c9aacd624766234c1e0abc37e3ed0742966e8e213d130b546a04675c9a3ac Document Verification API recovered https://status.cerebrum.com/ Thu, 02 Jul 2026 15:13:28 +0000 https://status.cerebrum.com/#cd55e0e31f39a7074a6dbd12d4d97642880c1312e6e80b3f15a758b9f44add02 Authentication API recovered https://status.cerebrum.com/ Thu, 02 Jul 2026 15:12:48 +0000 https://status.cerebrum.com/#5f2c01b08794339fc5905983122026d52882beb150e35f33492451ed38895de0 Cerebrum vID API recovered https://status.cerebrum.com/ Thu, 02 Jul 2026 15:12:00 +0000 https://status.cerebrum.com/#a19c9aacd624766234c1e0abc37e3ed0742966e8e213d130b546a04675c9a3ac Document Verification API went down https://status.cerebrum.com/ Thu, 02 Jul 2026 15:08:27 +0000 https://status.cerebrum.com/#cd55e0e31f39a7074a6dbd12d4d97642880c1312e6e80b3f15a758b9f44add02 Authentication API went down https://status.cerebrum.com/ Thu, 02 Jul 2026 15:07:19 +0000 https://status.cerebrum.com/#5f2c01b08794339fc5905983122026d52882beb150e35f33492451ed38895de0 Cerebrum vID API went down https://status.cerebrum.com/incident/940683 Wed, 01 Jul 2026 15:49:00 -0000 https://status.cerebrum.com/incident/940683#876d1a6ab9b8ece4acebda3c0f239ef59ef62d5125e97424b6d251edd9d39ae2 Our team has implemented a fix and is monitoring the situation. Platform access is restored. We will provide more details once a permanent solution is applied. https://status.cerebrum.com/ Wed, 01 Jul 2026 15:48:29 +0000 https://status.cerebrum.com/#c9cc31f3da4298059e520fabc6671e158ea5da92c7a8b2a0fd06894caa4d8975 Authentication API recovered https://status.cerebrum.com/ Wed, 01 Jul 2026 15:47:50 +0000 https://status.cerebrum.com/#9fea24312d0bd1a559713e8035ad51607bb1fe0630e811278da352fca980311f Cerebrum vID API recovered https://status.cerebrum.com/ Wed, 01 Jul 2026 15:46:55 +0000 https://status.cerebrum.com/#31a94399323864d13df1ac2532355e5af9a3c09170257d2079189db8d373b751 Document Verification API recovered https://status.cerebrum.com/incident/940683 Wed, 01 Jul 2026 15:42:00 -0000 https://status.cerebrum.com/incident/940683#de824b76e2e489dce6a2d13e0be2f0de4a38b95362387a2983954e9e8ee4f37c Our API is currently experiencing elevated error rates. Our team has identified the instability and is actively investigating the issue to restore normal service as quickly as possible. We will provide further updates shortly. https://status.cerebrum.com/ Wed, 01 Jul 2026 15:33:27 +0000 https://status.cerebrum.com/#c9cc31f3da4298059e520fabc6671e158ea5da92c7a8b2a0fd06894caa4d8975 Authentication API went down https://status.cerebrum.com/ Wed, 01 Jul 2026 15:31:56 +0000 https://status.cerebrum.com/#31a94399323864d13df1ac2532355e5af9a3c09170257d2079189db8d373b751 Document Verification API went down https://status.cerebrum.com/ Wed, 01 Jul 2026 15:31:10 +0000 https://status.cerebrum.com/#9fea24312d0bd1a559713e8035ad51607bb1fe0630e811278da352fca980311f Cerebrum vID API went down https://status.cerebrum.com/incident/913711 Fri, 05 Jun 2026 00:43:00 -0000 https://status.cerebrum.com/incident/913711#a8524ae69c2661937d6633245bbe5ffd413afe8645a99b14b668dc5e0b07c99c The incident has been resolved. https://status.cerebrum.com/incident/913711 Thu, 04 Jun 2026 23:56:00 -0000 https://status.cerebrum.com/incident/913711#f52221c3b8cd57da56769b78168f123731b5f1ea49c53e70785a8dfc1448ba0c The underlying issue with our third-party email provider has been resolved. We are currently monitoring our delivery queues as the backlog of delayed emails clears out. You should see pending emails arriving shortly. We will provide a final update once delivery times return to baseline. https://status.cerebrum.com/incident/913711 Thu, 04 Jun 2026 22:59:00 -0000 https://status.cerebrum.com/incident/913711#6b91edb6abf787f53481aecef8e813d57d55de62a7d3fa03866e22521e5efd6a We have identified an issue with a third-party vendor responsible for our email delivery services, which is causing a backlog and subsequent delays in sending transactional messages. The provider is currently implementing a fix. All outgoing emails are safely queued and will be processed chronologically as performance recovers. No action is required on your part. https://status.cerebrum.com/incident/901187 Wed, 20 May 2026 22:48:00 -0000 https://status.cerebrum.com/incident/901187#0ded32b0f4367d487ba78eeb348dc5cfe577c29881504e53ed664bb64ebdc352 The issue is resolved. https://status.cerebrum.com/incident/901187 Wed, 20 May 2026 22:05:00 -0000 https://status.cerebrum.com/incident/901187#25d97f09e7c8dcb9987aa822bf00836db11ada306d94eda1915571abfc567a34 Following a recent deployment, our system detected a spike in error rates for automated orders processing through Synapse. Our team immediately isolated the issue and reverted the changes. Services have fully recovered, and we are conducting a review to prevent future occurrences. https://status.cerebrum.com/incident/885499 Fri, 01 May 2026 22:45:00 -0000 https://status.cerebrum.com/incident/885499#42310277f6e24924349da6862ffbbd40e43884d93d64c7407056161e4a1f3389 The incident has been resolved. https://status.cerebrum.com/incident/885499 Fri, 01 May 2026 21:45:00 -0000 https://status.cerebrum.com/incident/885499#badd81b39a9e9d75bf10a4618726c747b96047cbe18121bcc640ed75bd1093d1 We experienced a transient issue affecting email delivery for a subset of customers. The incident started at approximately 4:45 PM CDT and lasted about an hour. Email delivery has been fully restored, and services are operating normally. https://status.cerebrum.com/incident/848921 Sat, 14 Mar 2026 03:00:00 -0000 https://status.cerebrum.com/incident/848921#9355c0f9b66a4aca3643040e7a9ddcbc960da778c1ebd74500d5d23ff0a19e04 We are performing server updates to our core APIs and infrastructure. Our applications may be intermittently unavailable for this period. https://status.cerebrum.com/incident/835840 Sat, 28 Feb 2026 04:00:00 -0000 https://status.cerebrum.com/incident/835840#90fac0332fb71a3e5baefc273fab5772fcc0e8a604334d4750170fc7d2e72837 We're performing a maintenance on our scheduling system. We expect its performance to improve significantly after the process is finished. Some actions like sending invites may take a little longer than expected during that period. We apologize for the inconvenience. https://status.cerebrum.com/incident/808752 Wed, 21 Jan 2026 11:06:00 -0000 https://status.cerebrum.com/incident/808752#035261de13987cca25fa8bfcf07d56a38b6fd671967e60c03db0369383951b8a The system has recovered and is operating correctly. https://status.cerebrum.com/incident/808752 Wed, 21 Jan 2026 08:42:00 -0000 https://status.cerebrum.com/incident/808752#eb21c3316210e9db7bc4f3778d0a2ba2da2de2b8dd440efe2df477997b659576 We have deployed a fix for the root cause of the issue and services are recovering. https://status.cerebrum.com/incident/808752 Wed, 21 Jan 2026 08:01:00 -0000 https://status.cerebrum.com/incident/808752#eda3e313f681c31e1a744ee097b72d8a0566c22e61ba57dd1fdca952a602a787 We’re having some trouble with our outbound integration with TazWorks. We’re working to fix the problem as quickly as we can. We’ll share another update shortly. https://status.cerebrum.com/incident/793141 Tue, 23 Dec 2025 11:00:00 -0000 https://status.cerebrum.com/incident/793141#c4904b364daf48d696ba9213fe9cd94088f440aa32f0c86b5c2f1c9bed6f4385 System status is now stable. We're sorry for the inconvenience. https://status.cerebrum.com/incident/793141 Tue, 23 Dec 2025 10:40:00 -0000 https://status.cerebrum.com/incident/793141#a250f7fc10d0d294a29655cd7580e9ea6df994efc4891a851d8738913a4e0e0e During a scheduled maintenance window intended to optimize our database infrastructure's security and performance, Cerebrum experienced a brief period of service degradation between 05:37 AM EST and 06:00 AM EST. This affected the vID, Authentication and Document Verification APIs. Full system health was restored promptly, and no data was compromised. What happened? A subset of users attempting to authenticate or verify documents during this window may have experienced intermittent server errors or request timeouts. 05:37 AM EST: Infrastructure optimization began, resulting in intermittent connectivity. 05:39 AM EST: Connectivity was partially restored (service degraded). 06:00 AM EST: All services returned to full operational capacity. Why did this happen? The degradation resulted from a complex interaction between network topology changes and our automated recovery systems: Topology Propagation: During the migration of database nodes to optimized subnets, network propagation delays prevented the application layer from immediately synchronizing with the new primary database node. Provisioning Latency: When our automated systems attempted to refresh the application instances to resolve the synchronization issue, a dependency in the deployment pipeline caused a delay in provisioning the necessary application artifacts. This extended the recovery window by approximately 20 minutes. What were the solutions applied? Engineering teams intervened manually to bypass the provisioning latency and expedite the service refresh. We have updated our deployment pipeline configurations to ensure high-availability access to application artifacts during future maintenance windows. All systems were verified stable by 6:00 AM EST. https://status.cerebrum.com/incident/792378 Mon, 22 Dec 2025 10:00:00 -0000 https://status.cerebrum.com/incident/792378#1516f64be5bd8266dc1fa3105475d45b6d25ddc5df27abea913792ef1354c158 Our team is applying an important set of improvements to our IT infrastructure. The approximate duration of the maintenance should be 50 minutes. During this time, we do not expect any downtime, and we are ready to act to ensure the availability of our services if needed. Thank you for your understanding. We'll update this warning as the operation proceeds. https://status.cerebrum.com/incident/763033 Wed, 12 Nov 2025 18:28:00 -0000 https://status.cerebrum.com/incident/763033#aed5ee0d7ac998cf96673a0c14b686275e9d93d0e373f96b5748531453dadfc6 Our team is still investigating both the root cause and a definitive fix. Our hotfix worked and our API is operational. We'll come back with more details soon. https://status.cerebrum.com/incident/763033 Wed, 12 Nov 2025 17:09:00 -0000 https://status.cerebrum.com/incident/763033#b3cf54b8d8b29db766df56e55985b30eb8ca5e987b525241b5ddbe2378ae725e A hotfix has been applied, and systems should be running correctly now. Our team is still investigating the issue's root cause and a definitive fix. We'll add more details to this page as the investigation continues. https://status.cerebrum.com/incident/763033 Wed, 12 Nov 2025 16:10:00 -0000 https://status.cerebrum.com/incident/763033#bc0241d09a4051037befca8092bd850be5ab8713badc4d4a476f070b66ed73f4 Our monitoring has detected an elevated rate of errors impacting our API endpoints. We are investigating the issue and are in the process of validating a potential root cause. We will provide another update as this investigation progresses. https://status.cerebrum.com/incident/747191 Mon, 20 Oct 2025 23:00:00 -0000 https://status.cerebrum.com/incident/747191#41a85e04a30c3f1ae13612cde1b5942edb3e4ec88057ed3bf595f5d74e31723d The AWS infrastructure seems to be stable now. Our team continues monitoring the situation. More information is available at the AWS Service Health Dashboard (https://health.aws.amazon.com/health/status). https://status.cerebrum.com/incident/747191 Mon, 20 Oct 2025 16:40:00 -0000 https://status.cerebrum.com/incident/747191#19b78a40730fee84e121488202e0c9a232e99de17634ee6c9bd27b7661ef9470 We are still experiencing intermittent service disruptions and performance degradation across some of our platforms. This is a result of a major, ongoing outage from our cloud provider, Amazon Web Services (AWS), which is affecting services globally. Our core systems are operational, but some users may experience unexpected behavior or latency. Our engineering team is actively monitoring the situation and working to mitigate the impact on our customers. For more details on the root cause, please refer to the official AWS Service Health Dashboard (https://health.aws.amazon.com/health/status). We will post further updates as more information becomes available. We appreciate your patience. https://status.cerebrum.com/incident/747191 Mon, 20 Oct 2025 07:50:00 -0000 https://status.cerebrum.com/incident/747191#4a31895fa27cd8d6ef91c86fcf213a1674929725e5cc93bfa00f4e5756a77538 A widespread service provider outage is also affecting Cerebrum Services, preventing functionality from behaving as expected in a number of areas. We're working to recover services now and will update this instance as recovery completes. https://status.cerebrum.com/incident/714245 Thu, 28 Aug 2025 05:50:00 -0000 https://status.cerebrum.com/incident/714245#4fb11fa62ec24e1a40265f6126572cdd43961379fdd1193b87cdff3bf0053130 Our Document Verification API experienced severe performance degradation causing some ID scan uploads to take 5-10 minutes instead of the expected near-instant processing. Multiple users reported these delays, with an estimated 37.5% of all verification operations potentially affected during the incident window. ### User Impact - 3-4 confirmed users reported 5-10 minute delays for ID uploads - 10-15 total users attempted to use the service during the incident - Successfully completed verifications showed success badges but no data was accessible - Records were not appearing in the admin dashboard for review ### Root Cause A critical service component entered a failure state, consuming excessive CPU resources while repeatedly failing to process requests. This component handled approximately 50% of all verification traffic, causing widespread impact when it became unresponsive. #### Contributing Factors - The affected service component entered an unrecoverable state requiring manual intervention - No automatic recovery mechanism was in place for high CPU usage scenarios ### Timeline - 2025-08-26: Normal operations, no errors reported - 2025-08-27: Error spike began, "No scan response" errors began to appear - 2025-08-28: Issue identified and resolved through manual intervention ### Resolution **Immediate Actions Taken:** - Manual restart of the failed service component - Traffic redistribution to reduce dependency on any single server from 50% to 25% **Planned Improvements:** - Enhanced monitoring and alerting for application-level health - Implementation of automatic recovery mechanisms for performance degradation - Improved health checks that can detect and isolate failing components https://status.cerebrum.com/incident/714245 Wed, 27 Aug 2025 19:56:00 -0000 https://status.cerebrum.com/incident/714245#2d5d2ac621b752043477e90d01ec3f87adf932b6acbe1f7123bd0d2a3ae850f4 We have received reports of elevated "No scan response" errors. We are investigating https://status.cerebrum.com/incident/575889 Thu, 22 May 2025 18:17:00 -0000 https://status.cerebrum.com/incident/575889#28416eb645041ab14af0188c614078b06159eacf7afcad3af0dde54126be28dd The issue has been resolved. https://status.cerebrum.com/incident/575889 Thu, 22 May 2025 18:17:00 -0000 https://status.cerebrum.com/incident/575889#e014390fd6912b1909cab53b7499aa47aa0104929a95011f87b7e31af9833593 On May 22nd, 2025, Cerebrum's Document Verify API had a 9-minute outage from 4:28 PM UTC to 4:37 PM UTC, caused by a deployment that upgraded a fundamental piece of software in our instances. Users who tried scanning their ID using vID / vID Web during that time window got an Internal Server Error response. The incident was identified and fixed, with a follow-up definitive fix to be implemented. We apologize for the inconvenience and are taking measures to ensure similar issues don't happen again. https://status.cerebrum.com/incident/521324 Sun, 02 Mar 2025 05:01:36 -0000 https://status.cerebrum.com/incident/521324#5a8c4d23896835dad8b3a8fd662e7839148300d877b2ebc577fc491265e5f966 Our team will perform a scheduled maintenance on Mar 2nd, 2025 from 12:00 AM to 12:30 AM EST (GMT -5). During that window, our systems may be temporarily unavailable. This maintenance is necessary to apply database improvements and ensure system stability and performance. We apologize for any inconvenience this may cause and appreciate your understanding. If you have any questions or concerns, please contact us via email to support@cerebrum.com. Thank you for your patience. https://status.cerebrum.com/incident/465475 Sat, 23 Nov 2024 05:00:37 -0000 https://status.cerebrum.com/incident/465475#a6e24a52d248434a456de2d0caa9b8d457e920e72988176f19748291f219e848 Our team will perform a scheduled maintenance on Nov 23rd, 2024 from 12:00 AM to 12:30 AM EST (GMT -5). During that window, our systems may be temporarily unavailable. This maintenance is necessary to apply platform improvements and ensure system stability. We apologize for any inconvenience this may cause and appreciate your understanding. If you have any questions or concerns, please contact us via email to support@cerebrum.com. Thank you for your patience. At 12:01 AM EST, the maintenance window started. At 12:10 AM EST, the platform improvements were applied successfully and the team was testing the platform. At 12:19 AM EST - The team finalizes the tests with no errors; At 12:21 AM EST - The maintenance window were completed. https://status.cerebrum.com/incident/450177 Thu, 24 Oct 2024 21:24:00 -0000 https://status.cerebrum.com/incident/450177#116792f26da570b86b8bbd23343ed6ef55e74cfd22cf5a181c8a2f1e922b6c99 We have identified the root cause and applied a quick fix, with a permanent solution to be implemented in the next 24 hours. Users should be able to go through with their orders now. We'll be monitoring the situation until it's resolved. https://status.cerebrum.com/incident/450177 Thu, 24 Oct 2024 20:44:00 -0000 https://status.cerebrum.com/incident/450177#ae2c75cfaf5b6a7ebec65b229e1eff6e11a33ff180be71abf26b68ede8893cb4 We are aware of the issues a subset of our users is facing when accepting invites and / or completing orders. Our team is working on the problem, and currently investigating a possible cause. We'll update this thread as we go through the problem. https://status.cerebrum.com/incident/400942 Sat, 20 Jul 2024 04:00:00 -0000 https://status.cerebrum.com/incident/400942#ed0d38aecfa652742b3d0a4d3f36c6520ccec39156e5eb14daf54f77fac16564 We're upgrading our production servers' operational systems and softwares in a rolling-update manner. We don't expect any downtimes in this maintenance, but they may occur. Our infrastructure team is actively monitoring the traffic and are ready to respond to any issues. https://status.cerebrum.com/incident/400838 Fri, 19 Jul 2024 23:34:00 -0000 https://status.cerebrum.com/incident/400838#f66acf0d8961a2146c139b1b00426431f8b0e74c3bfacbd25cc640f7c56d3971 We have records that indicate another instance in the load balancer was also affected. For that reason, that instance removed from the targets and that seems to have resolved the issue completely. We will ensure that instance is completely operational before bringing it back up. Sorry for the inconvenience. https://status.cerebrum.com/incident/400838 Fri, 19 Jul 2024 22:18:00 -0000 https://status.cerebrum.com/incident/400838#9519387fc3591b72c2555f4c8e8b61b3372eef6157523fb32a36d15e94ee10f4 We have removed the faulty instance from the load balancer until it's totally restored. New ID verification requests should go through without any issues. We're actively monitoring the issue. https://status.cerebrum.com/incident/400838 Fri, 19 Jul 2024 20:15:00 -0000 https://status.cerebrum.com/incident/400838#78b144c53a19b9383bba82e39a7bbb536f3ada660e7f02a4de41115da14597eb One of the instances handling ID verification in our systems stopped working for part of July 19th. This was due to the issue with Crowdstrike (https://www.crowdstrike.com/blog/statement-on-falcon-content-update-for-windows-hosts/) that impacted many companies around the globe. Because of that, part of the ID verification requests made to our servers failed. We're working to restore 100% coverage on that. https://status.cerebrum.com/incident/348089 Sat, 30 Mar 2024 02:20:00 -0000 https://status.cerebrum.com/incident/348089#373e16ec0798cdec96b0c90b004eb55a8b6bcda3e8f5140fb96c7d86b7519c3d We're performing a maintenance on our production services. There may be short periods of downtime (not more than 5 minutes) during the maintenance. https://status.cerebrum.com/incident/288839 Sat, 18 Nov 2023 03:26:23 -0000 https://status.cerebrum.com/incident/288839#2f16a16a0542703f6ffadda3c403bb9cdec604bf64ba1970f053eed5b0de1426 Maintenance completed https://status.cerebrum.com/incident/288839 Sat, 18 Nov 2023 02:40:00 -0000 https://status.cerebrum.com/incident/288839#07dee5b52c8de5213dee22df12980b69bc3f745632e2dfe06d0bf80007c775ba We are performing server updates to our core APIs, and web-services may be intermittently available for this period.