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/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.