Incidents reported on status page for Qriosum https://status.qriosum.com/ en https://status.qriosum.com/incident/829484 Fri, 20 Feb 2026 13:40:39 -0000 https://status.qriosum.com/incident/829484#31abbe3ca1bfc6a1153f8eaae6216f6f4c7bff66ac1c3a7ebd0e19a90cc5b824 Qriosum API recovered. https://status.qriosum.com/incident/829484 Fri, 20 Feb 2026 13:34:33 -0000 https://status.qriosum.com/incident/829484#708b6f743494dbf2b033a946b4d5457c4db245686f048ef7562e71e559b7c589 Qriosum API went down. https://status.qriosum.com/incident/829484 Fri, 20 Feb 2026 13:25:46 -0000 https://status.qriosum.com/incident/829484#07656645044957a167c5cdb83fa4fa9e327ec0928503141af7f9df389ca23068 Qriosum API recovered. https://status.qriosum.com/incident/829484 Fri, 20 Feb 2026 13:19:32 -0000 https://status.qriosum.com/incident/829484#01a9f74b5729ec0bd9e89dd3f559700cf9424a74b6a2db7047a72c7af6d48348 Qriosum API went down. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 13:07:32 -0000 https://status.qriosum.com/incident/828740#b821eb470e3f02d13c7bbe0fdbdaac0632dc3dd95fdbafea181c8ec687ecc40b Qriosum API recovered. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 13:06:34 -0000 https://status.qriosum.com/incident/828740#d750f4414b85e30df558d0dc631607b201bcca4ec4857a09a27a4deb9bb86cc4 Qriosum frontend recovered. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 13:01:22 -0000 https://status.qriosum.com/incident/828740#d455924a3c731382ea89fbb1ec2fb81c5cdc6f8210013b7b920a60f8f35375c8 Qriosum frontend went down. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 13:00:41 -0000 https://status.qriosum.com/incident/828740#69780ecd3ffcdb681dbbd263addf2350bbcb12dfdbaba0096a417ce681822b9b Qriosum frontend recovered. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 12:55:32 -0000 https://status.qriosum.com/incident/828740#1f0b87f59e6c61cc98eba7fd1df347b64e7dbea2aac333ea586493676479063a Qriosum frontend and Qriosum API went down. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 12:55:32 -0000 https://status.qriosum.com/incident/828740#1f0b87f59e6c61cc98eba7fd1df347b64e7dbea2aac333ea586493676479063a Qriosum frontend and Qriosum API went down. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 12:12:39 -0000 https://status.qriosum.com/incident/828740#9737f7697f422baa35946dfdf2e13b0eb2924224ce622b22fb728d1722caa352 Qriosum frontend recovered. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 12:10:34 -0000 https://status.qriosum.com/incident/828740#64bbee3dfb2d697abbfeba87a600128c97f6be3de16f2138fe08707b41ce571c Qriosum API recovered. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 12:04:28 -0000 https://status.qriosum.com/incident/828740#5ecf88070f38fc6ea6d0ccc74d44bd807f83b3c7177fe22d01d8fb6db8dcc9c7 Qriosum frontend and Qriosum API went down. https://status.qriosum.com/incident/828740 Thu, 19 Feb 2026 12:04:28 -0000 https://status.qriosum.com/incident/828740#5ecf88070f38fc6ea6d0ccc74d44bd807f83b3c7177fe22d01d8fb6db8dcc9c7 Qriosum frontend and Qriosum API went down. https://status.qriosum.com/incident/827885 Wed, 18 Feb 2026 09:31:51 -0000 https://status.qriosum.com/incident/827885#4fa94259d927a40ad3a72f8f1daf54ed368dd3505af65321c62dceda48ad5f2f Qriosum API recovered. https://status.qriosum.com/incident/827885 Wed, 18 Feb 2026 09:26:30 -0000 https://status.qriosum.com/incident/827885#95387a7396b643f8f6788c5c4fb5a6e6d2bf7648ba438b92533d2208fdb76160 Qriosum API went down. https://status.qriosum.com/incident/827229 Tue, 17 Feb 2026 12:31:41 -0000 https://status.qriosum.com/incident/827229#4c27c8c3762b3832047e4233b93678f6ef07aabf71425174fab7158dbfae6939 Qriosum API recovered. https://status.qriosum.com/incident/827229 Tue, 17 Feb 2026 12:25:39 -0000 https://status.qriosum.com/incident/827229#7b381708f2c312c5d0868e209ff921e2d1b5e46946fa67e76ea44b8b1dfab978 Qriosum API went down. https://status.qriosum.com/incident/805571 Fri, 16 Jan 2026 07:40:30 -0000 https://status.qriosum.com/incident/805571#ee74d35143a7ad7859dc7406b24b5f53ae7621de2621930c9a0fa20a9c103777 Qriosum API recovered. https://status.qriosum.com/incident/805571 Fri, 16 Jan 2026 07:31:35 -0000 https://status.qriosum.com/incident/805571#dec580e58e0f6a3fa459ebce01b8437c405aa015ac9a5b8da42b1865020d29a0 Qriosum API went down. https://status.qriosum.com/incident/805571 Fri, 16 Jan 2026 07:22:43 -0000 https://status.qriosum.com/incident/805571#b5228d375b4d19d057fbae8f7de6f5605f3475369159c2b01a69b232a52a021b Qriosum API recovered. https://status.qriosum.com/incident/805571 Fri, 16 Jan 2026 07:16:35 -0000 https://status.qriosum.com/incident/805571#6f178e5dfb400d32456f9a54d22153a26c4a9da09d55a5599505eef25c6a8b89 Qriosum API went down. https://status.qriosum.com/incident/804211 Wed, 14 Jan 2026 10:13:46 -0000 https://status.qriosum.com/incident/804211#67e46abb577eca01e183f1f13b3713e1fb87d4d3d6b3839f4024faec6e177357 Qriosum API recovered. https://status.qriosum.com/incident/804211 Wed, 14 Jan 2026 10:04:45 -0000 https://status.qriosum.com/incident/804211#90f40859e613adef18bf4d39465a22650535b00c0a1c1b482711e0fca03a5091 Qriosum API went down. https://status.qriosum.com/incident/802629 Mon, 12 Jan 2026 00:39:35 -0000 https://status.qriosum.com/incident/802629#4d6e9b4e0c766cf24f16eaadd0ee298c2f8df1181766e0ff8b7e3b728d2115e1 Qriosum frontend recovered. https://status.qriosum.com/incident/802629 Mon, 12 Jan 2026 00:16:44 -0000 https://status.qriosum.com/incident/802629#e3a1b69148c8b33a2a59b12255ceedf1d7fce76abe44c6339f0004d4f6a7f617 Qriosum frontend went down. https://status.qriosum.com/incident/800618 Thu, 08 Jan 2026 11:16:42 -0000 https://status.qriosum.com/incident/800618#8f7a76a224e48853d5cfcb0ab8bebce7bef22eb29e4d3726f066c2b0616171ac Qriosum API recovered. https://status.qriosum.com/incident/800618 Thu, 08 Jan 2026 11:10:34 -0000 https://status.qriosum.com/incident/800618#73d808a647b028f13668b17527d6098265f2fc6b08a3c7c377686b6911c85b25 Qriosum API went down. https://status.qriosum.com/incident/796567 Wed, 31 Dec 2025 10:07:48 -0000 https://status.qriosum.com/incident/796567#4343ff69bf43d4e46596784310744873de18fa3bf82a065b42ffe931acece6db Qriosum API recovered. https://status.qriosum.com/incident/796567 Wed, 31 Dec 2025 10:01:31 -0000 https://status.qriosum.com/incident/796567#41c2a3254f7df429b6b25f29c7d2f257ffb8abb3c78da429bc5cbf30c5108bf4 Qriosum API went down. https://status.qriosum.com/incident/782029 Mon, 08 Dec 2025 06:06:19 -0000 https://status.qriosum.com/incident/782029#62aa40f1b1cf7cab4f7f7c665697f505279146d0e52130a22920834c07e9da83 Qriosum API recovered. https://status.qriosum.com/incident/782029 Mon, 08 Dec 2025 06:00:19 -0000 https://status.qriosum.com/incident/782029#212665fc1dc02c20688254be5d86d485503fabf05d7e5a18c2e5a9ee0e6bd9f3 Qriosum API went down. https://status.qriosum.com/incident/774357 Wed, 26 Nov 2025 04:29:39 -0000 https://status.qriosum.com/incident/774357#17b9ec45f73403873500cda34f304fcdf13c73f11a1d8f07ee536ca79088bbe1 Qriosum frontend recovered. https://status.qriosum.com/incident/774357 Wed, 26 Nov 2025 04:18:44 -0000 https://status.qriosum.com/incident/774357#96d21f20a5cc07ca34434434d5ae962a5bbf0615c1041f4bade41129ea967584 Qriosum frontend went down. https://status.qriosum.com/incident/773703 Tue, 25 Nov 2025 06:45:11 -0000 https://status.qriosum.com/incident/773703#759a730aad5dd4478513300c00aa0facbf8c1ee5bd1caff095e896acdcb36703 Qriosum API recovered. https://status.qriosum.com/incident/773703 Tue, 25 Nov 2025 06:39:12 -0000 https://status.qriosum.com/incident/773703#71252d656b51e893282689cc481deaef1aaf4fb987f6ed2b98a47db3dd616be2 Qriosum API went down. https://status.qriosum.com/incident/762534 Wed, 12 Nov 2025 00:18:39 -0000 https://status.qriosum.com/incident/762534#cd0fbe8a8a77b4ca1590c47450c8316a2d4ef7f6490c87a846c0cbf47ac7a1b5 Qriosum API recovered. https://status.qriosum.com/incident/762534 Wed, 12 Nov 2025 00:17:34 -0000 https://status.qriosum.com/incident/762534#9c9e7aa6b383b9a609bf51f0ea9709b173eb441ab85ba6a076082245c957cf0b Qriosum frontend recovered. https://status.qriosum.com/incident/762534 Wed, 12 Nov 2025 00:09:25 -0000 https://status.qriosum.com/incident/762534#3b7f7e69d0da3f88d355ff1ae364ad4703bda939e7f5a070580cd0ad25043d26 Qriosum frontend and Qriosum API went down. https://status.qriosum.com/incident/762534 Wed, 12 Nov 2025 00:09:25 -0000 https://status.qriosum.com/incident/762534#3b7f7e69d0da3f88d355ff1ae364ad4703bda939e7f5a070580cd0ad25043d26 Qriosum frontend and Qriosum API went down. https://status.qriosum.com/incident/761228 Mon, 10 Nov 2025 04:52:27 -0000 https://status.qriosum.com/incident/761228#6db2e3b3f560251936936b9c1924a1c93e90047955ed244cd7fdfd5a94cf2ed0 Qriosum API recovered. https://status.qriosum.com/incident/761228 Mon, 10 Nov 2025 04:46:23 -0000 https://status.qriosum.com/incident/761228#1f6a900e8819e9c16ac0f8e24a3f89fd53a3742f86c064518956b21ff774b8e5 Qriosum API went down. https://status.qriosum.com/incident/760738 Sun, 09 Nov 2025 03:31:43 -0000 https://status.qriosum.com/incident/760738#528d9e066894448e620af5a0c03fe6c7f7d28b98c3a0acfebf173878e23543e8 Qriosum API recovered. https://status.qriosum.com/incident/760738 Sun, 09 Nov 2025 03:25:31 -0000 https://status.qriosum.com/incident/760738#0205f7144bcf9e4c94d2a220295642be57867db748a92179151111f9bd2ccc4d Qriosum API went down. https://status.qriosum.com/incident/754192 Thu, 30 Oct 2025 01:39:02 -0000 https://status.qriosum.com/incident/754192#81695f8df7d4511338462395395349091d979e4ad605a543360b5aaa15f466ae Qriosum frontend recovered. https://status.qriosum.com/incident/754192 Thu, 30 Oct 2025 01:30:32 -0000 https://status.qriosum.com/incident/754192#0492c1c792c97eed3e929d994ab6b36fb13503db16dc6c69f3cb282e96be3415 Qriosum frontend went down. https://status.qriosum.com/incident/754192 Thu, 30 Oct 2025 01:23:53 -0000 https://status.qriosum.com/incident/754192#16324888c889007e1a50ce60020712f65bae1d4291b96a485a1594a35eb67011 Qriosum frontend recovered. https://status.qriosum.com/incident/754192 Thu, 30 Oct 2025 01:21:54 -0000 https://status.qriosum.com/incident/754192#e66d9217e7ef1f144769a7a2cab8751c7b9895e7112cc5e656a971ce10921097 Qriosum API recovered. https://status.qriosum.com/incident/754192 Thu, 30 Oct 2025 01:12:33 -0000 https://status.qriosum.com/incident/754192#eb4169e0803ae36200506959ff91ec22d5ae40d3f92ef6aba5f6129247471216 Qriosum frontend went down. https://status.qriosum.com/incident/754192 Thu, 30 Oct 2025 01:09:55 -0000 https://status.qriosum.com/incident/754192#0b72dba304c3239f767725737d91609cc4c60470fab572a8b6cbcaf1f9762332 Qriosum API went down. https://status.qriosum.com/incident/751852 Mon, 27 Oct 2025 00:21:37 -0000 https://status.qriosum.com/incident/751852#69ec029a033e325af610c8264ad955b0900dd02d1f718d506c1ab99582754358 Qriosum API recovered. https://status.qriosum.com/incident/751852 Mon, 27 Oct 2025 00:18:58 -0000 https://status.qriosum.com/incident/751852#f4bc45b736a1cf057871ec4f278e275bf4bd9ff416fc173e4c8f73b0088ccce9 Qriosum frontend recovered. https://status.qriosum.com/incident/751852 Mon, 27 Oct 2025 00:13:52 -0000 https://status.qriosum.com/incident/751852#8599c00acf86217c1c66e1a02a31e9cb4d26a30fd00cacd45c72c14692ba7fa8 Qriosum frontend and Qriosum API went down. https://status.qriosum.com/incident/751852 Mon, 27 Oct 2025 00:13:52 -0000 https://status.qriosum.com/incident/751852#8599c00acf86217c1c66e1a02a31e9cb4d26a30fd00cacd45c72c14692ba7fa8 Qriosum frontend and Qriosum API went down. https://status.qriosum.com/incident/751311 Sat, 25 Oct 2025 20:25:18 -0000 https://status.qriosum.com/incident/751311#1c74dad330e458ff4d54764b6216a0ca65fa47f0684015b6e454e01594131d6d Qriosum API recovered. https://status.qriosum.com/incident/751311 Sat, 25 Oct 2025 20:21:36 -0000 https://status.qriosum.com/incident/751311#d25229cde2e72c7e0f374b28f308ec0a0642b7da8597c727d141d90b89f09ad2 Qriosum API went down.