MagicPod incident
Schedeled batch run fails on iOS 26 cloud devices.
MagicPod experienced a minor incident on November 19, 2025, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Nov 19, 2025, 03:12 AM UTC
Type: Incident Duration: 1 day, 2 hours and 52 minutes Affected Components: Cloud Device Nov 19, 03:12:27 GMT+0 - Identified - 🚨 Notification of System Disruption: Schedeled batch run fails on iOS 26 cloud devices We are currently experiencing issues with scheduled batch run on iOS 26\. Regarding this issue, we have already identified the cause and are currently working on restoration efforts. We will fix it tonight. ■ Affected Services \- Schedeled batch run on iOS 26 cloud device We kindly request that you avoid running the scheduled batch run on iOS 26 cloud devices. We sincerely apologize for any inconvenience this may cause. Updates will be posted regularly on the MagicPod Status Page as more information becomes available. Nov 19, 04:53:14 GMT+0 - Monitoring - ✅ Recovery and Monitoring Status: Schedeled batch run fails on iOS 26 cloud devices We have completed the necessary actions to resolve the issues with the disruption of scheduled batch run fails on iOS 26 cloud devices and have successfully restored system functionality. The system is now under a 24-hour observation period to ensure stable operation. ■ Recovery Details \- Scheduled batch runs on iOS 26 cloud devices are now functioning normally If no further issues are detected during the observation period, we will consider this incident resolved. Should any new issues arise, we will promptly notify you. We sincerely apologize for the inconvenience this has caused and are committed to providing stable service moving forward. Nov 20, 06:03:58 GMT+0 - Resolved - 📋 Completion of Observation Period: Schedeled batch run fails on iOS 26 cloud devices We are pleased to inform you that the observation period for iOS 26's scheduled batch run has concluded, and the system is functioning properly without any issues. We consider this incident officially resolved. We apologize for any disruption this incident may have caused to your operations. Our team is implementing additional measures to prevent similar incidents in the future.