CommandLink Outage History

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.

The Twilio PHONE NUMBERS component on CommandLink experienced a degradation starting at 6:53 AM UTC and ending at 6:13 PM UTC UTC, lasting 11 hours and 20 minutes. The status page listed the issue as "Experiencing Issues with Twilio PHONE NUMBERS," which could have affected calling and messaging routed through those numbers.

The incident involved two official status updates as CommandLink moved the component from up to warn and back to up, indicating the issue was resolved by 6:13 PM UTC.

The CommandLink status page reported a degraded experience for the Twilio PHONE NUMBERS component beginning on Jan 26, 2026 10:33 AM UTC after the component transitioned from up to warn. The issue affected Twilio PHONE NUMBERS, impacting calling and messaging routing for users relying on that feature. The provider posted an update noting 'Experiencing Issues with Twilio PHONE NUMBERS' and the service remained degraded until Jan 27, 2026 6:13 AM UTC when the component returned to up. The outage lasted approximately 19 hours and 40 minutes and was localized to this component with no broader impact reported.

CommandLink encountered degraded performance caused by issues with the Cloudflare Network, likely affecting services that rely on Cloudflare. Users may have experienced slower responses or intermittent connectivity during the incident. The outage began on 9:03 PM UTC and was resolved by 9:53 PM UTC, lasting about 50 minutes. The CommandLink status page tracked the issue as a Cloudflare Network incident, with updates published as the situation evolved.

CommandLink experienced a brief degradation in connectivity due to issues with the Cloudflare Network. Users may have observed intermittent connectivity and reduced performance as traffic traversed the Cloudflare network. The incident began at 10:23 AM UTC and was resolved by 12:13 PM UTC, lasting about 1 hour and 50 minutes. The provider published 2 status updates during the event, noting Cloudflare Network issues and the subsequent recovery. The issue affected the Cloudflare Network component, causing partial disruption for services that rely on Cloudflare.