Incidents reported on status page for FleetWorks https://status.fleetworks.ai/ en https://status.fleetworks.ai/incident/928228 Thu, 18 Jun 2026 23:57:00 -0000 https://status.fleetworks.ai/incident/928228#072d4dd9d534f3fea58aa483a9f9f757bf1f7f0493eb1dcdfff555515d2eefc4 Our vendor has rolled back a configuration change and we are noticing calls reaching our agent in a healthy manner. Apologies for the disruption https://status.fleetworks.ai/incident/928228 Thu, 18 Jun 2026 22:00:00 -0000 https://status.fleetworks.ai/incident/928228#706cd4931c5388907115c0b9114f3fc13b085f9357663762441ad68a1202a34a We have observed calls not being picked up by our systems, caused by a provider configuration change. We have escalated it as P0 and are working with them to restore service https://status.fleetworks.ai/ Thu, 11 Jun 2026 12:14:50 +0000 https://status.fleetworks.ai/#f5a32ac13a3e32534f232d4d5eecb8efe51b72bf5c7a38444a30930a9d95099e API recovered https://status.fleetworks.ai/ Thu, 11 Jun 2026 12:12:40 +0000 https://status.fleetworks.ai/#f5a32ac13a3e32534f232d4d5eecb8efe51b72bf5c7a38444a30930a9d95099e API went down https://status.fleetworks.ai/incident/901980 Thu, 21 May 2026 18:46:00 -0000 https://status.fleetworks.ai/incident/901980#7645baa44b169c8530c1f4bcc9b8a2541811ee820d7b172330e98f3f586a347b Normal call service has been restored, and the issue has been resolved. We will continue monitoring to ensure the service remains stable. https://status.fleetworks.ai/incident/901980 Thu, 21 May 2026 18:32:00 -0000 https://status.fleetworks.ai/incident/901980#746e8b83e0fa5005158db203cf46f467e741740d4b850b30ad8b6ec0755bc602 We have restored normal call routing and are closely monitoring performance to ensure the service remains stable. https://status.fleetworks.ai/incident/901980 Thu, 21 May 2026 17:56:00 -0000 https://status.fleetworks.ai/incident/901980#78123a4e016879b9672a0cecb7c1de539faef5a0fc4a9c45b4083588827f7453 Affected inbound calls continue to be redirected to fallback numbers while we work to restore normal call routing. We will provide another update as soon as more information is available. https://status.fleetworks.ai/incident/901980 Thu, 21 May 2026 16:36:00 -0000 https://status.fleetworks.ai/incident/901980#8e3ea293d3d6e0dedcc7e77af8d162e5b4ef107a8db6877f57bc1784cfb2c4ad We are now redirecting calls directly to fallback numbers while our team continues working to resolve the issue, which stems from a third party vendor. We’ll share additional updates as more information becomes available. https://status.fleetworks.ai/incident/901980 Thu, 21 May 2026 15:00:00 -0000 https://status.fleetworks.ai/incident/901980#060ae709a5c590a71698b770690e4254ab9956d26e2458b47851ce0d2f2722dc We’re currently experiencing degraded call performance, with the AI not responding as expected. Our team is actively investigating and working to resolve the issue. We’ll share updates as more information becomes available. https://status.fleetworks.ai/incident/894216 Tue, 12 May 2026 17:01:00 -0000 https://status.fleetworks.ai/incident/894216#a3990e9a241808bed28803fcff56699d3d149bb54c5f5ada0ee30f84c3467616 Provider has rolled back a bad deployment and we are seeing metrics return to healthy. We will keep monitoring https://status.fleetworks.ai/incident/894216 Tue, 12 May 2026 16:10:00 -0000 https://status.fleetworks.ai/incident/894216#3de0852e332714360956096e1d69954f64c224b97ccf5b917d2f6c7f3cd3eb1e We've noticed a subset of calls failing to initialize due to a provider failure and are currently investigating https://status.fleetworks.ai/incident/880736 Mon, 27 Apr 2026 07:45:00 -0000 https://status.fleetworks.ai/incident/880736#4fd187f3b28a32eded619770cd5d30826d90067f632c6dd69ac92aa85deca291 The load updates endpoints were temporarily unavailable for approximately one hour. All events during the affected window have since been replayed successfully, so there is no impact to loads data — everything is fully up to date. https://status.fleetworks.ai/incident/873136 Thu, 16 Apr 2026 16:24:00 -0000 https://status.fleetworks.ai/incident/873136#593cd2c1c48d528cf1b9566208c562e935960f4c16c1739750a93cce38ab13ca AI-agent call routing has been restored and the global bypass has been disabled. Call performance has returned to normal levels, with provider latency and error rates significantly improved. We are continuing to monitor the restored AI-agent path before closing this incident. https://status.fleetworks.ai/incident/873136 Thu, 16 Apr 2026 14:54:00 -0000 https://status.fleetworks.ai/incident/873136#46ee4f3c5e3d803b58afcbfb6e732e2d686f34fecbf36b156a4280913c901e54 We are seeing elevated errors from one of our providers, and have performed a global kill switch to bypass our AI agent and direct calls directly to dedicated forwarding numbers at 9:55AM CT https://status.fleetworks.ai/incident/873136 Thu, 16 Apr 2026 14:47:00 -0000 https://status.fleetworks.ai/incident/873136#22b58ac764d6c7ada25cec402c7cb5eb33c80455bcc73251a96b29178d0c10ed We are currently experiencing degraded call performance where the AI is not responding. Our team is actively investigating and working to resolve the problem. We will provide updates as more information becomes available.