Incidents reported on status page for Inex One https://status.inex.one/ https://d1lppblt9t2x15.cloudfront.net/logos/5887449ae70aaad9a735ac38ce1570b9.png https://status.inex.one/ en https://status.inex.one/incident/846645 Wed, 11 Mar 2026 05:19:59 -0000 https://status.inex.one/incident/846645#efe8cdde614ba6f0ef0a45b5811d78f01432aba8ad9c670cd2d506613eaf8d91 Backend services recovered. https://status.inex.one/incident/846645 Wed, 11 Mar 2026 05:16:11 -0000 https://status.inex.one/incident/846645#3471d679218d4050ee8abdc8d7c7084407640c8030723fbfbab3ecb9e8c49df8 Backend services went down. https://status.inex.one/incident/845091 Mon, 09 Mar 2026 09:17:26 -0000 https://status.inex.one/incident/845091#1d6ed1aac7330fe6033fdc232b87b0f23388266ff3c718c630380980abeeec1b Backend services recovered. https://status.inex.one/incident/845091 Mon, 09 Mar 2026 09:12:31 -0000 https://status.inex.one/incident/845091#cfe66a796c0a97844e8450318222b4963bc61e44c63dad26d414f8fced30fe6d Backend services went down. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 23:31:57 -0000 https://status.inex.one/incident/842386#be5c6570da59a3a9d7edc7cef4df425bc4492eb76981922f9509a05697058ce4 Backend services recovered. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 23:27:22 -0000 https://status.inex.one/incident/842386#60be42845edcdfa96e2d189fc374837b4f0f2210c9d158e375aa5c6744fcc20f Backend services went down. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 15:54:57 -0000 https://status.inex.one/incident/842386#bc195df5f0ee00b0be2e33d986c983075cb8ae52bdb648ff028f1c9066744d75 Backend services recovered. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 15:51:24 -0000 https://status.inex.one/incident/842386#6e48e530c29df02e1921e79fa9caeac030c49316dd53223341c46d8cba5270c3 Backend services went down. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 15:09:52 -0000 https://status.inex.one/incident/842386#79bfec6edd5483b491e334a2c55d2345d3f4b31f766f945732d3aa87b59a2d1f Backend services recovered. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 15:05:28 -0000 https://status.inex.one/incident/842386#ada15fdc43f0287c27148ecf8d616577da3704672073faff1af359dd2b507dfb Backend services went down. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 14:23:29 -0000 https://status.inex.one/incident/842386#bd42cd7277e2764943cdaa07e77c5d23abc5586b620c25b1913448e51531db2c Backend services recovered. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 14:18:33 -0000 https://status.inex.one/incident/842386#d24decd3a99236efd4471086bffbb911971262d197c8cd6b0e824dca552fe4ec Backend services went down. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 13:21:33 -0000 https://status.inex.one/incident/842386#38a3da111fe595e1bac134bef8ac6162171b238e5c67179e072702c0edd14885 Backend services recovered. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 13:17:37 -0000 https://status.inex.one/incident/842386#98e3040a2dc0f66a941e11dd0871c61bb2e1013b05efe6d382cab1664833b69f Backend services went down. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 11:20:27 -0000 https://status.inex.one/incident/842386#30f4e779c2b525b14f9a6c9f2cb3b9683b61bba68d36682190330bfd1163a7f8 Backend services recovered. https://status.inex.one/incident/842386 Fri, 06 Mar 2026 11:15:26 -0000 https://status.inex.one/incident/842386#f8760f55cdd2a414f43e91ea6720510068a65b4d9a62064b5b6385a5ee225ea6 Backend services went down. https://status.inex.one/incident/841767 Thu, 05 Mar 2026 21:41:58 -0000 https://status.inex.one/incident/841767#686129ab701758166a4c930b55ab82f93a70d0a17dc8f6705ee79c35086954d8 Backend services recovered. https://status.inex.one/incident/841767 Thu, 05 Mar 2026 21:38:22 -0000 https://status.inex.one/incident/841767#500b8e5b39b12a235ae2435bbd34c2bad03d781790a4038b73d074c124722eee Backend services went down. https://status.inex.one/incident/839629 Wed, 04 Mar 2026 16:53:29 -0000 https://status.inex.one/incident/839629#77252aac1c8135fce825ef143234ca22f928736c755a7d6e7b803c6ee3aa8175 Backend services recovered. https://status.inex.one/incident/839629 Wed, 04 Mar 2026 16:49:45 -0000 https://status.inex.one/incident/839629#e774e4562ec36eb9ce58b82c63da223d0e8d1da1b868b66982e8c5f1b7fa6e8b Backend services went down. https://status.inex.one/incident/839629 Wed, 04 Mar 2026 12:52:22 -0000 https://status.inex.one/incident/839629#19dd93a459b0f6e2f54a6ff4ff8236ef2b1dd0bbae25feca14e50b32609df539 Backend services recovered. https://status.inex.one/incident/839629 Wed, 04 Mar 2026 12:48:48 -0000 https://status.inex.one/incident/839629#dd20954911729a9b4f29eab040522da6ec366120e2b1e4ed0e411c697f672271 Backend services went down. https://status.inex.one/incident/839629 Wed, 04 Mar 2026 03:02:05 -0000 https://status.inex.one/incident/839629#25a38cee9b31b669f6a1c8aab4c1dc9bd05890d886ac8657b962628098262a4d Backend services recovered. https://status.inex.one/incident/839629 Wed, 04 Mar 2026 02:58:03 -0000 https://status.inex.one/incident/839629#67fefe9a7c0038337b9dcd6a7f827b137fd64d332e2246dc727efcb1bb408bc8 Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 23:01:24 -0000 https://status.inex.one/incident/838754#b6a2b655a46618c3837cebbe7c4a369443d42d7164e8c033a79bf5e7b979c24d Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 22:56:24 -0000 https://status.inex.one/incident/838754#16a09c107989a10295c8bfba8252f5f005619b9bf07d5dcc175cf83a463881a0 Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 18:41:59 -0000 https://status.inex.one/incident/838754#5302925368520540c15e5beca4a9c7b39fad9fec9b845db99cabb1c67986e4a6 Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 18:37:54 -0000 https://status.inex.one/incident/838754#28bd3f170405c8c39a9e7ae6a28286f2ccc21d830dfaa25b4faa392f9b3f8cb9 Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 18:20:15 -0000 https://status.inex.one/incident/838754#80955be760b7e489692bb683dc2197004f3f019bf011b278657372eba0738380 Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 18:16:03 -0000 https://status.inex.one/incident/838754#5c0bfacee1f2e2dea28ab6381981f84974057757551157eb99dfb8ee86f3121e Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 17:06:23 -0000 https://status.inex.one/incident/838754#8044d919c24e6512a22b6836669724f908d490d5110d0207a7de1831936f1da1 Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 17:02:24 -0000 https://status.inex.one/incident/838754#1e6504da6385889df875d023bec44d875417d59597775cce3eb2e41158964a1d Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 14:45:36 -0000 https://status.inex.one/incident/838754#e3b42c753e430cf6290af40d6f7b332c7dbd28e18f7f5df50810cd4396093d52 Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 14:40:57 -0000 https://status.inex.one/incident/838754#a6bf12b8ad250b3fae7466b3062d7a9949015e20bbbc87b261ad6b2b82c211d8 Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 14:25:01 -0000 https://status.inex.one/incident/838754#c9f05465f4ab50d8c01b56f1de2409d4be948c716387dc248034154a9d83109f Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 14:20:31 -0000 https://status.inex.one/incident/838754#f87654a983a12fd3a5e67264acacc66060ec2f8937115e502a76d94fc640b01b Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 14:09:31 -0000 https://status.inex.one/incident/838754#7de29d28633a9d15008f7f0f08b75311a1f7165e839b20b96dca6b44bb513095 Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 14:05:58 -0000 https://status.inex.one/incident/838754#41bf369c6cfbc8719c36461eabe16383bf5b473f79c8e96084f4a76b5115f39d Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 13:54:26 -0000 https://status.inex.one/incident/838754#3bdaccaa7bc15a3c54abcbb0c8f79e112c130c95295d37ea464d4348187c243a Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 13:50:32 -0000 https://status.inex.one/incident/838754#428036821c65d782d5d33d61c32ee3278196ea55c4a1d402db5a3bbdbdfa29a0 Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 11:52:05 -0000 https://status.inex.one/incident/838754#cc648f1fa0711e240e2ae276bfd03a8f54b7ed977dabc715e14a3ed1097d46ad Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 11:47:53 -0000 https://status.inex.one/incident/838754#f70d0452b040b2927824808af6077d0d6c4dad3aab6847c103dfbe96bf6c9619 Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 10:00:05 -0000 https://status.inex.one/incident/838754#0e77096dbcccaf695c2baafe12c62cff97839c9294efaba47a61dee352982c7c Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 09:55:21 -0000 https://status.inex.one/incident/838754#d3f177f6e040a700c45c3458ef5ffb71d6255519790f78e8c3172aa4560d0ffb Backend services went down. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 08:47:20 -0000 https://status.inex.one/incident/838754#b388081a14eedbf79f18819b29ad00b34521e1f43879ae0c8f40eba76f022a87 Backend services recovered. https://status.inex.one/incident/838754 Tue, 03 Mar 2026 08:40:11 -0000 https://status.inex.one/incident/838754#9262c2c321e7363bab41c938473501394414b0e4f515689ed6019067933d827d Backend services went down. https://status.inex.one/incident/837965 Mon, 02 Mar 2026 15:15:21 -0000 https://status.inex.one/incident/837965#12b184b4bba390b0d7c2482f6e1eb3a4f5dac9e7c7a1018027156b97365a9c3a Backend services recovered. https://status.inex.one/incident/837965 Mon, 02 Mar 2026 15:10:54 -0000 https://status.inex.one/incident/837965#5a47e84292d8b8caf249738e6159f457d78f2556b4bf4b4dc90e20fedc08e26d Backend services went down. https://status.inex.one/incident/837965 Mon, 02 Mar 2026 15:10:32 -0000 https://status.inex.one/incident/837965#3e9e4d890efc50d258bf52ff6939ea650d173b0d06a6a6b38fbcf1dc83376df6 Backend services recovered. https://status.inex.one/incident/837965 Mon, 02 Mar 2026 15:05:23 -0000 https://status.inex.one/incident/837965#f3680e2b588d9f381f8dfd00b0444d7e4110c0157da1b659f575ac3462885afc Backend services went down. https://status.inex.one/incident/835875 Sat, 28 Feb 2026 05:23:53 -0000 https://status.inex.one/incident/835875#0f0b9226197a19f68794d727c8f148515f7ab060aedad0e06199fb72f15ad02e Backend services recovered. https://status.inex.one/incident/835875 Sat, 28 Feb 2026 05:20:23 -0000 https://status.inex.one/incident/835875#43b94c7fea548a9ca6102506e6c4a5084d3e4390297ec79d9d3df4850d49d38a Backend services went down. https://status.inex.one/incident/830022 Sat, 21 Feb 2026 07:56:54 -0000 https://status.inex.one/incident/830022#63cfbeb2009628866b70aafbcff39f4f42bf1aea21d69bd6690bad1801eee682 Backend services recovered. https://status.inex.one/incident/830022 Sat, 21 Feb 2026 07:53:16 -0000 https://status.inex.one/incident/830022#7b02721120dcbb1ae6d7abf1794f1bf885bba0d71705a0d2de9b425ca32b7332 Backend services went down. https://status.inex.one/incident/811276 Sun, 25 Jan 2026 01:49:13 -0000 https://status.inex.one/incident/811276#3457ae312ee1f2c87f16865503abda4fd36e878f0df873712ffc34591216dabb Backend services recovered. https://status.inex.one/incident/811276 Sun, 25 Jan 2026 01:45:13 -0000 https://status.inex.one/incident/811276#7d21d09a12b797c1b040d0bdbc96e11d22c65a799c4e4b3c3a8eeed31c3c0065 Backend services went down. https://status.inex.one/incident/809705 Thu, 22 Jan 2026 15:18:00 -0000 https://status.inex.one/incident/809705#fe92b9949ecc6d4e3314be3db2b33fa418946aee5bfd075a914902c7d5703fb3 API connectivity degradation for a subset of users in the Ireland region. Summary Between 2026-01-22T09:33:35.957Z and 2026-01-22T15:08:57.765Z today, a subset of API requests originating from the EU West (Dublin) region failed to connect to our backend services, resulting in timeouts or connection errors (5xx). Traffic from other global regions (e.g., France, US, Asia) remained unaffected. The issue was traced to a regional routing conflict between our edge network provider and our application hosting infrastructure. A background infrastructure update in the Dublin datacenter created an incompatibility in how internal traffic was routed between these two providers within the same physical location. This caused connections initiated from Dublin to be dropped before reaching our application servers, despite the services being healthy. Resolution Our engineering team identified the routing loop and deployed a configuration update to force traffic through an alternative, stable network path. This effectively bypasses the conflict in the Dublin datacenter. The fix has now been verified, and all systems are operating normally. We have implemented monitoring to ensure this specific routing path remains stable. https://status.inex.one/incident/797923 Sat, 03 Jan 2026 15:55:57 -0000 https://status.inex.one/incident/797923#36049d55d2399c7e39fcdab310a943cb4bc5097cc67390763558d915afa84485 Backend services recovered. https://status.inex.one/incident/797923 Sat, 03 Jan 2026 15:52:19 -0000 https://status.inex.one/incident/797923#5afaa26a32f76efb751c5048af2b8a9fb05c7a8e71c658f744cfdc72a7843e2a Backend services went down. https://status.inex.one/incident/780137 Fri, 05 Dec 2025 09:14:00 -0000 https://status.inex.one/incident/780137#52105443fbdb60813193454374a5a3e0f22a448d80f8dd0a70e8eef9cb264125 Cloudflare has issued a fix, out services are back online https://status.inex.one/incident/780137 Fri, 05 Dec 2025 09:14:00 -0000 https://status.inex.one/incident/780137#52105443fbdb60813193454374a5a3e0f22a448d80f8dd0a70e8eef9cb264125 Cloudflare has issued a fix, out services are back online https://status.inex.one/incident/780137 Fri, 05 Dec 2025 08:49:00 -0000 https://status.inex.one/incident/780137#15b58808dabc2ccaf5175db61f1c883b7f0ee4cdafe303f16a8d61bc0d639745 Cloudflare, one of our upstream providers is currently down. The issue affects most websites and services around the world https://status.inex.one/incident/768873 Tue, 18 Nov 2025 14:47:00 -0000 https://status.inex.one/incident/768873#5dad0b03586140971f346e236d0dcda883296411984c0ec695d0db8c21d04207 We're monitoring Cloudflare's recovery. Every service seems to be fully functional again https://status.inex.one/incident/768873 Tue, 18 Nov 2025 14:47:00 -0000 https://status.inex.one/incident/768873#5dad0b03586140971f346e236d0dcda883296411984c0ec695d0db8c21d04207 We're monitoring Cloudflare's recovery. Every service seems to be fully functional again https://status.inex.one/incident/768873 Tue, 18 Nov 2025 14:06:00 -0000 https://status.inex.one/incident/768873#be5326f63af1127147f5818a833a28ddb16da0c6f678adbb32c32a0cf01579b5 Our secondary URL, https://app.inexone.com, is fully functional. Any broken link your might have would work by replacing "app.inex.one" with "app.inexone.com" Cloudflare is still working on resolving the issue - https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 https://status.inex.one/incident/768873 Tue, 18 Nov 2025 14:06:00 -0000 https://status.inex.one/incident/768873#be5326f63af1127147f5818a833a28ddb16da0c6f678adbb32c32a0cf01579b5 Our secondary URL, https://app.inexone.com, is fully functional. Any broken link your might have would work by replacing "app.inex.one" with "app.inexone.com" Cloudflare is still working on resolving the issue - https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 https://status.inex.one/incident/768873 Tue, 18 Nov 2025 11:48:00 -0000 https://status.inex.one/incident/768873#6bde7fec2c95efbb9e261e802c5dfbf8e92af3b0d05a196e0d55214c4fc5b29a You can go to our secondary URL, https://app.inexone.com, to access the app One of our cloud providers, Cloudflare, is currently experiencing issues. We're closely monitoring the situation. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 https://status.inex.one/incident/768873 Tue, 18 Nov 2025 11:48:00 -0000 https://status.inex.one/incident/768873#6bde7fec2c95efbb9e261e802c5dfbf8e92af3b0d05a196e0d55214c4fc5b29a You can go to our secondary URL, https://app.inexone.com, to access the app One of our cloud providers, Cloudflare, is currently experiencing issues. We're closely monitoring the situation. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 https://status.inex.one/incident/767248 Mon, 17 Nov 2025 11:39:12 -0000 https://status.inex.one/incident/767248#24b48004f328a95c3cb4563a76ab3d7fac7b91efb77ea807a2d1b2f309d7e4cc Public app recovered. https://status.inex.one/incident/767248 Mon, 17 Nov 2025 11:35:47 -0000 https://status.inex.one/incident/767248#2d424670de1524171bef3a2049a9590700f9253d3a7abb0a402bbe177863d410 Public app went down. https://status.inex.one/incident/767248 Mon, 17 Nov 2025 11:20:06 -0000 https://status.inex.one/incident/767248#d9078fc710eb323356d71f7d5e4710911dd0059be3a3c5a59328cbd8160b0b0f Public app recovered. https://status.inex.one/incident/767248 Mon, 17 Nov 2025 11:16:23 -0000 https://status.inex.one/incident/767248#5aeb4276d51d0546b0dcbfe71cd900355a2c434db8833946a85da09f1fe86be7 Public app went down. https://status.inex.one/incident/767248 Mon, 17 Nov 2025 11:05:47 -0000 https://status.inex.one/incident/767248#fb24f51706e0b58c6feebce24984a58ba27b6f57f58d4baeb21fb3e2cdd2d9e6 Backend services recovered. https://status.inex.one/incident/767248 Mon, 17 Nov 2025 11:03:39 -0000 https://status.inex.one/incident/767248#35628b3ecf271d22b93f6c6855c790edcb037e48362ccbd95be02b3511a28b64 Backend services went down. https://status.inex.one/incident/758402 Wed, 05 Nov 2025 10:04:53 -0000 https://status.inex.one/incident/758402#910788aef4912c115a17d0ec826e2787843fd48cd5c8832358397907dd98df35 Backend services recovered. https://status.inex.one/incident/758402 Wed, 05 Nov 2025 10:00:47 -0000 https://status.inex.one/incident/758402#0d972a2dafdf264f0a2724861734d744d022b88106eee72c0ed938139183f3ca Backend services went down. https://status.inex.one/incident/757722 Tue, 04 Nov 2025 12:58:47 -0000 https://status.inex.one/incident/757722#4a9589f4eeecd5dc3b5fefcfc22cd4ad484df38dfded28f1c017806348899ed0 Backend services recovered. https://status.inex.one/incident/757722 Tue, 04 Nov 2025 12:54:41 -0000 https://status.inex.one/incident/757722#3ee8b962621cd3155ab38a2be914bea36492736822cbd041d0c40b95539bb407 Backend services went down. https://status.inex.one/incident/757033 Mon, 03 Nov 2025 16:13:44 -0000 https://status.inex.one/incident/757033#3c1dbf8c7e87e23446c6a7f93080a7dffd9f73cea4323982ef247bd8e327bcf7 Backend services recovered. https://status.inex.one/incident/757033 Mon, 03 Nov 2025 16:10:13 -0000 https://status.inex.one/incident/757033#f4e2f9e656f4f909a79bff2a0f4d8bdbcc9e4a787cc1df982447c703006bff5b Backend services went down. https://status.inex.one/incident/753605 Wed, 29 Oct 2025 15:11:32 -0000 https://status.inex.one/incident/753605#48beb9c9fcb643506cd152539e1e63e60e6f20487691db963632fa5956e8dc1c Backend services recovered. https://status.inex.one/incident/753605 Wed, 29 Oct 2025 15:03:13 -0000 https://status.inex.one/incident/753605#9259798e9f68c958f9600bcda7d4ea8adc975371eb111c7d773660a7291342b7 Backend services went down. https://status.inex.one/incident/753605 Wed, 29 Oct 2025 14:06:44 -0000 https://status.inex.one/incident/753605#2323a425a6135a1fce6d73d3879a19db898b697ae0d8429daede2eca3d5b314a Backend services recovered. https://status.inex.one/incident/753605 Wed, 29 Oct 2025 14:02:33 -0000 https://status.inex.one/incident/753605#64c2a07d4027f58b5b122cf3333eefc8494f295e11c47fd9fea8d7900822314a Backend services went down. https://status.inex.one/incident/746877 Mon, 20 Oct 2025 09:30:00 -0000 https://status.inex.one/incident/746877#66d6f1f5928025f780541da2a5411b083c9af180031462b5e27ba24a66e8ddf9 Every service is now recovered, we're still monitoring the situation https://status.inex.one/incident/746877 Mon, 20 Oct 2025 08:08:00 -0000 https://status.inex.one/incident/746877#3b2399f81adfd86dcd3d7e8ce6c87bcbe9402a18c4fb41ae1e097fe5fc6553f6 We are currently experiencing a service disruption affecting our authentication and live chat services. This is due to a widespread outage with our cloud provider, Amazon Web Services (AWS). Impacted Services: - Login/Authentication: You may be unable to log in. If you need immediate access, please email help@inex.one to receive a magic login link. - Live Chat: Our live chat support is currently unavailable. Please contact us at help@inex.one for assistance. Current Status: Our team is actively monitoring the situation with AWS and is ready to restore full functionality as soon as the underlying issue is resolved. We sincerely apologize for the inconvenience and appreciate your patience. We will post another update as soon as we have more information. https://status.inex.one/incident/716421 Mon, 01 Sep 2025 11:49:50 -0000 https://status.inex.one/incident/716421#d7d62b6c6276af0c1f350568894d418c02aa62d348b9899201d355b70460e1d4 Public app recovered. https://status.inex.one/incident/716421 Mon, 01 Sep 2025 11:46:22 -0000 https://status.inex.one/incident/716421#01085a60dd9879fd25c9307ade22cbbd7e21269e06481dfecc562393351bfcf6 Public app went down. https://status.inex.one/incident/715802 Sun, 31 Aug 2025 12:46:50 -0000 https://status.inex.one/incident/715802#8a85d4a7a0b508c22b5d4ef179bd33a641390a5e1ca3b57d189b227e142b102f Backend services recovered. https://status.inex.one/incident/715802 Sun, 31 Aug 2025 12:42:01 -0000 https://status.inex.one/incident/715802#6d3631d9cf0e2413fa28d31c8b1b68f5a9341c65e258eb62b5f887d9fd1b6e38 Backend services went down. https://status.inex.one/incident/699901 Mon, 04 Aug 2025 12:13:33 -0000 https://status.inex.one/incident/699901#8b4b29555694bec769c3867e5e20ed1dfd31f0d6fbf7f703c3beddd36357776f Backend services recovered. https://status.inex.one/incident/699901 Mon, 04 Aug 2025 12:10:02 -0000 https://status.inex.one/incident/699901#1c5912df5a93db96505d88f5e500518ff57147586b40a03d9c395a2f1c5ae827 Backend services went down. https://status.inex.one/incident/699901 Mon, 04 Aug 2025 12:07:18 -0000 https://status.inex.one/incident/699901#d04892a337a500e4ecc572aae67fee6c4ffd8110a7c62bca0664f5481c7ac7e9 Backend services recovered. https://status.inex.one/incident/699901 Mon, 04 Aug 2025 12:03:10 -0000 https://status.inex.one/incident/699901#0b92fbb72ae50a64bbe1e3598f4ec1fd2a6e645ba8646007d008bcbe48439063 Backend services went down. https://status.inex.one/incident/699901 Mon, 04 Aug 2025 10:44:23 -0000 https://status.inex.one/incident/699901#d66731b229ba7838e8d5089d6d05b7102e964bee6294e657f004c9a8f7f4594a Backend services recovered. https://status.inex.one/incident/699901 Mon, 04 Aug 2025 10:33:49 -0000 https://status.inex.one/incident/699901#f11c4103a65e811a4ea423e3c3c27f7ce0345fe52a86755097c5a377d14d5835 Backend services went down. https://status.inex.one/incident/699901 Mon, 04 Aug 2025 06:06:40 -0000 https://status.inex.one/incident/699901#288a4e40e706fb17d4296d6ca24ce6bb2755e5c51fa151e8ae887d7db1634ae3 Backend services recovered. https://status.inex.one/incident/699901 Mon, 04 Aug 2025 06:03:11 -0000 https://status.inex.one/incident/699901#4851c521c3579855e775308ac32646c7964646ca448b00c2aa3d1003c5b49984 Backend services went down. https://status.inex.one/incident/684435 Fri, 01 Aug 2025 06:09:05 -0000 https://status.inex.one/incident/684435#17261cc03b919179028f2cf6d1c8f25019be6f3e794f01b002fdfefcd7f47838 Backend services recovered. https://status.inex.one/incident/684435 Fri, 01 Aug 2025 06:08:44 -0000 https://status.inex.one/incident/684435#f6d7184c90f5dd8413c509eb3c1435a2c0edea74277c0ccc4bc128ddb3e2787e Backend services went down. https://status.inex.one/incident/684435 Fri, 01 Aug 2025 06:06:01 -0000 https://status.inex.one/incident/684435#bb7cd654d068e9a1adaaa3474a296ee8084d4f9cdcb58eb8417150eae80d1d9a Backend services recovered. https://status.inex.one/incident/684435 Fri, 01 Aug 2025 06:03:04 -0000 https://status.inex.one/incident/684435#73d4145d3387f272b2cdf5ccd036c60aeebbd7d37bf80d37fb0410d11336ffc9 Backend services went down. https://status.inex.one/incident/670669 Thu, 31 Jul 2025 13:04:32 -0000 https://status.inex.one/incident/670669#6af61cdeb3200468bc2ae24f382b811ad91462db451edfa1f212c621fe8f7d4a Backend services recovered. https://status.inex.one/incident/670669 Thu, 31 Jul 2025 13:01:55 -0000 https://status.inex.one/incident/670669#f38e247b540f8ccad91a8becd5fe49d7106e048b2553e90ba4f5b389e1a4f508 Backend services went down. https://status.inex.one/incident/626962 Mon, 28 Jul 2025 08:27:00 -0000 https://status.inex.one/incident/626962#ac4bf379921c0314bcff20c7dff7ec76cf0c142d270081cb05cee66fbe557b65 The issue with the upstream provider has been resolved. The Inex One platform should be working normally at this time. https://status.inex.one/incident/626962 Mon, 28 Jul 2025 08:27:00 -0000 https://status.inex.one/incident/626962#ac4bf379921c0314bcff20c7dff7ec76cf0c142d270081cb05cee66fbe557b65 The issue with the upstream provider has been resolved. The Inex One platform should be working normally at this time. https://status.inex.one/incident/626962 Mon, 28 Jul 2025 07:39:00 -0000 https://status.inex.one/incident/626962#2f5d2cabfd675b0db9c7cca1bb2be1f615dac79e27d290d32c80cdbc5d3f073c We're aware of an issue where users may experience errors when accessing the Inex One platform. This is due to an ongoing incident with one of our upstream providers. We're actively monitoring the situation and will provide updates when the issue is resolved. https://status.inex.one/incident/626962 Mon, 28 Jul 2025 07:39:00 -0000 https://status.inex.one/incident/626962#2f5d2cabfd675b0db9c7cca1bb2be1f615dac79e27d290d32c80cdbc5d3f073c We're aware of an issue where users may experience errors when accessing the Inex One platform. This is due to an ongoing incident with one of our upstream providers. We're actively monitoring the situation and will provide updates when the issue is resolved. https://status.inex.one/incident/609162 Wed, 25 Jun 2025 20:11:28 -0000 https://status.inex.one/incident/609162#12cfbeed34b5824db36b7d9b4293dddb96f5066c24ad4d8e7e6f40c3abc4317d Backend services recovered. https://status.inex.one/incident/609162 Wed, 25 Jun 2025 20:08:03 -0000 https://status.inex.one/incident/609162#ffc7e2cc3b05bfea14923d7363f752e7ceb8f6a26dab0999d43735f0f2c59e54 Backend services went down. https://status.inex.one/incident/527103 Wed, 12 Mar 2025 15:21:08 -0000 https://status.inex.one/incident/527103#3258988ae68a2f764670c557ef597b20cba8512523b5b0dbc8077b971763341b Backend services recovered. https://status.inex.one/incident/527103 Wed, 12 Mar 2025 15:18:27 -0000 https://status.inex.one/incident/527103#8d75e065fa6306bf127dd14f0488111215ef4d511f8d23be62368699bf608bd8 Backend services went down. https://status.inex.one/incident/517407 Sun, 23 Feb 2025 01:14:46 -0000 https://status.inex.one/incident/517407#1e0e9c1646f246ab0f8c8af01c925c3c95c9b99a9e18b2ec39e6481f43cebc55 Backend services recovered. https://status.inex.one/incident/517407 Sun, 23 Feb 2025 01:13:54 -0000 https://status.inex.one/incident/517407#215b7b684daeb98f24479b52fabc395a6e1abfbca46722f1bee4dd3e56802908 Backend services went down. https://status.inex.one/incident/517407 Sun, 23 Feb 2025 01:12:24 -0000 https://status.inex.one/incident/517407#2076a2ddde40005b5abb56cace04265186f3abd53f9f43d0469054d0c28dfff9 Backend services recovered. https://status.inex.one/incident/517407 Sun, 23 Feb 2025 01:12:08 -0000 https://status.inex.one/incident/517407#95ab4c5660ae68157af13f34245a5156faee2b34627ca16d71c4cef2f95ef9a2 Backend services went down. https://status.inex.one/incident/517407 Sun, 23 Feb 2025 01:08:19 -0000 https://status.inex.one/incident/517407#ae9841a813348d42e8b982517749b05b27b41824880b4c1da7128301cf53bb74 Backend services recovered. https://status.inex.one/incident/517407 Sun, 23 Feb 2025 00:56:25 -0000 https://status.inex.one/incident/517407#7c880a488e3a2d24ecc81f234f0db8de26d847f7ae779716c42677febd428ed2 Backend services went down. https://status.inex.one/incident/510697 Tue, 11 Feb 2025 00:11:25 -0000 https://status.inex.one/incident/510697#4a3a1a76311efe5907242839e1adf6c6250152de38c06550f33bc4f50f06f978 Backend services recovered. https://status.inex.one/incident/510697 Tue, 11 Feb 2025 00:06:16 -0000 https://status.inex.one/incident/510697#75f1dc7dcd7501e7ebdd0e81083fa62e7a63ae5dc700fa01cac0595b0980ec9b Backend services went down. https://status.inex.one/incident/506184 Mon, 03 Feb 2025 13:13:23 -0000 https://status.inex.one/incident/506184#1d1103b84ca3d51f53dc8947e1d2ed54a9e19edd6933eee8e3be8f54cd8d6824 Public app recovered. https://status.inex.one/incident/506184 Mon, 03 Feb 2025 13:07:05 -0000 https://status.inex.one/incident/506184#5cc855889b485b5e31e42bbe5158ce4aa2a33aad0db483c83020d5a12bde27cb Public app went down. https://status.inex.one/incident/506184 Mon, 03 Feb 2025 01:46:08 -0000 https://status.inex.one/incident/506184#533ef28a77319268db2dba8592f4e9c06ea37cae358245f6b4181bab27ba655a Backend services recovered. https://status.inex.one/incident/506184 Mon, 03 Feb 2025 01:34:38 -0000 https://status.inex.one/incident/506184#16770c08cfd3731189915e875bc742b1fa0e27b8ec9cf0a5c596c67852294c5d Backend services went down. https://status.inex.one/incident/506184 Mon, 03 Feb 2025 00:41:22 -0000 https://status.inex.one/incident/506184#212352aeb35399db90be2d70c4fb4cb57a89095aeb051577f9f6588f5b45ceba Backend services recovered. https://status.inex.one/incident/506184 Mon, 03 Feb 2025 00:37:52 -0000 https://status.inex.one/incident/506184#8c95fa8f71c30ef6cd6381846ee641cd1263fb7b38701a536751201df80e904f Backend services went down.