Incidents reported on status page for OmniRoute https://status.omniroute.cloud/ https://d1lppblt9t2x15.cloudfront.net/logos/66562633a8e53bba632d9ea097490bac.png https://status.omniroute.cloud/ en https://status.omniroute.cloud/ Thu, 28 May 2026 18:43:29 +0000 https://status.omniroute.cloud/#aa37549bf4ccf007617193c71b4f3199b52b32f26b9229c67bc7c610191b8cb5 WEB recovered https://status.omniroute.cloud/ Thu, 28 May 2026 18:34:29 +0000 https://status.omniroute.cloud/#aa37549bf4ccf007617193c71b4f3199b52b32f26b9229c67bc7c610191b8cb5 WEB went down https://status.omniroute.cloud/ Thu, 28 May 2026 18:10:41 +0000 https://status.omniroute.cloud/#8808d3a91038b3b58e838fb4f877620f36fdd63af24847642f4d3b36c0955486 WEB recovered https://status.omniroute.cloud/ Thu, 28 May 2026 18:07:28 +0000 https://status.omniroute.cloud/#8808d3a91038b3b58e838fb4f877620f36fdd63af24847642f4d3b36c0955486 WEB went down https://status.omniroute.cloud/ Wed, 27 May 2026 17:40:28 +0000 https://status.omniroute.cloud/#a38f65178eec7e38a4865efe6978b6d1750a9138c5e25f0d2f16f8d28bbd4d23 WEB recovered https://status.omniroute.cloud/ Wed, 27 May 2026 17:22:28 +0000 https://status.omniroute.cloud/#a38f65178eec7e38a4865efe6978b6d1750a9138c5e25f0d2f16f8d28bbd4d23 WEB went down https://status.omniroute.cloud/incident/895363 Wed, 13 May 2026 21:31:27 -0000 https://status.omniroute.cloud/incident/895363#2eff10a2bd11f19aec5b665910ad83cd98803753eeeb1c4131480882423ee3a2 Maintenance completed https://status.omniroute.cloud/ Wed, 13 May 2026 21:10:42 +0000 https://status.omniroute.cloud/#a9d616292fdbff955e6ef796f4fdc17ab283004b7cea7d53d592866e07ff4e26 WEB recovered https://status.omniroute.cloud/ Wed, 13 May 2026 21:07:26 +0000 https://status.omniroute.cloud/#a9d616292fdbff955e6ef796f4fdc17ab283004b7cea7d53d592866e07ff4e26 WEB went down https://status.omniroute.cloud/incident/895363 Wed, 13 May 2026 20:00:26 -0000 https://status.omniroute.cloud/incident/895363#643add733b61b0740e08cf0eb85a5cbd207b03da6595078999f906cb0ab6022c We are performing an infrastructure update on the OmniRoute API server. During this time the platform may be temporarily unavailable or operating with limited functionality. What to expect: • The web panel may be unresponsive or show login errors • The desktop app may have trouble submitting routes — they will be saved locally and submitted automatically once the connection is restored • Stats and rankings may be temporarily outdated We are working to restore full service as quickly as possible. Thank you for your patience. https://status.omniroute.cloud/ Fri, 08 May 2026 09:46:47 +0000 https://status.omniroute.cloud/#c958cf29c1adf0302da1cd2bc767ece6b5c3ac51f3a0f6b3abc751225d2c3da7 WEB recovered https://status.omniroute.cloud/ Fri, 08 May 2026 06:34:31 +0000 https://status.omniroute.cloud/#c958cf29c1adf0302da1cd2bc767ece6b5c3ac51f3a0f6b3abc751225d2c3da7 WEB went down https://status.omniroute.cloud/ Tue, 05 May 2026 19:49:38 +0000 https://status.omniroute.cloud/#38ac8b0d2992a1a2935a77d329f66477a4c23c6737de7532bc753fabd7a02149 WEB recovered https://status.omniroute.cloud/ Tue, 05 May 2026 19:40:40 +0000 https://status.omniroute.cloud/#38ac8b0d2992a1a2935a77d329f66477a4c23c6737de7532bc753fabd7a02149 WEB went down https://status.omniroute.cloud/ Wed, 22 Apr 2026 23:04:33 +0000 https://status.omniroute.cloud/#641267041dc2c02e1a14f787f64df9756fda02c7f55283802dc594de8daa3e7b WEB recovered https://status.omniroute.cloud/ Wed, 22 Apr 2026 23:01:36 +0000 https://status.omniroute.cloud/#641267041dc2c02e1a14f787f64df9756fda02c7f55283802dc594de8daa3e7b WEB went down https://status.omniroute.cloud/ Sat, 04 Apr 2026 10:51:18 +0000 https://status.omniroute.cloud/#48de32e36fa9c069750582b7dae179a01e6110d514da72992edd016610bd1ca3 WEB recovered https://status.omniroute.cloud/ Sat, 04 Apr 2026 10:17:17 +0000 https://status.omniroute.cloud/#48de32e36fa9c069750582b7dae179a01e6110d514da72992edd016610bd1ca3 WEB went down https://status.omniroute.cloud/incident/864622 Fri, 03 Apr 2026 20:03:00 -0000 https://status.omniroute.cloud/incident/864622#5a4bfcd844b8776e667db8983e43e02740f95d81f68b5fedb9c849f3a104c154 After infrastructure changes on 2026-04-03, the web service became completely unavailable. Users were either redirected to localhost:3000/pl or received a 500 Internal Server Error. Root cause: Next.js 14 standalone was running behind Cloudflare Tunnel without Nginx as an intermediate proxy. Next.js internally builds request URLs using its own fetchHostname:port (127.0.0.1:3000) instead of the public Host header, causing next-intl middleware to generate redirects and rewrites targeting https://localhost:3000 — which then triggered EPROTO SSL errors as Next.js tried to proxy requests to its own plain HTTP port over TLS. Resolution: Nginx was introduced between Cloudflare Tunnel and Next.js to properly forward X-Forwarded-Host and X-Forwarded-Proto headers. Cloudflare Tunnel routes were updated to point to Nginx (ports 8080/8081). Post-build patches were added to deploy.sh to fix Next.js 14 internal URL construction in next-server.js. Total downtime: ~14h 46m (2026-04-03 22:03 – 2026-04-04 12:49)