CommandLink Outage History

CommandLink experienced issues with the Cloudflare Firewall beginning at Nov 7, 2025 12:13 AM UTC, resulting in degraded firewall protection and related service impact for an extended period. The incident affected the Cloudflare Firewall component across the platform, with users potentially experiencing intermittent protection failures until restoration. The provider posted two status updates during the event, first noting degraded firewall conditions and later confirming restoration. The outage was resolved by Nov 7, 2025 5:13 PM UTC after roughly 17 hours of impact.

CommandLink experienced a Cloudflare Firewall issue leading to degraded firewall functionality for a period. The Cloudflare Firewall component entered a degraded state and subsequently returned to normal. The incident began on Nov 6, 2025 11:23 AM UTC and was resolved by Nov 6, 2025 3:13 PM UTC, lasting about 3 hours and 50 minutes. The status page recorded 2 official updates during the outage.

CommandLink experienced a brief degradation caused by issues with the Cloudflare Network, affecting connectivity and performance for users relying on Cloudflare routing. The incident impacted a single component (Cloudflare Network) and lasted about 2 hours and 26 minutes, from 12:53 PM UTC to 3:19 PM UTC.

CommandLink communicated via the status page, posting two updates during the incident: the first at 12:53 PM UTC acknowledging the problem, and a follow-up at 3:19 PM UTC confirming restoration.

CommandLink's ITSM Platform experienced degraded performance beginning on Oct 30, 2025 4:23 PM UTC due to failures at an underlying provider. In response, CommandLink activated failover plans to keep services running, which helped maintain operation though some users may have experienced slower responses or intermittent access.

The incident prompted two official status updates: the first noted degraded performance on Oct 30, 2025 4:23 PM UTC; the second confirmed restoration to full service on Nov 1, 2025 6:08 PM UTC. The outage lasted from Oct 30, 2025 4:23 PM UTC to Nov 1, 2025 6:08 PM UTC, roughly 2 days and 1 hour.

CommandLink experienced a brief degradation in the Twilio PHONE NUMBERS component. Users, including those in the United States, reported a host-down condition during the incident. The issue began at Oct 29, 2025 8:03 PM UTC and was resolved by Oct 29, 2025 8:43 PM UTC, lasting about 40 minutes. CommandLink issued 2 status updates during the incident, acknowledging the degraded service and confirming restoration. The impact was limited to the Twilio PHONE NUMBERS functionality and did not appear to affect other CommandLink services.

CommandLink experienced a brief degradation in Twilio PSTN services, affecting voice connectivity for users relying on PSTN dialing. The incident began at 6:03 PM UTC and was resolved by 6:53 PM UTC, lasting roughly 50 minutes. The Twilio PSTN component transitioned from Up to Degraded (warn) and back to Up, with two official status updates documenting the degradation and subsequent recovery.

CommandLink experienced a brief partial outage affecting its Twilio telephony services. Twilio PHONE NUMBERS entered a degraded state starting at 1:33 PM UTC, followed by Twilio PSTN entering a degraded state at 1:43 PM UTC. The issue impacted voice connectivity and number routing for a subset of users, and the PSTN service remained degraded until 8:58 PM UTC.

CommandLink experienced a brief degradation in the Twilio PSTN telephony path, resulting in intermittent call issues for some users. The incident was identified on CommandLink's status page as Experiencing Issues with Twilio PSTN and appeared isolated to the Twilio PSTN component, with no broader platform impact reported. The outage began at Oct 20, 2025 9:18 PM UTC and was resolved by Oct 20, 2025 10:23 PM UTC, lasting about 1 hour and 5 minutes. The provider issued two status updates during the incident, detailing the degraded state and restoration.

CommandLink users experienced intermittent issues across Twilio-powered telephony services, including Twilio Origination, Twilio Termination, Twilio PSTN, Twilio PHONE NUMBERS, and Twilio MMS. The outage began at 8:13 AM UTC and was resolved by 8:18 PM UTC. Throughout the incident, the CommandLink status page issued updates as the situation evolved, with several components moving between degraded and partially restored states before a full recovery.

Overall, the issue affected 5 Twilio components and saw multiple updates from the provider to communicate progress. Voice calls and messaging could be impacted for users relying on Twilio for origination, termination, PSTN, phone numbers, and MMS, with recovery occurring gradually as components returned to normal.

CommandLink experienced a brief degradation in the Twilio PHONE NUMBERS component, impacting the ability to use those numbers for messaging and calling tasks. The outage began at 12:28 AM UTC and was resolved by 1:18 AM UTC, lasting about 50 minutes. The incident was noted on CommandLink's status page as 'Experiencing Issues with Twilio PHONE NUMBERS', followed by restoration updates.

During the event, CommandLink posted 2 status updates describing the disruption and its resolution. The impact was contained to the Twilio PHONE NUMBERS component and did not indicate broader service degradation.