There were 116 CommandLink outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
CommandLink not working for you?
CommandLink not working for you?
Minor
: CommandLink Twilio MMS and Phone Numbers degraded, then restored
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 day, 21 hours and 30 minutes)
The incident began with Twilio MMS issues, later expanding to Twilio PHONE NUMBERS in addition to MMS. Users likely experienced messaging problems during this period, including MMS delivery and related number services. The outage lasted from to , a duration of approximately 45 hours and 30 minutes.
Minor
: CommandLink: Twilio PHONE NUMBERS degraded for about 19 hours
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(18 hours and 50 minutes)
CommandLink experienced degraded service with the Twilio PHONE NUMBERS component beginning when it was listed as degraded. This affected phone-number related features for users during the outage window.
The incident lasted about 18 hours and 50 minutes and was resolved when the Twilio PHONE NUMBERS component returned to normal at . CommandLink issued 2 status updates during the incident to communicate the degraded state and recovery progress. The disruption affected only the Twilio PHONE NUMBERS component.
CommandLink experienced degraded performance due to issues with the Cloudflare Network. The outage began at and was resolved by , lasting about 2 hours and 55 minutes. The Cloudflare Network component was listed as degraded during the event, with 2 official status updates documenting the degradation and its resolution.
Minor
: CommandLink Twilio PHONE NUMBERS issue during maintenance
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour)
During a scheduled maintenance window, CommandLink reported issues with Twilio PHONE NUMBERS, potentially affecting phone-number related features for users.
The maintenance window began at and was resolved by . The Twilio PHONE NUMBERS component moved from up to maintenance and back to up as the issue was addressed.
The incident involved two official status updates from CommandLink and appeared limited to the Twilio PHONE NUMBERS component with no broader impact reported.
CommandLink experienced a brief outage affecting Twilio Phone Numbers. The incident began at and was resolved by , lasting about 5 minutes. The Twilio Phone Numbers component was briefly degraded, impacting telephony functions, before service returned to normal. The provider issued two status updates during the incident.
An outage began at , when the Cloudflare Network went down and CommandLink users started experiencing connectivity issues. By , the Cloudflare Firewall was listed as degraded, and at the Cloudflare Network remained degraded. Later in the day, Twilio PHONE NUMBERS were added to the degraded list at , signaling broader impact on communications services that rely on these dependencies.
Recovery progressed as the Cloudflare Network and Cloudflare Firewall moved back to up at , while Twilio PHONE NUMBERS remained degraded. By , all components had recovered and returned to normal operation.
Overall, the incident lasted about 10 hours, with six official status updates documenting the progression across Cloudflare Network, Cloudflare Firewall, and Twilio PHONE NUMBERS. The disruption affected services relying on Cloudflare networking and telephony routing, indicating a major service impact for CommandLink.
Minor
: Twilio PSTN briefly degraded, then restored
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 35 minutes)
Twilio PSTN experienced a brief degradation in voice services. The issue began at and lasted about 2 hours and 35 minutes, with some users possibly experiencing failed or degraded calls. The PSTN service was restored by .
Twilio's status page indicated the problem with the message "Experiencing Issues with Twilio PSTN" and showed the Twilio PSTN component moving from up to warn and back to up. The provider issued two status updates during the incident, signaling the issue and its resolution.
CommandLink experienced a brief degradation due to issues with the Cloudflare Network. The outage began at and was resolved by , lasting about 45 minutes. The incident affected the Cloudflare Network component, with intermittent connectivity or slower responses possible during the window. The status page confirmed the Cloudflare Network returned to normal after the disruption and resolution.
Minor
: CommandLink Twilio PSTN briefly degraded, service restored
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(35 minutes)
CommandLink's Twilio PSTN component experienced a brief degradation in telephony services. Users may have encountered issues with PSTN calls during the incident. The outage began on and was resolved by , lasting about 35 minutes. The status page documented the issue and subsequent recovery, with two status updates issued during the event.
CommandLink experienced a brief degraded network affecting users as the Cloudflare Network showed issues on the status page. The incident began at and was resolved by , lasting about 50 minutes. The Cloudflare Network component moved from up to warn and back to up during the event. CommandLink published 2 official status updates describing the situation. The impact was limited to network connectivity through the Cloudflare edge network, with some users potentially seeing intermittent access or slower performance during the window.
