ISI Outage History

ISI is up right now

ISI had 20 outages in the last 2 years totaling 797h 19m of downtime — averaging 0.8 incidents per month.

There were 20 ISI outages since August 14, 2024 totaling 797h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.isi-info.com

Notice April 13, 2026

Transfer.isi-info.com SFTP Services

Detected by Pingoru
Apr 13, 2026, 12:56 AM UTC
Resolved
Apr 13, 2026, 06:14 PM UTC
Duration
17h 17m
Affected: SFTP Data Transfer
Timeline · 2 updates
  1. monitoring Apr 13, 2026, 12:56 AM UTC

    ISI initiated a service failover for SFTP connections utilizing transfer.isi-info.com at 7:35 PM CDT to resolve an authentication issue impacting a segment of customers. If you are experiencing a CUCM connection issue or received a CUCM CDR alert, please restart your CUCM Repository Manager(s) and CDR Agent services to restart the flow of CDR files. Please contact ISI Customer Support at 1-800-326-6183 (US Toll Free) or 1-847-592-3250 (Local or Non-US) if you have any questions.

  2. resolved Apr 13, 2026, 06:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 2, 2026

CUCM Directory Import Issue

Detected by Pingoru
Apr 02, 2026, 03:30 PM UTC
Resolved
Apr 02, 2026, 09:42 PM UTC
Duration
6h 11m
Affected: Cisco UCM
Timeline · 3 updates
  1. investigating Apr 02, 2026, 03:30 PM UTC

    We are currently investigating an issue after the recent update to Cloud Connect (v2.0.47070.26090), which is affecting CUCM Directory Imports. A Linkage error is preventing the isvCLoudConnect service from starting successfully. Our Engineering Team is currently working on a solution to this. Thank you for you patience.

  2. identified Apr 02, 2026, 04:49 PM UTC

    The problem has been identified. Please restart your Cloud Connect server as a resolution, if you are experiencing this issue. A root cause is still being investigated.

  3. resolved Apr 02, 2026, 09:42 PM UTC

    Restarting the server has been confirmed to be a working resolution. Please restart your server running the Cloud Connect software if you are experiencing issues with your scheduled CUCM Directory Imports. Our Support Team will also be reaching out to those directly affected shortly, if we've not already communicated with you.

Read the full incident report →

Minor March 23, 2026

MS Teams and Webex Data Collection Errors

Detected by Pingoru
Mar 23, 2026, 03:20 PM UTC
Resolved
Mar 25, 2026, 02:41 PM UTC
Duration
1d 23h
Affected: Cisco WebexMicrosoft Teams
Timeline · 4 updates
  1. monitoring Mar 23, 2026, 03:20 PM UTC

    An issue with MS Teams data collection from 9:47AM to 10:07PM (CDT) on March 22nd was identified and resolved. We are performing root a cause analysis, and will provide additional details on the gap in CDR as it becomes available.

  2. investigating Mar 23, 2026, 04:17 PM UTC

    We are now troubleshooting intermediate delays in both MS Teams and Webex processing.

  3. identified Mar 24, 2026, 02:55 PM UTC

    Delays in processing for both MS Teams and Webex have been resolved. We are currently working on a solution to recover missing MS Teams call records from the weekend.

  4. resolved Mar 25, 2026, 02:41 PM UTC

    Missing MS Teams data from the 22nd (Sunday) been collected and processed. Thank you for your patience during this issue.

Read the full incident report →

Major March 6, 2026

Unexpected Webex Service App Error

Detected by Pingoru
Mar 06, 2026, 03:37 PM UTC
Resolved
Mar 12, 2026, 04:39 PM UTC
Duration
6d 1h
Affected: Cisco Webex
Timeline · 4 updates
  1. identified Mar 06, 2026, 03:37 PM UTC

    An unexpected change in Webex API behavior is impacting Queue syncing and data collection for a subset of Webex data sources. Cisco has acknowledged the error, and are currently testing a resolution.

  2. identified Mar 09, 2026, 07:03 PM UTC

    ISI is implementing a temporary workaround to resume Webex call data collection while we wait for final resolution from Webex. Call processing delays may still occur, but ISI will work to address ASAP.

  3. identified Mar 10, 2026, 04:39 PM UTC

    ISI is implementing a temporary workaround to resume Webex call data (CDR) collection while we wait for final resolution from Webex. Call processing delays may still occur, but ISI will work to address ASAP. Please note that Webex Directory Imports are still unavailable while a permanent resolution is being worked on.

  4. resolved Mar 12, 2026, 04:39 PM UTC

    Webex has notified us that they have rolled out their fix to all data centers, and our own testing confirms that the Connectors are back online. Thank you for your patience, and please reach out to our support team know if you're experiencing any issues with data collection or Queue syncing ([email protected] or https://isianalytics.com/support).

Read the full incident report →

Notice February 9, 2026

Inbound Support Calls

Detected by Pingoru
Feb 09, 2026, 03:18 PM UTC
Resolved
Feb 10, 2026, 06:41 PM UTC
Duration
1d 3h
Timeline · 3 updates
  1. investigating Feb 09, 2026, 03:18 PM UTC

    We are currently experiencing an issue receiving calls to our support line. Please use our web form at "https://isianalytics.com/support/", or email "[email protected]" if you need to reach the Support Team.

  2. investigating Feb 09, 2026, 03:19 PM UTC

    We are continuing to investigate this issue.

  3. resolved Feb 10, 2026, 06:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 24, 2026

Webex Collection

Detected by Pingoru
Jan 24, 2026, 02:45 PM UTC
Resolved
Jan 25, 2026, 02:54 PM UTC
Duration
1d
Affected: Cisco Webex
Timeline · 4 updates
  1. investigating Jan 24, 2026, 02:45 PM UTC

    We are currently investigating an issue preventing call data collection from Webex.

  2. monitoring Jan 24, 2026, 05:21 PM UTC

    Webex call data is now collecting and catching up from the time last retrieved successfully. Cisco communicated a change to the Webex API FQDN used to collect call data. In the scheduled maintenance this week, ISI updated the used FQDN accordingly and confirmed collection systems were operational. As of 12AM CST, the new FQDN was no longer operational for ISI. We reverted our systems back to the previous FQDN and collection has resumed. ISI is in touch with Webex Dev Support to determine next steps.

  3. monitoring Jan 24, 2026, 07:10 PM UTC

    Webex call data collection has caught up to current time.

  4. resolved Jan 25, 2026, 02:54 PM UTC

    After monitoring, the call data collection for Webex has remained stable. ISI will be working with Webex Dev Support to prevent this issue in the future.

Read the full incident report →

Minor January 15, 2026

Cloud Connect Server Connection Issue

Detected by Pingoru
Jan 15, 2026, 10:00 PM UTC
Resolved
Jan 20, 2026, 07:57 PM UTC
Duration
4d 21h
Affected: Cisco UCM
Timeline · 4 updates
  1. investigating Jan 15, 2026, 10:00 PM UTC

    After a recent update to Cloud Connect, an issue was discovered that has caused a subset of Cloud Connect Servers to be unable to connect to ISI Analytics; resulting in Directory Imports being unable to fetch new data. This is currently under investigation, and updates on a resolution will be provided when available.

  2. identified Jan 19, 2026, 08:21 PM UTC

    The issue has been identified, and an update for Cloud Connect is being prepared for release later today. Thank you for your patience while we tend to this issue.

  3. monitoring Jan 20, 2026, 02:16 PM UTC

    The Cloud Connect software update has been release, and we are now monitoring server connection statuses to confirm the issue has been resolved.

  4. resolved Jan 20, 2026, 07:57 PM UTC

    After monitoring server statuses this morning, we are considering this issue resolved. Thank you for your patience.

Read the full incident report →

Minor December 1, 2025

Classic Reporting - Outbound Emails

Detected by Pingoru
Dec 01, 2025, 03:33 PM UTC
Resolved
Dec 02, 2025, 10:10 PM UTC
Duration
1d 6h
Affected: Infortel Select Classic
Timeline · 4 updates
  1. investigating Dec 01, 2025, 03:33 PM UTC

    An intermittent issue with Office 365 sending emails to external parties is being investigated. This may affect scheduled reports delivery from Classic Reporting.

  2. investigating Dec 01, 2025, 07:49 PM UTC

    ISI will be implementing a system update to address report delivery for Classic Reporting at 2PM. Temporary system interruption can be expected. Another notification will be sent when the update is complete.

  3. monitoring Dec 01, 2025, 10:04 PM UTC

    The system update to address report delivery for Classic Reporting has been completed. Scheduled reports are running again, and the situation is being monitored.

  4. resolved Dec 02, 2025, 10:10 PM UTC

    This situation has been considered resolved. Scheduled reports that weren't sent during yesterday's downtime will need to be manually run by the report's owner, or another User with access to reporting management.

Read the full incident report →

Minor August 27, 2025

Main Dashboard Widgets Error

Detected by Pingoru
Aug 27, 2025, 01:16 PM UTC
Resolved
Aug 27, 2025, 02:02 PM UTC
Duration
45m
Affected: ISI Analytics
Timeline · 3 updates
  1. investigating Aug 27, 2025, 01:16 PM UTC

    We are investigating an error causing an interruption in loading data for Main Dashboard Widgets. Data is still available for reporting, Queue Dashboards and Infortel Classic remain unaffected. Updates will be posted as they become available.

  2. identified Aug 27, 2025, 01:52 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Aug 27, 2025, 02:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 17, 2025

Infortel Select Classic Report Emails

Detected by Pingoru
Jul 17, 2025, 04:35 AM UTC
Resolved
Jul 17, 2025, 09:55 PM UTC
Duration
17h 19m
Affected: Infortel Select Classic
Timeline · 4 updates
  1. investigating Jul 17, 2025, 04:35 AM UTC

    During scheduled maintenance validation, ISI identified an issue regarding Infortel Select Classic report emails not being received. It has been determined reports scheduled between 7PM to 9:30PM CDT generated but were unable to be sent via email. ISI is investigating the issue. Reports that ran after 9:30PM CDT have been sent. Scheduled reports and email are currently functional. For any critical needs, rerunning any missed reports that fell within this time frame can be completed within Infortel Select Classic.

  2. identified Jul 17, 2025, 01:31 PM UTC

    A fix for the delayed reports has been identified. We are working towards implementing a solution to have them sent.

  3. monitoring Jul 17, 2025, 02:21 PM UTC

    A fix has been implemented. The delayed report emails have now all been sent. We'll continue to monitor the situation today.

  4. resolved Jul 17, 2025, 09:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 1, 2025

Temporary Login and Processing Delay

Detected by Pingoru
May 01, 2025, 06:26 PM UTC
Resolved
May 02, 2025, 11:59 AM UTC
Duration
17h 32m
Affected: ISI AnalyticsInfortel Select Classic
Timeline · 2 updates
  1. monitoring May 01, 2025, 06:26 PM UTC

    ISI identified an issue preventing logging in and processing for some customers from 11:20am to 12:40pm (CST). The issue has since been resolved, and we are still monitoring to confirm stability.

  2. resolved May 02, 2025, 11:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 27, 2025

Cisco Webex Processing Delay

Detected by Pingoru
Feb 27, 2025, 09:21 PM UTC
Resolved
Feb 28, 2025, 09:34 PM UTC
Duration
1d
Affected: Cisco Webex
Timeline · 3 updates
  1. investigating Feb 27, 2025, 09:21 PM UTC

    ISI is experiencing intermittent delays with data delivery from Cisco Webex. This may result in delays in new records appearing in your system. We have reported the issue to Cisco, and will provide additional updates when available.

  2. identified Feb 28, 2025, 02:16 PM UTC

    ISI has received an update from Webex that they are working to increase resources and address the backlog of CDR to be processed. We will continue to provide updates as they become available.

  3. resolved Feb 28, 2025, 09:34 PM UTC

    Webex has updated ISI that the underlying issue is resolved. We are working to collect any missing records available from Webex and will continue to monitor the incident.

Read the full incident report →

Minor February 6, 2025

Adhoc Reporting Error

Detected by Pingoru
Feb 06, 2025, 04:24 PM UTC
Resolved
Feb 06, 2025, 09:59 PM UTC
Duration
5h 35m
Affected: Infortel Select Classic
Timeline · 3 updates
  1. investigating Feb 06, 2025, 04:24 PM UTC

    We are troubleshooting an error that may cause some users issues with running adhoc reports. Updates will be posted as they become available.

  2. monitoring Feb 06, 2025, 05:00 PM UTC

    Issues are no longer occurring, but services are still being monitor.

  3. resolved Feb 06, 2025, 09:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 24, 2025

Microsoft Teams Processing Delay

Detected by Pingoru
Jan 24, 2025, 10:32 PM UTC
Resolved
Jan 25, 2025, 01:34 PM UTC
Duration
15h 2m
Affected: ISI AnalyticsInfortel Select ClassicMicrosoft Teams
Timeline · 2 updates
  1. monitoring Jan 24, 2025, 10:32 PM UTC

    ISI is experiencing a delay in data delivery from Microsoft. This may result in a delay of information appearing in your system.

  2. resolved Jan 25, 2025, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 12, 2024

SFTP Services

Detected by Pingoru
Dec 12, 2024, 04:35 PM UTC
Resolved
Dec 13, 2024, 03:12 PM UTC
Duration
22h 37m
Affected: SFTP Data Transfer
Timeline · 2 updates
  1. monitoring Dec 12, 2024, 04:35 PM UTC

    ISI initiated a service failover for SFTP connections utilizing transfer.isi-info.com at 10:07 AM CST to resolve an authentication issue impacting a segment of customers. If you are experiencing a CUCM connection issue or received a CUCM CDR alert, please restart your CUCM Repository Manager(s) and CDR Agent services to restart the flow of CDR files. Please contact ISI Customer Support at 1-800-326-6183 (US Toll Free) or 1-847-592-3250 (Local or Non-US) if you have any questions.

  2. resolved Dec 13, 2024, 03:12 PM UTC

    This incident is now resolved. ISI Customer Support will continue to work with any customers that may require CUCM CDR service restarts to establish their SFTP connection.

Read the full incident report →

Minor December 2, 2024

Firewall Error

Detected by Pingoru
Dec 02, 2024, 05:17 PM UTC
Resolved
Dec 02, 2024, 11:06 PM UTC
Duration
5h 48m
Affected: SFTP Data TransferInfortel Select Classic
Timeline · 3 updates
  1. investigating Dec 02, 2024, 05:17 PM UTC

    One of our firewalls faced an Azure error, and then failed over to the secondary firewall. Some users may have experienced a brief interruption with Infortel Select Classic and SFTP connections. If you are not receiving new records, please follow the steps outlined in this support article to restart your CDR Repository Manager. https://isianalytics.com/help/doc/cucm-cisco-cdr-troubleshooting-guide/

  2. monitoring Dec 02, 2024, 05:40 PM UTC

    The queue of emails are now all sent. SFTP services have been restarted. System is currently stable. If you are not receiving new records, please follow the steps outlined in this support article to restart your CDR Repository Manager. https://isianalytics.com/help/doc/cucm-cisco-cdr-troubleshooting-guide/

  3. resolved Dec 02, 2024, 11:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 19, 2024

Microsoft Teams

Detected by Pingoru
Nov 19, 2024, 03:22 PM UTC
Resolved
Nov 21, 2024, 01:32 PM UTC
Duration
1d 22h
Affected: Microsoft Teams
Timeline · 6 updates
  1. investigating Nov 19, 2024, 03:22 PM UTC

    We are currently investigating delays in MS Teams data.

  2. monitoring Nov 19, 2024, 03:59 PM UTC

    ISI is receiving internal error responses from MSGraph, and will continue to monitor this issue. In instances where call data is being received from MSGraph, processing is working.

  3. monitoring Nov 19, 2024, 10:04 PM UTC

    We have a support case opened with Microsoft, and are continuing to monitor the issue. This issue stems from Microsoft not sending the necessary data to our system, which has caused interruptions in service.

  4. monitoring Nov 20, 2024, 01:23 PM UTC

    Error responses from MSGraph have reduced, but not diminished entirely. In instances where call data is being received from MSGraph, processing is working.

  5. monitoring Nov 20, 2024, 10:20 PM UTC

    Microsoft has acknowledged the incident with Issue ID TM938579 impacting the ability to retrieve call data. They're implementing new configuration changes to Microsoft Teams to assist in processing calling data more efficiently and resolving impact.

  6. resolved Nov 21, 2024, 01:32 PM UTC

    Microsoft has confirmed that the MSGraph response errors has stopped. Missing CDR will continue to backfill throughout the day.

Read the full incident report →

Notice October 28, 2024

Scheduled Azure Cloud Service Maintenance

Detected by Pingoru
Oct 28, 2024, 12:43 PM UTC
Resolved
Oct 30, 2024, 01:11 PM UTC
Duration
2d
Affected: SFTP Data Transfer
Timeline · 4 updates
  1. monitoring Oct 28, 2024, 12:43 PM UTC

    Microsoft Azure services have notified their subscribers of a scheduled maintenance window starting Monday 10/28 at 10PM CT to Tuesday 10/29 6AM CT. There is no service interruption expected for Infortel Select and SFTP services. If you receive CUCM CDR alerts, please restart your CUCM Repository Manager(s) and CDR Agent services to restart the flow of CDR files.

  2. monitoring Oct 29, 2024, 12:38 PM UTC

    ISI has been notified that scheduled maintenance will continue again Tuesday 10/29 10PM CT to Wednesday 10/30 6AM CT.

  3. monitoring Oct 30, 2024, 11:51 AM UTC

    ISI initiated a service failover for SFTP connections utilizing transfer.isi-info.com at 3:05AM CDT to resolve an authentication issue impacting a segment of customers. If you receive CUCM CDR alerts, please restart your CUCM Repository Manager(s) and CDR Agent services to restart the flow of CDR files. Please contact ISI Customer Support at 1-800-326-6183 (US Toll Free) or 1-847-592-3250 (Local or Non-US) if you have any questions.

  4. resolved Oct 30, 2024, 01:11 PM UTC

    The scheduled maintenance has been completed.

Read the full incident report →

Minor October 10, 2024

SFTP Service Degradation

Detected by Pingoru
Oct 10, 2024, 07:32 PM UTC
Resolved
Oct 17, 2024, 12:50 PM UTC
Duration
6d 17h
Affected: SFTP Data Transfer
Timeline · 3 updates
  1. investigating Oct 10, 2024, 07:32 PM UTC

    We are currently experiencing degraded performance for SFTP services. Some customers may encounter slow transfer speeds or delays when authenticating. Initial analysis indicates that all VMs have appropriate CPU, memory, and other resources available. As part of our efforts to resolve the issue, a change has been made to the load balancing configuration to improve performance. Our team is continuing to monitor the impact and will provide updates as more information becomes available.

  2. monitoring Oct 14, 2024, 04:01 PM UTC

    We have found improved performance since the configuration changes and will continue to monitor the situation this week.

  3. resolved Oct 17, 2024, 12:50 PM UTC

    This incident has been resolved. Service performance has returned to its normal operating state.

Read the full incident report →

Notice October 4, 2024

Infortel Select Dashboard Widgets

Detected by Pingoru
Oct 04, 2024, 08:33 PM UTC
Resolved
Oct 05, 2024, 01:03 PM UTC
Duration
16h 30m
Affected: Infortel Select Classic
Timeline · 4 updates
  1. investigating Oct 04, 2024, 08:33 PM UTC

    ISI is investigating an issue with widget errors on cloud.isi-info.com and clientlogin.isi-info.com.

  2. investigating Oct 04, 2024, 08:56 PM UTC

    ISI is restarting cloud.isi-info.com and clientlogin.isi-info.com web services. Users may experience an interruption in service.

  3. monitoring Oct 04, 2024, 09:08 PM UTC

    Issue is currently resolved and being monitored.

  4. resolved Oct 05, 2024, 01:03 PM UTC

    This incident has been resolved.

Read the full incident report →