CommandLink outage history

CommandLink experienced a brief degraded performance affecting the Twilio PHONE NUMBERS component. Users relying on phone-number features may have experienced intermittent issues. The incident began at 7:33 PM UTC and was resolved by 11:34 PM UTC, lasting about four hours.

CommandLink faced a period of degraded performance beginning 1:13 AM UTC as the Cloudflare Network entered a degraded state. The impact persisted for about three days, with users likely experiencing slower responses and intermittent connectivity across CommandLink services. The Cloudflare network returned to a healthy state and CommandLink resumed full operation when the status was updated to up at 1:53 AM UTC.

CommandLink experienced a brief maintenance window affecting Twilio Origination, Twilio Termination, and Twilio PSTN. The maintenance began at 1:03 PM UTC and completed at 2:33 PM UTC, with the three components returned to the up state afterward. Users may have seen intermittent issues with voice origination and termination during this interval, though no broader outages were reported.

CommandLink experienced degraded performance due to a Cloudflare Network issue. The status page progressed from up to warn at 2:14 PM UTC, with users likely encountering slower responses or intermittent connectivity while the Cloudflare service was affected. The issue was resolved as the Cloudflare Network returned to up at 12:08 AM UTC.

The Twilio MMS component on CommandLink experienced degraded performance starting at Feb 16, 2026 6:13 PM UTC and returning to normal at Feb 17, 2026 8:28 AM UTC. During this window, MMS messaging could have been delayed or intermittently unreliable for some users.

The incident involved a single component (Twilio MMS) and was tracked with two official status updates, showing a transition from up to degraded (warn) and back to up. The outage duration spanned from Feb 16, 2026 6:13 PM UTC to Feb 17, 2026 8:28 AM UTC with recovery confirmed by the status page.

CommandLink experienced a brief degradation in the ITSM Platform, causing slowness on some pages for users. The issue was acknowledged at 6:44 PM UTC with ongoing investigations, and the service returned to normal by 7:23 PM UTC after two status updates were issued. The incident lasted about 39 minutes and affected only the ITSM Platform component.

CommandLink experienced a brief degradation in the Cloudflare Firewall component. The issue began at Feb 10, 2026 6:48 PM UTC and was resolved at Feb 10, 2026 7:53 PM UTC, lasting about 1 hour and 5 minutes. The status page indicated the Cloudflare Firewall moved from operational to degraded before returning to normal, with users potentially experiencing intermittent filtering or access issues during the window. The incident was contained to this component, and services returned to full operation after the recovery.

CommandLink experienced a brief degradation in the Cloudflare Firewall component, resulting in a short window of degraded protection and performance. The incident began at 6:34 PM UTC and was resolved by 6:44 PM UTC, lasting about 10 minutes. The status page showed the Cloudflare Firewall transitioning from up to degraded (warn) and back to up once the issue was resolved, with the impact limited to this component.

CommandLink conducted a planned maintenance window for the Twilio MMS component. The window lasted approximately 6 hours, beginning at 4:48 AM UTC and ending at 10:48 AM UTC UTC. During this period, MMS delivery may have been unavailable or degraded while the component was undergoing maintenance.

The CommandLink status page showed the Twilio MMS component transitioning from up to maintenance at the start of the window and returning to up after maintenance concluded, with the service restored once the maintenance completed.

CommandLink experienced a degradation affecting Twilio PHONE NUMBERS, impacting users who rely on those numbers for calls and messaging. The incident began when Twilio PHONE NUMBERS entered a degraded state at Jan 28, 2026 6:03 PM UTC and was resolved by Jan 30, 2026 12:18 AM UTC, lasting roughly 30 hours and 15 minutes. The status page documented the issue and subsequent recovery, with two updates issued during the incident and restoration of normal operation thereafter.