Interviewstream Status

**Root Cause:** * The incident was caused by an infrastructure-level service disruption with AWS within a cloud hosting availability zone, which impacted database connectivity and platform availability. **Resolution Details:** * The AWS issue was mitigated, database services recovered successfully, and platform access was fully restored. **Remediation Items:** * We are reviewing resiliency, monitoring, and recovery configurations to help reduce the impact of similar infrastructure-related incidents in the future. Our team will continue to monitor closely.

### **Root Cause:** * The incident was caused by inaccessible deployment files combined with server resource settings that exceeded system capacity, leading to failed deployments and service instability. ### **Resolution Details:** * Our development team identified and corrected the configurations. Restoring normal platform functionality for all users. ### **Remediation Items:** * To prevent this from happening again, we’re improving how deployment files are managed, ensuring server settings better match system capacity, reviewing options to ensure stronger monitoring and checks before deployments, and improving access for faster troubleshooting.

### **Root Cause:** * The issue was triggered by a validation failure. ### **Resolution Details:** * Our development team addressed the failure which resolved the issue and restored the iOS mobile app. ### **Remediation Items:** * Review and confirm mobile alert/notification settings. * Identify areas for mobile fallback validation logic in case of third-party service failures.

### **Root Cause:** * The issue was triggered by a third-party email validation failure, which prevented users from registering via Landing Pages and Event Templates. ### **Resolution Details:** * Our development team collaborated with the vendor to resolve the issue and restore full functionality. ### **Remediation Items:** * Review and confirm all alert/notification settings. * Identify areas for fallback validation logic in case of third-party service failures.

### **Root Cause:** * This incident was caused by AWS connection and precautionary measures, resulting in intermittent service access for a limited number of users. ### **Resolution Details:** * Our development team, working with AWS, promptly identified and resolved the issue, restoring normal platform functionality for all users. ### **Remediation Items:** * Rechecking and confirming all alerts and notifications. Remediation was completed for intermittent service disruption on the day of occurrence for impacted users.

### **Root Cause Analysis:** * This incident was due to a failed node server that is responsible for our live platform.  ### **Resolution Details:** * The development team identified the failure and implemented a fix.   * We confirmed that the fix implemented resolved the behavior restoring access to connect.  Once restored the system behavior returned to operational.  ### **Remediation Items:** * Adding additional alerts.

### **Root Cause Analysis:** * This incident was due to a failed internal account creation. ### **Resolution Details:** * The development team identified the failure and implemented a fix.   * We confirmed that no End-Users were impacted by this incident. ### **Remediation Items:** * Review and improve our codebase.

### **Root Cause Analysis:** This incident was due to a hardware failure on our Amazon Web Service \(AWS\) instance.   The auto-restore failed due to an outdated codebase on our server. ### **Resolution Details:** The development team identified the failure and restored the code.  Once restored the system behavior returned to operational.   ### **Remediation Items:** Review and improve our codebase.

#### **Root Cause Analysis:** This incident was due to a long-running database query.   #### **Resolution Details:** The development team identified a long-running query that was causing database performance issues. After those queries were terminated, system behavior returned to operational.   #### **Remediation Items:** Improve optimization and logging.

The incident affecting our RIVS US Platform (on demand, connect, scheduler, and builder) is no longer occurring. We will continue to monitor the system's performance. Our apologies for any disruption this incident may have caused to your user experience. If you have any questions, please submit a request to our technical support team. Best Regards, Interviewstream support https://support.interviewstream.com

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance was completed Tuesday, September 24, 2025, at 11:30 PM CDT. If you have any questions, please submit a request to our technical support team. Best Regards, Interviewstream support https://support.interviewstream.com

The scheduled maintenance was completed Tuesday, September 23, 2025, at 11:30 PM CDT. If you have any questions, please submit a request to our technical support team. Best Regards, Interviewstream support https://support.interviewstream.com

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

Scheduled maintenance for Saturday, September 7, 2024, at 9:00 PM CDT \(0300 GMT\) has been canceled.

We want to make you aware that the update to interview Insights is complete. If you have any questions, please submit a request to our Technical Support team. Best Regards, interviewstream Support https://support.interviewstream.com

The scheduled maintenance has been completed.