Incidents reported on status page for Co-PR https://status.co-pr.com/ https://d1lppblt9t2x15.cloudfront.net/logos/863c6fdae2ae4b028202e7f61e30be0d.png https://status.co-pr.com/ en https://status.co-pr.com/incident/614108 Fri, 04 Jul 2025 09:13:45 -0000 https://status.co-pr.com/incident/614108#cb5c6bfedb966e708d564e240d91f1f6e7ad05f135de91456d182510e08c6795 api.dev.co-pr.com went down. https://status.co-pr.com/incident/614108 Fri, 04 Jul 2025 08:58:43 -0000 https://status.co-pr.com/incident/614108#5635d52d1a1d016e97f10b02d9c084525349a7b295842fe6169c258d3d2e6d06 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/614108 Fri, 04 Jul 2025 08:49:33 -0000 https://status.co-pr.com/incident/614108#c3022f177b46ba17e1c0723e576a82225df6cada22ca7b6b203e5eb5fbe99965 api.dev.co-pr.com went down. https://status.co-pr.com/incident/614108 Fri, 04 Jul 2025 08:49:00 -0000 https://status.co-pr.com/incident/614108#204f32dd20f7480d2b1c128d7f12c29ca31201b285b452a5e846a7bf900eb5b0 portal.develop.co-pr.com/v1 went down. https://status.co-pr.com/incident/613308 Thu, 03 Jul 2025 00:18:40 -0000 https://status.co-pr.com/incident/613308#11042a4d0be89775d630b21fa115889c9efe55569e9070ddc91ce64024be32dc portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/613308 Thu, 03 Jul 2025 00:16:09 -0000 https://status.co-pr.com/incident/613308#26a9e8fec6df09e910f6f4ffc14b02325a55752db77c4794b0e9ea21956d7c88 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/613308 Thu, 03 Jul 2025 00:03:49 -0000 https://status.co-pr.com/incident/613308#d570ce5a03bc21db98c81855cda4a9c5a5381cb0751f8d203661daa3010785cc api.dev.co-pr.com and portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/613308 Thu, 03 Jul 2025 00:03:49 -0000 https://status.co-pr.com/incident/613308#d570ce5a03bc21db98c81855cda4a9c5a5381cb0751f8d203661daa3010785cc api.dev.co-pr.com and portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 08:18:15 -0000 https://status.co-pr.com/incident/612820#476457d21ca8ac3668e2b3143ea529157e2e197cb9ed6397859b12974d98bee1 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 08:17:43 -0000 https://status.co-pr.com/incident/612820#bc00698f80682dda65a9a45e1adfd0db190785c50b41bba28e45fe4b6d89e2a1 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 08:03:23 -0000 https://status.co-pr.com/incident/612820#957cfe352381046f7bca30f11b65ce7371218481761d99be242cc87d6f77394b api.dev.co-pr.com went down. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 08:03:05 -0000 https://status.co-pr.com/incident/612820#f9e85679b2ee81b346651cfcc0b40d2780d26f411543224a13483bd36f810aaf portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 07:56:52 -0000 https://status.co-pr.com/incident/612820#a36ef8239c895bdf0de8e3b348dd495bcb5c80c5486335af929acc63caaa3caf portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 07:54:22 -0000 https://status.co-pr.com/incident/612820#919b6d96213ae3b6e9bdc7daf5a69c0a144f19aa532a65c173fec767202e5b04 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 07:35:10 -0000 https://status.co-pr.com/incident/612820#7f7c131e5ef7fd2714700f3078adbd7bcf406d8e3a1c12cab4b64706878a721b api.dev.co-pr.com went down. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 07:34:34 -0000 https://status.co-pr.com/incident/612820#e28fbf6967403e80cf4d9f5f49042d67d8fcf80c8a4e432c71722d3a520ec527 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 04:38:37 -0000 https://status.co-pr.com/incident/612820#d8586a95dcef86b81ae2a6984f275578d8838c35a378d16f4739685ee859b895 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 04:36:10 -0000 https://status.co-pr.com/incident/612820#858465ed30a6d1ea3dbe2c5d0f4dffef2741fa6f4bbb84a94c08b32824bba326 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 04:27:10 -0000 https://status.co-pr.com/incident/612820#4d9e3c1590b67013b1f6322460a4d62b8d0ea9a7406f9fa2424b0709b369f2ab api.dev.co-pr.com went down. https://status.co-pr.com/incident/612820 Wed, 02 Jul 2025 04:26:43 -0000 https://status.co-pr.com/incident/612820#6e651230aed77991bdc439e211600c89f5f62272d7cd41107b5bfde54636a888 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 06:16:40 -0000 https://status.co-pr.com/incident/612079#3f3f7de123c5b6ad37b0d55d95c9359f12d0a60663ad2386637453e2dcc9074a api.dev.co-pr.com recovered. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 06:16:09 -0000 https://status.co-pr.com/incident/612079#89511ef5ee24b7555ede706f5a1f1e4eecacfc8903d153b98459cd3bf500dfe4 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 05:58:08 -0000 https://status.co-pr.com/incident/612079#a49a78a09c488c012f48ea40bde2d70f4c434ce507aff7f936fdc3844ddd385f api.dev.co-pr.com went down. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 05:57:37 -0000 https://status.co-pr.com/incident/612079#1d01b0c728ec51a3e9632bb85a1beaaa450d36b4620b7cb1699177700785940b portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 05:37:00 -0000 https://status.co-pr.com/incident/612079#327a861cc3830daac56580322fb7135c2df44c000133f5f62ef3c52bac82e2ce api.dev.co-pr.com recovered. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 05:36:41 -0000 https://status.co-pr.com/incident/612079#61ccf0c51345555821d79c63f852a4596a288b1a102446dff9fde600c5b9455e portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 05:27:36 -0000 https://status.co-pr.com/incident/612079#0f3266d56aad079382e30a251aa397dac5f4fe8e51741980bdf219d7f8f68bf3 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 05:25:03 -0000 https://status.co-pr.com/incident/612079#98397bc0ab6ceeb7f40d7c196642e49f91e86d782e2dc5948cc4f44cdde6930c api.dev.co-pr.com went down. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 01:16:01 -0000 https://status.co-pr.com/incident/612079#6674b33be684c5c28d1bd19736a5db469adbd19faf261d1f0e60b9c7bba1b9b4 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/612079 Tue, 01 Jul 2025 01:12:43 -0000 https://status.co-pr.com/incident/612079#a68a6067953d034e8670bd701a6c076281192b33b7f6db88cae6b0450deea881 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/611391 Mon, 30 Jun 2025 00:56:26 -0000 https://status.co-pr.com/incident/611391#ab88b12e0a49b7df4d3c5d99b16fd512684ac715ab867589f528707dba84df47 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/611391 Mon, 30 Jun 2025 00:53:25 -0000 https://status.co-pr.com/incident/611391#4fa77d8deb896a967fff9aef2805732ac096369b4352701299639c7c61b35333 api.dev.co-pr.com went down. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 08:05:50 -0000 https://status.co-pr.com/incident/608618#959355685871891fa773e29fe8cb6a84c1c1f22384fccb462de6cf6001f13069 api.dev.co-pr.com and portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 08:05:50 -0000 https://status.co-pr.com/incident/608618#959355685871891fa773e29fe8cb6a84c1c1f22384fccb462de6cf6001f13069 api.dev.co-pr.com and portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 08:00:04 -0000 https://status.co-pr.com/incident/608618#d0affb54265d9a551982226d421e2646406130dbbd1d1b0db2fbbfff6df11be5 api.dev.co-pr.com went down. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 07:59:32 -0000 https://status.co-pr.com/incident/608618#3d978db8347877d7a9f965ebdd0d591282e77200633c9a32ac130a3d327d0c43 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 06:27:08 -0000 https://status.co-pr.com/incident/608618#63b6c4559b7b1a8eeca6c1919b110982d298fa5c0c3d2eba6a4d7cc4bed1bde6 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 06:26:45 -0000 https://status.co-pr.com/incident/608618#946dbdc5c5462792254f28a919a90cd8346df4e46b8e486653415001ecc50100 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 06:21:03 -0000 https://status.co-pr.com/incident/608618#95255b9ffc004a9700874577d7a04597f96e35114fab1fa9038e66d655e3b05f api.dev.co-pr.com went down. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 06:20:28 -0000 https://status.co-pr.com/incident/608618#06958411038101a0f5c43379f5bc4b511cdfecc3d664b2b6c26c44986dd85710 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 05:59:37 -0000 https://status.co-pr.com/incident/608618#051a6349da419761eecc6a15e2acc62640cc4060afd2ecf17c635744b5436ce8 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 02:39:11 -0000 https://status.co-pr.com/incident/608618#6d1e91b433a6d479c35b711e5bccf7ed1edbdd14fda042291efe9665c4618dea api.dev.co-pr.com recovered. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 02:32:56 -0000 https://status.co-pr.com/incident/608618#459e4565bc2b225b0d3cd56334f5158bb37916d7ebd33ab620bc43aa2cafd378 api.dev.co-pr.com went down. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 02:32:27 -0000 https://status.co-pr.com/incident/608618#ab8170a646addfe95bc458f63d81e0324f62c4966617c9daf5ffb7decce8b65a portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 01:35:45 -0000 https://status.co-pr.com/incident/608618#8ab9ab2c0263d492217f0ea26b0a414f1017bc2cabfffebca3ce03237680fd8d portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 01:32:23 -0000 https://status.co-pr.com/incident/608618#d0296980f5afbfc6298b3b1f09285c85394aebc068267daecd16f643cd31c941 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 01:20:23 -0000 https://status.co-pr.com/incident/608618#8d21b6fd1c34a6457ed2d64a634a15d22dae576e8cc126ec3b082c4ee28f6db5 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/608618 Wed, 25 Jun 2025 01:17:21 -0000 https://status.co-pr.com/incident/608618#d4875312e87c1e17579373d3d5abf1aaa3860a5f5fb6a1eeec38d409eb273484 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/604943 Wed, 18 Jun 2025 05:55:42 -0000 https://status.co-pr.com/incident/604943#af3f8f6c517748c99a05c269937e4034a5fa9687b11ffc780e7c4fea84e93ad4 api.dev.co-pr.com and portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/604943 Wed, 18 Jun 2025 05:55:42 -0000 https://status.co-pr.com/incident/604943#af3f8f6c517748c99a05c269937e4034a5fa9687b11ffc780e7c4fea84e93ad4 api.dev.co-pr.com and portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/604943 Wed, 18 Jun 2025 05:19:51 -0000 https://status.co-pr.com/incident/604943#fe74393b5502ed67b1fb853ec0674c3835dfce4ccd42f4a66bfe5d93c5293603 api.dev.co-pr.com went down. https://status.co-pr.com/incident/604943 Wed, 18 Jun 2025 05:19:20 -0000 https://status.co-pr.com/incident/604943#07bb6e6d1585f9cf253d0f636816d47350fc1ac59107198a1cda4b2e179d3a69 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/603744 Tue, 17 Jun 2025 08:00:49 -0000 https://status.co-pr.com/incident/603744#337c8651b2a196cfb81fad287316646da2aa8455557199930d6ea0aae73f52d6 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/603744 Tue, 17 Jun 2025 07:57:41 -0000 https://status.co-pr.com/incident/603744#590bbdcffbb0d3163c53fdf2b8384d1a545bbac39ec32a3147e2f49357bb82bf portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/603744 Tue, 17 Jun 2025 01:42:37 -0000 https://status.co-pr.com/incident/603744#e628906a282eb9e611618697808929093b96ca77955829ef04796c3249358d96 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/603744 Tue, 17 Jun 2025 01:39:36 -0000 https://status.co-pr.com/incident/603744#292a48263d0ba49890ba049a9f02c908d914b5655818218f321afa02127c247a portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/603744 Tue, 17 Jun 2025 00:01:05 -0000 https://status.co-pr.com/incident/603744#054e67537e74d2f14a34baeb19331b216b3f8468bc643effe90b8b8d35bc7716 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/603744 Tue, 17 Jun 2025 00:00:44 -0000 https://status.co-pr.com/incident/603744#b005100361422bee58dda71f61e2c7c6a6b8d467655fc70b75eb7a4b11b19272 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/603744 Mon, 16 Jun 2025 23:54:34 -0000 https://status.co-pr.com/incident/603744#4a774355ecd8bf1ad9f2f3d36ee7d217e04fc5e34fcd0d2cba173ee8ce1c09fe portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/603744 Mon, 16 Jun 2025 23:52:16 -0000 https://status.co-pr.com/incident/603744#e49217703b6ca6d1bf05956d454eb7762130d930582fd2b64542737a4c28db5f api.dev.co-pr.com went down. https://status.co-pr.com/incident/603744 Mon, 16 Jun 2025 07:33:33 -0000 https://status.co-pr.com/incident/603744#ec3ed82bc4de7aa3d2001a1f1007e56b74e0b9a8379724e7dcaf574cc5cfe4b4 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/603744 Mon, 16 Jun 2025 07:33:04 -0000 https://status.co-pr.com/incident/603744#000e887ad48e1becaebb37ea2a387dd27180cf649faed81a6db78deeebc750b1 portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/603744 Mon, 16 Jun 2025 07:27:28 -0000 https://status.co-pr.com/incident/603744#cedeaefc7c9ff6a3a01dd618e64e94a4b7b105f8f3c93deadd04133f8f3ce627 api.dev.co-pr.com went down. https://status.co-pr.com/incident/603744 Mon, 16 Jun 2025 07:27:02 -0000 https://status.co-pr.com/incident/603744#fab62dee840f51c29a0d7509c964fa2748980771b1b83118b36d8819d439aa2c portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/599775 Tue, 10 Jun 2025 07:00:41 -0000 https://status.co-pr.com/incident/599775#5f9d0887c90e76292173e33f4c8c776203c1796d33cd18c550ff1da49ac7c91a portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/599775 Tue, 10 Jun 2025 06:57:39 -0000 https://status.co-pr.com/incident/599775#b13487e039c57aa4f0d8fa9fcb1a12e9d66bf5aa5532b981565fea78c3ba2882 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/599775 Tue, 10 Jun 2025 01:49:07 -0000 https://status.co-pr.com/incident/599775#a0749d7cdae0aff11ece56675b27b352a1fd93c947368bad180925f0c7beae52 api.dev.co-pr.com and portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/599775 Tue, 10 Jun 2025 01:49:07 -0000 https://status.co-pr.com/incident/599775#a0749d7cdae0aff11ece56675b27b352a1fd93c947368bad180925f0c7beae52 api.dev.co-pr.com and portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/599775 Tue, 10 Jun 2025 01:40:10 -0000 https://status.co-pr.com/incident/599775#3993f2b14047de72bcefd1650f7191bb21e656ab8e66e042c4249edf7a686356 api.dev.co-pr.com went down. https://status.co-pr.com/incident/599775 Tue, 10 Jun 2025 01:39:33 -0000 https://status.co-pr.com/incident/599775#cc1d44fa8c4a1ccb05079cae3db6f518b5248f4ad3dd3d3ecd967c983bed5625 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/599775 Tue, 10 Jun 2025 01:12:50 -0000 https://status.co-pr.com/incident/599775#40ed6710f7f69e569b7141c56801779e478a64f4795d8e38debb1252bfc3435e portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/599775 Tue, 10 Jun 2025 01:09:33 -0000 https://status.co-pr.com/incident/599775#05382ce81dcef78bb62c5207235672a84dbdef541ee0032cec26b74be6345059 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/596566 Mon, 09 Jun 2025 12:04:02 -0000 https://status.co-pr.com/incident/596566#faa467ee2dc9aaa4fa7ad1a35256b08f96d8076a656045dda5e5fedbefa150c5 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/596566 Mon, 09 Jun 2025 12:03:34 -0000 https://status.co-pr.com/incident/596566#8fcaee8645fe4d7d93be8eb8b69a639efb41acaf5dd336fb06a1c1aa4ea7f66e portal.dev.co-pr.com/v1 recovered. https://status.co-pr.com/incident/596566 Mon, 09 Jun 2025 11:45:59 -0000 https://status.co-pr.com/incident/596566#b3d6c3cc5a9229c873d14b691d2b57648ed0b44bc24f16a14a9020b7103ea416 api.dev.co-pr.com went down. https://status.co-pr.com/incident/596567 Wed, 04 Jun 2025 07:00:05 -0000 https://status.co-pr.com/incident/596567#63a05dd5dbd01896d9e6db30eaccdc55db4b71a2f791c4872c1b189017f89b77 Maintenance completed https://status.co-pr.com/incident/596567 Wed, 04 Jun 2025 07:00:05 -0000 https://status.co-pr.com/incident/596567#63a05dd5dbd01896d9e6db30eaccdc55db4b71a2f791c4872c1b189017f89b77 Maintenance completed https://status.co-pr.com/incident/596566 Wed, 04 Jun 2025 00:41:42 -0000 https://status.co-pr.com/incident/596566#dba304aae9806250fd8e84c45ff198f03d977e01fa927a8d30549b3334186610 portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/596567 Wed, 04 Jun 2025 00:00:05 -0000 https://status.co-pr.com/incident/596567#54dcb29e9413270de77e74e7af86584506f51baa491a72924c6260940da2283d Currently facing issues with accessing portal, control panel, and dashboard. https://status.co-pr.com/incident/596567 Wed, 04 Jun 2025 00:00:05 -0000 https://status.co-pr.com/incident/596567#54dcb29e9413270de77e74e7af86584506f51baa491a72924c6260940da2283d Currently facing issues with accessing portal, control panel, and dashboard. https://status.co-pr.com/incident/595997 Tue, 03 Jun 2025 13:05:50 -0000 https://status.co-pr.com/incident/595997#db9a871dbf69ef3cb107d87cba808c2abbf5d6fb534f2b333c1be581a8f824e7 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/595997 Tue, 03 Jun 2025 07:53:45 -0000 https://status.co-pr.com/incident/595997#d3e04fd3effd917ca8289cd5314215efd392633e3528eecb3595afaa8ac505c0 api.dev.co-pr.com and portal.dev.co-pr.com/v1 went down. https://status.co-pr.com/incident/595997 Tue, 03 Jun 2025 04:44:14 -0000 https://status.co-pr.com/incident/595997#463a68d1d175c671936df7f2d9fe517dde8630355e2121946a7ec80286dec3d2 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/595997 Tue, 03 Jun 2025 04:23:20 -0000 https://status.co-pr.com/incident/595997#8927e94cc301ee1af8ff0d130db4501446c9e1d57acc33cb9a7af40606bf78f4 api.dev.co-pr.com went down. https://status.co-pr.com/incident/595289 Mon, 02 Jun 2025 13:59:00 -0000 https://status.co-pr.com/incident/595289#9b38100638c3fa261818e056bc7f7144ff57c86a69336dc2a1e9e54303ccd61f Maintenance completed https://status.co-pr.com/incident/595289 Mon, 02 Jun 2025 01:00:00 -0000 https://status.co-pr.com/incident/595289#b02a92c11184e686bdf7b606adef3a82732245fadc95080a13fcbea66e9e72c7 ## 📝 Changelog ### 🔧 Employment Point Calculation Rework - Added support for skill-specific point calculations: - Introduced a new field: `skillCode` to filter and compute points only from employment relevant to the assessed skill. - Enhanced structure for customer employment data: - Work experience is now separated into `past`, `current`, and `future` states. - Refined employment experience computation: - Filters jobs by relevance to the skill assessment. - Calculates income: - For past/current jobs: sum of income in the last year. - For future jobs: uses base salary. --- ### ✅ Employment Validation on Customer Details (Create) - Introduced validation rule for current employment entries: - A customer may have: - Up to 1 full-time employment, OR - 1 full-time and 1 part-time employment, OR - Up to 2 part-time employments. - Any configuration outside these rules will now be rejected with a validation error. - Ensures realistic employment combinations for point and eligibility calculations. --- ### 🏠 New Home Microservice - Provides API endpoints for homepage content. - Includes: - /motivational-quotes: returns a motivational quote and an image. - /point-summary: provides a summary of the customer's point calculation. --- ### 🛂 New Visa Eligibility Microservice - Adds endpoint to evaluate visa eligibility. - Returns: - Status color (e.g. green, yellow, red) for each subclass and visa stream based on customer's eligibility. - Clear reasons and criteria for each status to inform users why they are or aren't eligible. - Enables dynamic frontend display of eligibility status per visa category. --- 🚀 Frontend Portal Deployment Deployed the frontend portal for public access. https://status.co-pr.com/incident/563709 Wed, 14 May 2025 06:51:44 -0000 https://status.co-pr.com/incident/563709#446e81cf95e08a203486253e8af9017c6ee458346e1dd3e2d28e3486c664c6a7 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/563709 Wed, 14 May 2025 06:39:39 -0000 https://status.co-pr.com/incident/563709#1295be9b4e686e7b59b099dfc96d42b56ca5b9d9f006beb60d01b5581300db51 api.dev.co-pr.com went down. https://status.co-pr.com/incident/560315 Wed, 14 May 2025 06:25:01 -0000 https://status.co-pr.com/incident/560315#3998a28bdf9755fe92943126585b077665a7c594460cfcd07ab663192ef88e6b Maintenance completed https://status.co-pr.com/incident/560315 Wed, 14 May 2025 06:00:00 -0000 https://status.co-pr.com/incident/560315#87173ea1eeae0a5fed8942b1d4a0aa965af697508580fe53a6a0e718f248f469 🚧 Major Refactoring Work 📦 Utility Functions Moved common utility files across services into the @bytecronix/co-pr-common-utils NPM package and replaced the imports accordingly: calculateYears dynamicErrorMsg getEnvVariable handleErrorLogs 📐 Interface Standardization Replaced usage of local interfaces (e.g., IResponse) with types from @bytecronix/common-interfaces. 🗃️ Database Model Centralization Replaced usage of common DB models with models from @bytecronix/co-pr-database. https://status.co-pr.com/incident/557869 Wed, 07 May 2025 05:27:10 -0000 https://status.co-pr.com/incident/557869#ad90f43a7dbfb35a50a6a2c9c088365bcb1b791378f80b23e3887e53a2b53ef7 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/557869 Wed, 07 May 2025 05:06:09 -0000 https://status.co-pr.com/incident/557869#447e99843783558ecea66f61c329e78cb85fc0ba15cf8f7d0a86367d04c56a38 api.dev.co-pr.com went down. https://status.co-pr.com/incident/554069 Wed, 07 May 2025 02:30:00 -0000 https://status.co-pr.com/incident/554069#97dfafcb225bd71b5ffabc244428e8adf2e6900ceec96857ddc69e1078608eeb Maintenance completed https://status.co-pr.com/incident/554069 Wed, 07 May 2025 01:00:00 -0000 https://status.co-pr.com/incident/554069#a84390d2d55a3dc9062a51826e8d899f3dbff1eab8a1325227f9db4bd162e81f Visa Education Points Calculation: - Customer details no longer store status of education on whether or not they are valid for regional study and specialist education. - The system iterates through the customer's educations and grants points if any of their educations are valid for Australian study, regional study, and specialist education. Degree Information Enhanced: - The system now allows for multiple ongoing degrees under a user's education history, offering more flexibility. Dropdown Service Authentication - Token validation is now required to access the dropdown service. https://status.co-pr.com/incident/554066 Wed, 30 Apr 2025 01:30:23 -0000 https://status.co-pr.com/incident/554066#0b585f3b9c6543172715e3a7cb4dfacdb6e0efbd0af616907ca3b87938b0bac1 Maintenance completed https://status.co-pr.com/incident/554066 Wed, 30 Apr 2025 01:00:23 -0000 https://status.co-pr.com/incident/554066#c6b2f594b3585c43454d9d0dc9671fea75692e88903f4b731f45008809b98eed New Dropdown Menus Added: You can now select from updated dropdowns for: Permanent Residency Countries English Speaking Countries Community Language Professional year course Improved Data Accuracy for Job Titles: Job titles now include both ANZSCO and OSCA codes, helping ensure correct skill code mapping. We've also updated the data source for cleaner and more accurate listings. System Refactoring & Cleanups: Various technical improvements were made to ensure faster, more reliable dropdown responses and better organization of code behind the scenes. https://status.co-pr.com/incident/549518 Wed, 23 Apr 2025 07:24:22 -0000 https://status.co-pr.com/incident/549518#734f9780009cb4611abd48ce03f02ad5311d1a8b0be8ba8ca26e33ed42c09974 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/549518 Wed, 23 Apr 2025 07:09:22 -0000 https://status.co-pr.com/incident/549518#e955576a95382d336b8d5dfa3048bdd01d51eeccf151417dd20365c2a5fe5e6f api.dev.co-pr.com went down. https://status.co-pr.com/incident/549500 Wed, 23 Apr 2025 07:00:18 -0000 https://status.co-pr.com/incident/549500#92aee339cc0a28c00f0bce564fb1228378a522e4fcdb1a360e433685eda0f409 Maintenance completed https://status.co-pr.com/incident/549500 Wed, 23 Apr 2025 06:30:18 -0000 https://status.co-pr.com/incident/549500#da80c9259689e7d11eccffa28def292872698daf1a3e0683c8d0d0da95b529b5 updated the professional year data structure and response of professional year drop down. Changes: added is_active and deactivated_on filed in both study field level and branch level. We can know if a study_field is canceled or a branch stops running. added validity_period_months in study filed level. give freedom of setting different validity period for different study field. https://status.co-pr.com/incident/548910 Wed, 23 Apr 2025 02:00:34 -0000 https://status.co-pr.com/incident/548910#8e9be1492cfb9775c6c55e91acf2b1d9d86f65bbb65691ce312c10203def3336 Maintenance completed https://status.co-pr.com/incident/548910 Wed, 23 Apr 2025 01:00:34 -0000 https://status.co-pr.com/incident/548910#8c3d130cf199208b08668691165ae665067ca0dee6da569062f2234a3cc5b69e - Moved CustomerDetailsSchema: The Mongoose schema for CustomerDetails has been moved to an exported constant to improve code organization and facilitate reuse. - Modified ArchivedCustomerSchema: A new Mongoose schema, ArchivedCustomerSchema, has been created. This schema is largely based on CustomerDetailsSchema but with the unique constraint on the email field removed to allow for potential duplicate archived entries. - Added archiving constants: New constants related to customer details archiving, such as collection names, have been added to logger.constants.ts. - Added archiveCustomerDetails method: A new method, archiveCustomerDetails, has been implemented. This method takes a customer details document as input and creates a corresponding document in the archived_customers collection. - Updated deleteCustomerDetails method: The deleteCustomerDetails method has been modified to first call archiveCustomerDetails. Only upon successful creation of the archived record will the original customer details be deleted from the customer_details collection. https://status.co-pr.com/incident/548739 Tue, 22 Apr 2025 01:08:17 -0000 https://status.co-pr.com/incident/548739#1005713c122272ff8d4227955cd9580ddc174fab24e0290f2e35f85cde83339b Maintenance completed https://status.co-pr.com/incident/548739 Tue, 22 Apr 2025 01:00:21 -0000 https://status.co-pr.com/incident/548739#e481e75e577f401f27b446e6d180584339ab3eb364e668364970223ebde838a1 * refactor the authentication flow (login, logout, verify session) * add py dropdown * add community language dropdown * add your information update timestamps to customer profile https://status.co-pr.com/incident/548739 Tue, 22 Apr 2025 01:00:21 -0000 https://status.co-pr.com/incident/548739#e481e75e577f401f27b446e6d180584339ab3eb364e668364970223ebde838a1 * refactor the authentication flow (login, logout, verify session) * add py dropdown * add community language dropdown * add your information update timestamps to customer profile https://status.co-pr.com/incident/540612 Mon, 07 Apr 2025 05:15:45 -0000 https://status.co-pr.com/incident/540612#a8fcb61e2f681c299741e2c734ff2c3abf612af9353f8a6811ce4473cb06e678 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/540612 Sun, 06 Apr 2025 04:12:32 -0000 https://status.co-pr.com/incident/540612#1d8eed472302aa1700ea608feced2d0a03541344832ec247840a618026fe77aa api.dev.co-pr.com went down. https://status.co-pr.com/incident/533972 Tue, 25 Mar 2025 04:52:12 -0000 https://status.co-pr.com/incident/533972#0586b2deb0111770402c811797265463cc16471a7f3c72f9065465b1eb55f0c9 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/533972 Tue, 25 Mar 2025 04:49:00 -0000 https://status.co-pr.com/incident/533972#ceab243de2633d7f02a11bf771664ff25f5a5e50bb958f60f89af9f193065ecf api.dev.co-pr.com went down. https://status.co-pr.com/incident/527389 Thu, 13 Mar 2025 04:11:36 -0000 https://status.co-pr.com/incident/527389#8920db2ef4e5a7c79996ab2b0f6c0a5efd519b97fed1084b40f5dcf9f354f564 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/527389 Thu, 13 Mar 2025 02:44:30 -0000 https://status.co-pr.com/incident/527389#9b46ea5c0824ae892a604168c4927caf8a133dcdbd9168001daba97bc281481c api.dev.co-pr.com went down. https://status.co-pr.com/incident/516580 Fri, 21 Feb 2025 12:01:46 -0000 https://status.co-pr.com/incident/516580#b1c0461d335c198143998a1edc75fd94290499bf736df16734ad4cb6c550799a api.dev.co-pr.com recovered. https://status.co-pr.com/incident/516580 Fri, 21 Feb 2025 09:56:13 -0000 https://status.co-pr.com/incident/516580#4c45abdb0df20b16f9b08603d8083e725fce6333f4a1585ca311c75b71103995 api.dev.co-pr.com went down. https://status.co-pr.com/incident/516580 Fri, 21 Feb 2025 07:10:36 -0000 https://status.co-pr.com/incident/516580#7fe2ef5b5bb9ab9c7ed8aa6b1f85370d0558b4d36fbe0eb954a3cee9c723c4e0 api.dev.co-pr.com recovered. https://status.co-pr.com/incident/516580 Fri, 21 Feb 2025 05:55:12 -0000 https://status.co-pr.com/incident/516580#3b82b245425ddc64b56581ad514f828943b292167209fe4b75ea790e7eb2c96a api.dev.co-pr.com went down. https://status.co-pr.com/incident/515789 Thu, 20 Feb 2025 05:00:16 -0000 https://status.co-pr.com/incident/515789#90114a97b33dcd1d5d75da1c3bde0537d6b661d63341e090e74c9420fb930010 Maintenance completed https://status.co-pr.com/incident/515789 Thu, 20 Feb 2025 04:00:16 -0000 https://status.co-pr.com/incident/515789#860e46dc11b416e14b4389bb2429f3d7db65d4520e6e507aa121de85c3c7c207 - Cleaned up dead code / unnecessary features for a lighter, faster deployment https://status.co-pr.com/incident/510848 Tue, 11 Feb 2025 06:32:46 -0000 https://status.co-pr.com/incident/510848#1cb37c3ce48222362b013bfc4871e21692f06c89e2157689df1c0c5941b5a7ff api.dev.co-pr.com recovered. https://status.co-pr.com/incident/510848 Tue, 11 Feb 2025 06:20:36 -0000 https://status.co-pr.com/incident/510848#67ff07b6cb691725e4792c9d4d09199a020c20c438719a78ab8f30716094a244 api.dev.co-pr.com went down. https://status.co-pr.com/incident/508083 Sun, 09 Feb 2025 05:30:01 -0000 https://status.co-pr.com/incident/508083#4734ad50e1a1a2dda18091ff28049476ffd1e14db1b18e8ee1b31d83592f0995 Maintenance completed https://status.co-pr.com/incident/508083 Thu, 06 Feb 2025 05:30:01 -0000 https://status.co-pr.com/incident/508083#fd1c390fdddfa9f63e2a41b1708dd2833c2a26fa1cac1c521d0b5811aac3ec2c Maintenance Notice: Cluster Upgrade and Cost Optimization We will be performing maintenance on the `dev-cluster` to optimize our infrastructure costs. The goal is to transition from an auto-scaling setup to a standard GKE cluster using spot instances, which will help significantly reduce our cloud expenses. The work will include: - Creating a new GKE cluster with spot instances. - Migrating all microservices, deployments, and configurations to the new cluster. - Attaching the existing SSL certificate and ensuring API access via `api.dev.co-pr.com`. - Updating DNS records to point to the new cluster. - Removing the old cluster to stop unnecessary costs. During this maintenance window, there may be brief service interruptions as we perform the migration. We will do our best to minimize disruptions and will keep you informed of any changes. Thank you for your understanding! https://status.co-pr.com/incident/503494 Wed, 29 Jan 2025 00:54:59 -0000 https://status.co-pr.com/incident/503494#3ed6e63f651a67d75404c7d979ce3c2b993790d03d8c8418e9b6450f7631934c api.dev.co-pr.com recovered. https://status.co-pr.com/incident/503494 Wed, 29 Jan 2025 00:51:32 -0000 https://status.co-pr.com/incident/503494#9873ac4709b38f6adf397f4a86a38507f0cec536d54dc20b29a76816edfef652 api.dev.co-pr.com went down. https://status.co-pr.com/incident/500500 Thu, 23 Jan 2025 09:00:03 -0000 https://status.co-pr.com/incident/500500#c0b6cc61a817cfe4aaa0dd7e63fcfb2380281f918cff27b9fe68c6e9aed0c3f1 Maintenance completed https://status.co-pr.com/incident/500500 Thu, 23 Jan 2025 07:53:03 -0000 https://status.co-pr.com/incident/500500#64d8259896cd15b2f04b9d6d864d5fab0cf62ff345c52489a9fb9f10ed240559 Uploading Modular Swagger Document Fixing HTTPS-Routes GCP Error https://status.co-pr.com/incident/500421 Thu, 23 Jan 2025 05:30:36 -0000 https://status.co-pr.com/incident/500421#46f58cbc28a29894570fe859259f70bccb50b22883628ac3057bb1f98c7e1903 Maintenance completed https://status.co-pr.com/incident/500421 Thu, 23 Jan 2025 01:30:36 -0000 https://status.co-pr.com/incident/500421#3c9958ce617c7ae78efdbba19a01d46384382c8990c66da4c190e957b68a9c9d Pull Request: NGINX Configuration Update for Swagger Docs Overview This pull request updates the NGINX configuration to properly serve Swagger documentation for the API. The changes ensure that the /swagger/ route is correctly mapped and serves the Swagger UI files, as well as the YAML API specification for iOS and Android. Changes Made Updated NGINX configuration: Added a location block for serving Swagger UI HTML files under /swagger/. Configured the Swagger API YAML files (iosApi.yaml and androidApi.yaml) to be served under /ios and /android. Applied aliasing for Swagger UI assets to ensure they are correctly served from /usr/share/nginx/html/swagger-ui/. Set the correct MIME type for YAML files to application/yaml. NGINX Error Logging: Added error logging configuration with debug level to help with troubleshooting. Testing Swagger UI Access: Tested accessing https://api.dev.co-pr.com/swagger/ to verify that Swagger UI loads correctly. Ensured that the /swagger/index.html loads and displays the API documentation. YAML File Access: Accessed /swagger/ios and /swagger/android to confirm that the correct YAML files (iosApi.yaml and androidApi.yaml) are being served and the content is valid. HTTP to HTTPS Redirection: Ensured that HTTP traffic is properly redirected to HTTPS. Related Issues None Checklist Updated NGINX configuration to serve Swagger documentation Tested Swagger UI and YAML file access Enabled error logging for debugging Verified HTTP to HTTPS redirection is functional Additional Information The configuration is now set up to serve Swagger UI from /swagger/ and YAML files from /ios and /android. Ensure that the file paths for the YAML files are correct and they are accessible within the NGINX container. https://status.co-pr.com/incident/497123 Fri, 17 Jan 2025 01:54:07 -0000 https://status.co-pr.com/incident/497123#4aede447aebfc191a0e98d5f635656af94054bd60ef8ea20a729e1dc64fa0c82 Maintenance completed https://status.co-pr.com/incident/497123 Thu, 16 Jan 2025 23:54:07 -0000 https://status.co-pr.com/incident/497123#8a5c1af329a093a97ba95826e4f3b20a0e5f691f4a8326aeaf656ef23a9716d9 After today’s maintenance, these features can be tested: - CustomerDetails CRUD operations - CustomerEligibility GET operation - Points Calculations (Current and Proposed) - Nationality and job title dropdown https://status.co-pr.com/incident/496088 Wed, 15 Jan 2025 06:04:42 -0000 https://status.co-pr.com/incident/496088#d39d563f9a29b4c6b3f4c038b38e28e384e764a805ef92f455c74ff742a00bd0 Maintenance completed https://status.co-pr.com/incident/496088 Wed, 15 Jan 2025 06:00:00 -0000 https://status.co-pr.com/incident/496088#3bf469872c9d0fcc0907bf85161b50f96738c80368542a2739fcb189feb41807 1) Created Shared micro services for the Back end to better align the package structures. Created shared and common/dropdown microservices Have shared bridge requests between the bffs and microservices Only kept authentication logic in android and ios, shared handles the rest Successfully deployed.