Is Cytracom down?

Last checked 2m ago
Current status
Cytracom is up

No incidents right now.

Official status page: https://status.cytracom.com · Polled every 5 minutes · 26 components tracked

Cytracom is operational right now. Last checked 2m ago; the most recent incident resolved 2d ago.

Real-time Cytracom status, recent outages, and incident history — pulled directly from Cytracom's official status page at https://status.cytracom.com every 5 minutes. Pingoru tracks 26 Cytracom services and has captured 23 incidents in the last 90 days (98.97% uptime). Get email, Slack, Discord, or webhook alerts the moment Cytracom reports a new incident — free for 5 monitors, no credit card.

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

Recent outages & incidents

Past 90 days
  1. Resolved 16h 51m
    Started Jun 10, 2026, 06:43 PM UTC · Resolved Jun 11, 2026, 11:34 AM UTC
    BLF Presence
    Timeline · 3 updates
    • identified · Jun 10, 2026, 06:43 PM UTC

      We are currently experiencing a backlog in our call event processing system, which may cause delays in event-related updates. This may impact CDR processing, BLF status updates, and voicemail arrival indicators. Inbound and outbound calling remain operational, and voicemail delivery is not impacted. Our team is actively working to clear the backlog and will continue to monitor the system.

    • monitoring · Jun 10, 2026, 08:50 PM UTC

      We have identified and corrected the issue. Call Detail Records (CDRs) in Insights during the incident will be available within next 12 hours. New events are processing normally and are not expected to experience delays. Inbound and outbound calling, voicemail delivery, and new CDR processing are not impacted at this time. We will continue monitoring until the backlog is fully cleared.

    • resolved · Jun 11, 2026, 11:34 AM UTC

      All backlog Call Details Records have been processed. This issue is now resolved.

    Latest: All backlog Call Details Records have been processed. This issue is now resolved.

  2. Resolved 5h 31m
    Started Jun 09, 2026, 08:32 PM UTC · Resolved Jun 10, 2026, 02:04 AM UTC
    BLF Presence
    Timeline · 3 updates
    • identified · Jun 09, 2026, 08:32 PM UTC

      We are currently experiencing a backlog in our call event processing system, which may cause delays in event-related updates. This may impact CDR processing, BLF status updates, and voicemail arrival indicators. Inbound and outbound calling remain operational, and voicemail delivery is not impacted. Our team is actively working to clear the backlog and will continue to monitor the system.

    • monitoring · Jun 09, 2026, 09:44 PM UTC

      We have identified and corrected the issue that caused a backlog in our event processing pipeline. The issue was related to a failed event consumer, which has now been restarted, and queued messages are processing successfully. Some Call Detail Records (CDRs) in Insights may continue to be delayed for the next few hours while the CDR processor catches up on previously delayed events. New events are processing normally and are not expected to experience delays. Inbound and outbound calling, voicemail delivery, and new CDR processing are not impacted at this time. We will continue monitoring until the backlog is fully cleared.

    • resolved · Jun 10, 2026, 02:04 AM UTC

      The backlog processing has been completed. This issue is now resolved.

    Latest: The backlog processing has been completed. This issue is now resolved.

  3. Resolved 12h 56m
    Started Jun 03, 2026, 03:10 PM UTC · Resolved Jun 04, 2026, 04:06 AM UTC
    Call Completion
    Timeline · 3 updates
    • investigating · Jun 03, 2026, 03:10 PM UTC

      We are currently investigating an issue causing intermittent inbound and outbound call failures for some customers. Our engineering team is actively working to identify the root cause and restore normal call processing. We will provide an update as soon as more information is available.

    • monitoring · Jun 03, 2026, 03:49 PM UTC

      We have identified and mitigated the issue that caused intermittent call setup failures for some customers. The issue was related to a degraded backend component that impacted call processing on a subset of voice infrastructure. Our engineering team applied corrective action, and calls are now processing normally. We are continuing to monitor the platform closely to ensure stability.

    • resolved · Jun 04, 2026, 04:06 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 4h 45m
    Started Jun 02, 2026, 04:11 PM UTC · Resolved Jun 02, 2026, 08:57 PM UTC
    Call Completion
    Timeline · 4 updates
    • investigating · Jun 02, 2026, 04:11 PM UTC

      We are currently investigating intermittent inbound and outbound call failures affecting some customers. Our team is actively working to identify the issue and will provide updates as they become available.

    • monitoring · Jun 02, 2026, 04:49 PM UTC

      We identified an issue affecting call processing on a subset of voice servers, which resulted in intermittent inbound and outbound call failures for some customers. Our engineering team applied corrective action, and call processing has returned to normal. We are continuing to monitor the platform closely to ensure stability.

    • monitoring · Jun 02, 2026, 08:56 PM UTC

      The issue causing intermittent inbound and outbound call failures has been resolved. Our engineering team identified a capacity constraint in a backend call processing service and applied corrective action. Calls are now processing normally, and the platform remains stable.

    • resolved · Jun 02, 2026, 08:57 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 4h 45m
    Started May 29, 2026, 06:41 PM UTC · Resolved May 29, 2026, 11:27 PM UTC
    Caller ID ResolutionSpamGuard Service
    Timeline · 3 updates
    • identified · May 29, 2026, 06:41 PM UTC

      We have identified that our third-party CNAM provider is not responding within our required performance thresholds. To prevent call completion delays or failures, we are temporarily bypassing Caller ID name resolution for affected calls. During this time, calls may complete without a resolved caller identity or display name. Call delivery itself remains operational. Our team is working on a remediation plan and expects to implement a permanent solution within the next 72 hours. We will continue to monitor the service and provide updates as progress is made.

    • monitoring · May 29, 2026, 09:02 PM UTC

      The Caller Id resolution is working as expected. We are monitoring for any further issues.

    • resolved · May 29, 2026, 11:27 PM UTC

      The CNAM (Caller ID) service is fully functional without any performance constraints.

    Latest: The CNAM (Caller ID) service is fully functional without any performance constraints.

See the full Cytracom outage history

13 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Cytracom outage history →

Or sign up free to get alerts when Cytracom breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 18 incidents View full outage history →