interviewstream Status Page

May 8, 2026 · resolved May 8

**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.

Jan 8, 2026 · resolved Jan 9

### **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.

Aug 4, 2025 · resolved Aug 4

### **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.

Jul 6, 2025 · resolved Jul 7

### **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.

Nov 16, 2024 · resolved Nov 16

### **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.