Incidents reported on status page for Callshift https://status.callshift.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/8ac82b5f16f18f5afa62294e4dd7508f.png https://status.callshift.ai/ en https://status.callshift.ai/incident/1052227 Sat, 05 Sep 2026 15:23:00 -0000 https://status.callshift.ai/incident/1052227#d97d53856e68efb74e646a6afc1ec78b4a6d38f7bb89b9cb4cc754c6cc658542 Resolved. The carrier has lifted the restrictions. Calls, SMS, and phone number purchasing on affected numbers are back to normal. If you paused a campaign, you can resume it now. Contacts marked as errored during the incident were not reached and need to be retried; those calls were not queued and did not go out later. The carrier's security review is closed. No Callshift system and no customer data were accessed at any point. https://status.callshift.ai/incident/1052227 Sat, 05 Sep 2026 09:30:00 -0000 https://status.callshift.ai/incident/1052227#2b7a03c657da01db9ac4809447997285b8f6d76d5b787b4b2f0e6be70350cc53 One of our upstream telephony carriers has applied precautionary restrictions to the Callshift platform account following an automated security review on their side. While those restrictions are in place, the following are affected: - Inbound and outbound calls on phone numbers Callshift provisioned for you through this carrier - Purchasing or searching for new phone numbers from that carrier in the dashboard - SMS notifications sent from the shared Callshift number **Not affected:** - Customers who have connected their own carrier account under Applications: your calls and messages continue to run on your own credentials - Numbers provisioned through our other carrier - The dashboard, public API, campaign configuration, and your contact data We have opened the carrier's account review process and are engaged with their support team. In parallel we are preparing to move affected numbers to an alternate carrier so calling can resume before the review completes. If you have a campaign running on an affected number, we recommend pausing it: calls that fail to launch are marked as errored against the contact, so a running campaign will work through your list without reaching anyone. We have no evidence that Callshift systems or customer data were accessed. If that changes, we will say so here and contact affected customers directly. https://status.callshift.ai/incident/873772 Wed, 15 Apr 2026 08:15:00 -0000 https://status.callshift.ai/incident/873772#85e3ada9c0f9719acb6e1bfaa93ae35f56dba5576db6e4d0b57aa4e7af278284 Apr 15, 2026 — 12:15 PM UTC — Investigating We identified that approximately 25% of incoming calls were failing to start. The issue was traced to delays in our event processing pipeline caused by a degradation at our infrastructure provider Inngest. Apr 15, 2026 — ~6:36 PM UTC — Partial recovery Call start reliability began improving as our provider resolved the primary function scheduling delays. Some residual latency remained. Apr 15, 2026 — 11:21 PM UTC — Resolved Full service restored. Our provider confirmed complete resolution of the underlying infrastructure issue. All calls are processing normally. https://status.callshift.ai/incident/859070 Fri, 27 Mar 2026 14:15:00 -0000 https://status.callshift.ai/incident/859070#1fcc9874c8aaf30a06493d66275df5b9a013cff14385f9a21c167404d8ffac85 We experienced a service disruption affecting call transcription functionality. The root cause was an exhausted resource on one of our Deepgram provider account, which caused transcription requests to fail. The issue has been resolved. All services are now operating normally. Impact: calls for all agents using Deepgram STT provider failed to connect. Duration: 15:15 – 16:00 https://status.callshift.ai/incident/769144 Tue, 18 Nov 2025 14:37:00 -0000 https://status.callshift.ai/incident/769144#8c1e8c06055a4a1478e302a757523de281b44c0b091c82435dbf946aca33bdb9 A fix has been implemented on cloudflare and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal. https://status.callshift.ai/incident/769144 Tue, 18 Nov 2025 12:11:00 -0000 https://status.callshift.ai/incident/769144#d8f40b463554aa4858aa726b48daf3285614a476cb9a9bc66eafdd0ba9896c92 Our service is affected by an ongoing Cloudflare network incident affecting reachability across Cloudflare's global network. Cloudflare is actively investigating the issue. Our team is monitoring the situation and prepared to restore service immediately once the upstream issue is resolved. In addition to our incident updates, you can follow Cloudflare's at: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We will provide updates as more information becomes available. https://status.callshift.ai/incident/747216 Mon, 20 Oct 2025 09:24:00 -0000 https://status.callshift.ai/incident/747216#e762f283f32acd4952a174c8b102346318e5058f1fa3f757c76f5ea38e0fcc4a Callshift API is currently unavailable due to AWS global outage. No calls can be passed or received on the platform. https://status.callshift.ai/incident/740111 Tue, 07 Oct 2025 10:10:00 -0000 https://status.callshift.ai/incident/740111#75fce3aa27193b1295a632e697f954b98b645b9c1f133b5e5dd5c397479d567c Issue corrected. We will continue to monitor. https://status.callshift.ai/incident/740111 Tue, 07 Oct 2025 10:08:00 -0000 https://status.callshift.ai/incident/740111#a7644f8427136f061e400aae6e257d92ddc775265d9cc6ad1e875cf51c8a3404 Some calls are missing transcripts, summary and recording.