Is Ciptex down?

Last checked 3m ago
Current status
Ciptex has degraded performance

Active incident: Twilio - Inbound SIP Calls With OPUS Codec Only Blocked

Official status page: https://status.ciptex.com · Polled every 5 minutes · 102 components tracked

Ciptex is reporting degraded performance right now (last checked 3m ago). 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 54 incidents in the last 90 days (99.53% uptime). Get email, Slack, Discord, or webhook alerts the moment Ciptex reports a new incident — free for 5 monitors, no credit card.

Users who monitor Ciptex also follow these Telephony services: Twilio Aircall Dialpad Loom Plivo Nextiva Mitel OneSignal Attentive Grasshopper View all 6,000+ providers
Ciptex uptime 99.53% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Active incident 1

  1. Ongoing ● 1h 39m
    Started Sep 15, 2026, 08:13 PM UTC
    Timeline · 2 updates
    • investigating · Sep 15, 2026, 08:13 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.

    • monitoring · Sep 15, 2026, 08:17 PM UTC

      Twilio have identified an issue whereby some calls made to Twilio using Programmable Voice SIP interfaces and OPUS codec may unexpectedly be rejected. Customers may see a SIP 488 responses for those requests. The Twilio engineering team is working on a fix. We will provide another update in 2 hours or as soon as more information becomes available.

    Latest: Twilio have identified an issue whereby some calls made to Twilio using Programmable Voice SIP interfaces and OPUS codec may unexpectedly be rejected. Customers may see a SIP 488 r…

Recent outages & incidents

Past 90 days
  1. Resolved 1h 26m
    Started Sep 15, 2026, 03:42 PM UTC · Resolved Sep 15, 2026, 05:09 PM UTC
    Twilio Group Rooms
    Timeline · 3 updates
    • investigating · Sep 15, 2026, 03:42 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 · Sep 15, 2026, 03:44 PM UTC

      Twilio are currently investigating an issue where the Video Room Settings page is failing to load for users within 1Console. Their engineering team is actively looking into the root cause. We will provide an update in 1 hour or as soon as more information becomes available.

    • resolved · Sep 15, 2026, 05:09 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.

  2. Resolved 1h 37m
    Started Sep 14, 2026, 10:19 AM UTC · Resolved Sep 14, 2026, 11:57 AM UTC
    Race ESign
    Timeline · 4 updates
    • investigating · Sep 14, 2026, 10:15 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 · Sep 14, 2026, 10:19 AM UTC

      Race ESign is experiencing a slowdown of processing time for Advanced Electronic Signature identity verification and standalone Identity Verification service. We are actively working with our Identity Verification provider to understand the root cause and restore service as soon as possible.

    • identified · Sep 14, 2026, 11:11 AM UTC

      Our identity verification provider has confirmed an issue at their side leading to instabilities. Although some identity verification requests are successful, the majority is either failing (for AES) or stuck in a pending status. We are actively monitoring the situation and communicate directly with our provider to bring the situation back to normal as soon as possible.

    • resolved · Sep 14, 2026, 11:57 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 7h 38m
    Started Sep 14, 2026, 09:51 AM UTC · Resolved Sep 14, 2026, 05:29 PM UTC
    Twilio Voice, Middle East & Africa
    Timeline · 5 updates
    • investigating · Sep 14, 2026, 09:51 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 · Sep 14, 2026, 09:52 AM UTC

      Twilio customers may be experiencing voice call failures from a subset of Twilio United States Phone Numbers to Korek Telecom network subscribers in Iraq. Twilio team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

    • investigating · Sep 14, 2026, 11:58 AM UTC

      Twilio customers may be experiencing voice call failures from a subset of Twilio United States Phone Numbers to Korek Telecom network subscribers in Iraq. Twilio team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

    • identified · Sep 14, 2026, 12:58 PM UTC

      Twilio customers may be experiencing voice call failures from a subset of Twilio United States Phone Numbers to network subscribers in Iraq. Twilio has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

    • resolved · Sep 14, 2026, 05:29 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.

  4. Resolved 2m
    Started Sep 11, 2026, 02:34 PM UTC · Resolved Sep 11, 2026, 02:36 PM UTC
    Timeline · 2 updates
    • investigating · Sep 11, 2026, 02:34 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 · Sep 11, 2026, 02:36 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.

  5. Resolved 1h 11m
    Started Sep 10, 2026, 02:31 PM UTC · Resolved Sep 10, 2026, 03:42 PM UTC
    Timeline · 3 updates
    • investigating · Sep 10, 2026, 02:31 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 · Sep 10, 2026, 02:46 PM UTC

      We are continuing to investigate this issue.

    • resolved · Sep 10, 2026, 03:42 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.

See the full Ciptex outage history

49 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

Outage history

Past 90 days · 54 incidents View full outage history →