Is Alvys Down?

On November 11, 2026, from 12:05 PM to 12:50 PM PT (3:05 to 3:50 PM ET, 20:05 to 20:50 UTC), Alvys was unavailable to all customers. During this window, our application services could not keep reliable connections to our primary database. Network latency stopped secure connections (TLS handshakes) between our services and the database from completing. Our cloud provider has confirmed that a configuration change they deployed to part of their database infrastructure in the Central US region caused the issue. The change has been rolled back, and service is fully restored. Our database and the data stored in it were not affected. Customer impact - Alvys web and mobile apps: pages failed to load, and users could not view or save data. - Public API: requests failed or timed out. - EDI: inbound EDI processing stopped during the outage (details below). - Inbound webhooks: webhooks sent to Alvys by integration partners during the outage were not processed. - Background processing: settlements, accounting reports and scheduled jobs were delayed, and resumed once service was restored. EDI impact AS2: Inbound AS2 transmissions to Alvys failed from 12:05 PM to 12:47 PM PT (3:05 to 3:47 PM ET). Tenders and updates sent over AS2 in this window were not received. We have notified affected customers directly. We asked them to have their trading partners resend any AS2 transactions from this window that were not retried automatically. SFTP: Files that waited on trading partners’ servers during the outage were picked up automatically once service was restored. No action is needed for these. A small number of SFTP tender files failed to import while service was recovering. We are re-importing them on customers’ behalf. Tender board: fully recovered by 12:50 PM PT. Tenders are flowing normally. We apologize for the disruption to your operations. If you have questions, contact support@alvys.com or your account manager. --- [2026-11-11T22:16:24.518Z] (monitoring) We have initiated a failover, and traffic is recovering; we are still monitoring. We will continue to share updates as soon as they become available. --- [2026-11-11T20:42:02.940Z] (identified) We have identified the issue related to network connectivity in the central US and are working on remediation. We will continue to share updates as soon as they become available. --- [2026-11-11T20:36:47.655Z] (investigating) Alvys has detected a service degradation affecting Web/Mobile for some users. Our engineers are currently investigating the issue to determine the impact and root cause. We will provide updates as soon as more information becomes available. --- [2026-11-11T22:15:52.171Z] (investigating) We are aware of a service outage affecting all Alvys customers and our engineering team is actively investigating.

This incident has been resolved. --- [2026-10-27T13:32:35.694Z] (investigating) We're aware that some users can't open app.alvys.com from their office network. The page times out, and the browser shows an "ERR_TIMED_OUT" or "ERR_EMPTY_RESPONSE" error. Users can still reach Alvys from phones and from other networks. This matches an ongoing issue our provider, Cloudflare, is working on: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew. According to Cloudflare, the problem happens when some third-party office firewalls inspect web traffic, mostly after a recent firmware update. If you're affected: - Use Alvys from a phone or a mobile hotspot for now. - Ask your IT team or firewall vendor about the Cloudflare issue, or have them exclude app.alvys.com from HTTPS/SSL inspection. - Contact Alvys Support if you need help. Your office's public IP address and firewall brand help us look into it faster. We're following Cloudflare's progress and will post an update as soon as we have more information.

On October 19, 2026, from 3:49 to 3:53 PM ET (19:49–19:53 UTC), some actions in Alvys failed with an error instead of loading. The Load Board and Dispatch Planner were affected most. Some mobile app actions also failed, including location updates, arrival and departure check-ins, and document uploads, as did a small number of incoming EDI and integration messages. The errors were caused by a temporary slowdown in network traffic reaching our servers. It cleared on its own, and we have not seen any errors since. Some automated actions that failed were retried and completed automatically. If you tried an action during this window and it failed, retrying it now should work. We recommend checking that any mobile check-ins or document uploads submitted during this time were recorded.