Incidents reported on status page for Crossing Minds https://status.crossingminds.com/ https://d1lppblt9t2x15.cloudfront.net/logos/b9547e2f4e77d6b0a7b4abbf9531360a.png https://status.crossingminds.com/ en https://status.crossingminds.com/incident/495212 Mon, 13 Jan 2025 07:23:00 -0000 https://status.crossingminds.com/incident/495212#48e30dbb0a915276f5028298520cb19e9940e6b47d34aae8e8ccad660602c0a0 Our API experienced a brief interruption lasting 11 minutes. The issue occurred due to a database server restart during planned maintenance. We apologies if you were affected by this incident. https://status.crossingminds.com/incident/475470 Mon, 09 Dec 2024 18:32:00 -0000 https://status.crossingminds.com/incident/475470#5463647b40cfed1ee208f046ea7c8bdf7fed2bedd2cdff5397814fd4af6ed61a Our API recovered from a short incident earlier today. The root cause was an [outage of GCP BigQuery](https://status.cloud.google.com/incidents/LztMRFrCwWofMbzRENLW), which started at 9:29a PT and ended at 11:50a PT. The impact on our API was elevated error rate during three spikes (US API): - 30% error rate from 9:29a to 9:31a PT - 48% error rate from 9:43a to 9:55a PT - 52% error rate from 10:17a to 10:20a PT We apologies if you were affected by this incident. https://status.crossingminds.com/incident/354266 Sat, 13 Apr 2024 13:15:00 -0000 https://status.crossingminds.com/incident/354266#5e528deb9167a83a41e70ac8f157939962ea74010e493ee615a65a282b7395b9 Maintenance completed https://status.crossingminds.com/incident/354266 Sat, 13 Apr 2024 13:00:00 -0000 https://status.crossingminds.com/incident/354266#e9f0284791ab3dfb0b0f8c4f78f1b58fc52ecafed2c34779b27e3b3ea2b89c93 We will conduct scheduled maintenance on our Databases. During this maintenance window, you may experience intermittent 500 errors when accessing our API. We apologize for any inconvenience this may cause and appreciate your understanding and patience as we continue to improve our services. Should you have any concerns or require assistance, please reach out to our support team. https://status.crossingminds.com/incident/352475 Mon, 08 Apr 2024 09:35:00 -0000 https://status.crossingminds.com/incident/352475#329853d400da954fd6bd9f4843ce51ea80670e275dffb5ab9179227c8d0e7e89 A planned maintenance started at 09:15 UTC on Apr 8, 2024, and finished at 09:34 UTC. During the maintenance, writing data returned 503 status. Reading data, including real-time recommendations, was not affected. https://status.crossingminds.com/incident/343198 Mon, 18 Mar 2024 18:45:00 -0000 https://status.crossingminds.com/incident/343198#feef532a71443d652f32b3ef8fc44499b7fd3761c52e565b1028f35caa5ebc6b At 18:40 UTC on Mar 18, 2024, our API went down in the us-central1 and us-east1 regions, stemming from resource issues. Systems were restarted and all systems returned to normal beginning at 18:43 UTC. Customers using other regions were not affected. https://status.crossingminds.com/incident/343197 Mon, 18 Mar 2024 17:45:00 -0000 https://status.crossingminds.com/incident/343197#179f48b3eb812c48ab4f0b590223225574ddda59756b3adc81baab97d3725c7f At 15:36 UTC on Mar 18, 2024, our API went down in the us-central1 and us-east1 regions, stemming from resource issues. Systems were restarted and all systems returned to normal beginning at 15:42 UTC. Customers using other regions were not affected. https://status.crossingminds.com/incident/343196 Sun, 10 Mar 2024 02:10:00 -0000 https://status.crossingminds.com/incident/343196#7688042066e2d911e9762eeb8c99d5fed75ff346213c1b98649c21491e72fd3c At 12:56 UTC on Mar 9, 2024, our services were unavailable in the us-central1 and us-east1 regions, due to scheduled maintenance. Systems returned to normal operation beginning at 13:08 UTC. Customers using other regions were not affected. https://status.crossingminds.com/incident/324145 Wed, 07 Feb 2024 17:00:00 -0000 https://status.crossingminds.com/incident/324145#03dce0cfd11256f17f41b515716e0b29097f25decfed095280e87a461e38026a At 08:52 UTC on Feb 7, 2024, our API went down in the us-central1 region, stemming from an error in a configuration during deployment. A fix was deployed at 09:17 UTC, and all systems returned to normal beginning at 09:23 UTC. Customers using other regions were not affected.