Is Ciptex down?
Last checked just now2 components affected: Twilio SMS, Twilio Conversations
Ciptex is reporting degraded performance right now (last checked just now). Services are up but slower or partially failing.
Real-time Ciptex status, recent outages, and incident history — pulled directly from Ciptex's official status page at https://status.ciptex.com every 5 minutes. Pingoru tracks 102 Ciptex services and has captured 48 incidents in the last 90 days (99.18% uptime). Get email, Slack, Discord, or webhook alerts the moment Ciptex reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Twilio SMS
Timeline · 3 updates
- investigating · Jun 12, 2026, 02:32 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
- investigating · Jun 12, 2026, 02:34 PM UTC
Twilio are experiencing delivery delays and failures when sending messages from WhatsApp and Messenger platform. Twilio engineers are working with their carrier partner to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.
- resolved · Jun 12, 2026, 08:41 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Latest: Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
-
-
Timeline · 2 updates
- investigating · Jun 11, 2026, 08:38 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
- resolved · Jun 12, 2026, 01:34 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Latest: Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
-
- Race ESign
Timeline · 3 updates
- investigating · Jun 10, 2026, 07:57 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
- investigating · Jun 10, 2026, 08:09 AM UTC
Since 7:31 AM (UTC), we have been experiencing degraded performance affecting both the Race ESign application and the API v3. The main impact is increased latency in the execution of our processes. The Yousign engineering team is actively investigating to assess the full scope of the impact and identify the root cause. We will provide a further update as soon as we have more information.
- resolved · Jun 10, 2026, 08:12 AM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Latest: Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
-
- Twilio Recordings
Timeline · 3 updates
- investigating · Jun 10, 2026, 03:39 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
- monitoring · Jun 10, 2026, 03:46 AM UTC
Twilio are currently monitoring possible issues affecting voice calls. Customers could experience degradation during that time.Twilio will continue to monitor for system stability. We will provide another update ins 2 hours or soon as more information becomes available.
- resolved · Jun 10, 2026, 04:26 AM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Latest: Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
-
- Twilio Go RoomsTwilio CompositionsTwilio RecordingsTwilio Peer-to-Peer RoomsTwilio Group Rooms
Timeline · 4 updates
- investigating · Jun 06, 2026, 02:03 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
- investigating · Jun 06, 2026, 02:08 AM UTC
Twilio are currently investigating issues with video room sessions. Customers could experience high latency when connecting to video room. We will provide another update in 1 hour or as soon as more information becomes available.
- monitoring · Jun 06, 2026, 02:48 AM UTC
Twilio are observing recovery on the latency issue with video room sessions. They will continue monitoring the service to ensure a full recovery. We will provide another update in 2 hours or as soon as more information becomes available.
- resolved · Jun 06, 2026, 04:39 AM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Latest: Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
-
See the full Ciptex outage history
43 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Ciptex outage history →Or sign up free to get alerts when Ciptex breaks · 10 free monitors · No credit card
- Started Jun 12, 2026, 02:32 PM UTC · Resolved Jun 12, 2026, 08:41 PM UTC · 6h 9m
- Started Jun 11, 2026, 08:38 PM UTC · Resolved Jun 12, 2026, 01:34 PM UTC · 16h 56m
- Started Jun 10, 2026, 07:57 AM UTC · Resolved Jun 10, 2026, 08:12 AM UTC · 14m
- Twilio - Degradation on Voice calls ResolvedStarted Jun 10, 2026, 03:39 AM UTC · Resolved Jun 10, 2026, 04:26 AM UTC · 46m
- Started Jun 06, 2026, 02:03 AM UTC · Resolved Jun 06, 2026, 04:39 AM UTC · 2h 36m
- Started Jun 04, 2026, 08:24 PM UTC · Resolved Jun 04, 2026, 08:47 PM UTC · 23m
- Started Jun 02, 2026, 03:05 PM UTC · Resolved Jun 02, 2026, 03:31 PM UTC · 26m
- Investigating a Potential Issue ResolvedStarted May 29, 2026, 03:32 PM UTC · Resolved May 29, 2026, 03:35 PM UTC · 2m