MagicPod Outage History

Started May 22, 2026, 05:55 AM UTC· resolved May 23, 2026, 06:03 AM UTC

1. identified May 22, 2026, 05:55 AM UTC

   There is currently an issue with Claude Sonnet 4.6, and MagicPod Autopilot is unavailable. Claude is currently working on a fix. https://status.claude.com/ ■ Affected Services \- MagicPod Autopilot Please refrain from using MagicPod Autopilot until the issue is resolved. We sincerely apologize for any inconvenience this may cause. Updates will be posted regularly on the MagicPod Status Page as more information becomes available..

2. identified May 22, 2026, 05:55 AM UTC

   There is currently an issue with Claude Sonnet 4.6, and MagicPod Autopilot is unavailable. Claude is currently working on a fix. https://status.claude.com/ ■ Affected Services \- MagicPod Autopilot Please refrain from using MagicPod Autopilot until the issue is resolved. We sincerely apologize for any inconvenience this may cause. Updates will be posted regularly on the MagicPod Status Page as more information becomes available.

3. monitoring May 22, 2026, 06:13 AM UTC

   ✅ Recovery and Monitoring Status: Autopilot Claude has completed its end of the process, and we have confirmed that Autopilot is operational. The system is now under a 24-hour observation period to ensure stable operation. ■ Recovery Details \- MagicPod Autopilot 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..

4. monitoring May 22, 2026, 06:13 AM UTC

   ✅ Recovery and Monitoring Status: Autopilot Claude has completed its end of the process, and we have confirmed that Autopilot is operational. The system is now under a 24-hour observation period to ensure stable operation. ■ Recovery Details \- MagicPod Autopilot 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.

5. resolved May 23, 2026, 06:03 AM UTC

   📋 Completion of Observation Period: MagicPod Autopilot We are pleased to inform you that the observation period for MagicPod Autopilot 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. .

6. resolved May 23, 2026, 06:03 AM UTC

   📋 Completion of Observation Period: MagicPod Autopilot We are pleased to inform you that the observation period for MagicPod Autopilot 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.

Read the full incident report →

Started May 08, 2026, 05:31 AM UTC· resolved May 08, 2026, 05:31 AM UTC

1. resolved May 08, 2026, 05:31 AM UTC

   We were experiencing an issue where batch runs could not be executed when the test execution environment was set to SauceLabs or BrowserStack. We have now completed our investigation into the cause and resolved the issue, and batch runs can now be executed normally. ■ Time the problem occurred May 7th 13:40 - May 8th 10:40 JST 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..

2. resolved May 08, 2026, 05:31 AM UTC

   We were experiencing an issue where batch runs could not be executed when the test execution environment was set to SauceLabs or BrowserStack. We have now completed our investigation into the cause and resolved the issue, and batch runs can now be executed normally. ■ Time the problem occurred May 7th 13:40 - May 8th 10:40 JST 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.

Read the full incident report →

Started Feb 09, 2026, 01:11 AM UTC· resolved Feb 09, 2026, 04:12 AM UTC

1. investigating Feb 09, 2026, 01:11 AM UTC

   🚨 Notice Regarding Test Execution Settings Dialog Issue We are experiencing an issue where the test execution settings dialog (Basic Settings/Advanced Settings) appears completely blank,preventing users from modifying configuration settings. We are currently investigating this with the highest priority. We apologize for the inconvenience, but if you need urgent access, please use the workaround below. Affected Screens: ・Test Case Edit Screen: Test Execution Settings Dialog (Basic Settings/Advanced Settings) ・Batch Run Settings Screen: Test Execution Settings Dialog (Basic Settings/Advanced Settings) Workaround: You can view the test execution settings dialog normally by following these steps: 1\. Add a new pattern on the batch run settings screen 2\. Reload the page 3\. Open the batch run settings screen again We sincerely apologize for the inconvenience. We will provide updates on the MagicPod StatusPage as progress is made. .

2. resolved Feb 09, 2026, 04:12 AM UTC

   We have confirmed that the issue with the test execution settings dialog has been resolved. We are now closing this matter as complete. We sincerely apologize for any inconvenience this may have caused. We will continue to implement measures internally to prevent recurrence..

Read the full incident report →

Started Dec 20, 2025, 02:32 AM UTC· resolved Dec 22, 2025, 12:22 AM UTC

1. investigating Dec 20, 2025, 02:32 AM UTC

   We are currently experiencing issues that prevent uses of the cloud browser. Our team is actively investigating the situation. .

2. monitoring Dec 20, 2025, 03:14 AM UTC

   We have completed the necessary actions to resolve the issues with the cloud browser outage and have successfully restored system functionality. The system is now under a 24-hour observation period to ensure stable operation. ■ Recovery Details We had released the new version of MagicPod, but it did not work correctly. Therefore, we discarded the released version and rolled back to the old version. We will release the new version again after identifying the cause of the trouble. We sincerely apologize for the inconvenience this has caused..

3. resolved Dec 22, 2025, 12:22 AM UTC

   📋 Completion of Observation Period: Cloud browser We are pleased to inform you that the observation period for issue of the cloud browser 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. .

Read the full incident report →

Started Dec 01, 2025, 04:47 AM UTC· resolved Dec 02, 2025, 06:00 AM UTC

1. monitoring Dec 01, 2025, 04:47 AM UTC

   ✅ Recovery and Monitoring Status: The test case editing screen does not open. On 1 December, around 11:30, an issue occurred in some environments where the cloud browser failed to open, preventing test editing. The cause of this issue has been identified and the system has been restored. The system is currently undergoing a 24-hour observation period to confirm stable operation. Please note that the system operated without issues for BatchRun during the aforementioned period. ■ Recovery Details \- Service restoration of the test case editing 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..

2. resolved Dec 02, 2025, 06:00 AM UTC

   📋 Completion of Observation Period: The test case editing screen does not open We are pleased to inform you that the observation period for ”The test case editing screen does not open” 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. .

Read the full incident report →

Started Nov 19, 2025, 03:12 AM UTC· resolved Nov 20, 2025, 06:03 AM UTC

1. identified Nov 19, 2025, 03:12 AM UTC

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

2. monitoring Nov 19, 2025, 04:53 AM UTC

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

3. resolved Nov 20, 2025, 06:03 AM UTC

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

Read the full incident report →

Started Oct 31, 2025, 09:16 AM UTC· resolved Nov 04, 2025, 01:00 AM UTC

1. investigating Oct 31, 2025, 09:16 AM UTC

   🚨 Notice of Service Disruption: Generative AI Features We are currently experiencing an outage affecting our Generative AI features, and they are temporarily unavailable. The cause of the issue is under investigation. ■ Affected Services \* MagicPod Autopilot \* AI Assertion \* The cause has been identified, and recovery is expected by tomorrow or later. We kindly ask that you refrain from using the Generative AI features until the issue is resolved. We sincerely apologize for the inconvenience. Updates will be provided on the MagicPod Status Page as progress is made. .

2. monitoring Nov 01, 2025, 12:34 AM UTC

   ✅ Recovery: The incident about Generative AI Features We have completed the necessary actions to resolve the issues with Generative AI Features and have successfully restored system functionality. The system is now under a 24-hour observation period to ensure stable operation. ■ Recovery Details \- The feature had been unable to access because it had passed the usage limit of the AI model. It was automatically recovered as time passed. We sincerely apologize for the inconvenience this has caused. We are committed to providing stable service moving forward by reviewing our usage and account management, as well as striving to raise our limits. .

3. resolved Nov 04, 2025, 01:00 AM UTC

   📋 Completion of Observation Period: The incident about Generative AI Feature We are pleased to inform you that the observation period, 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. .

Read the full incident report →

Started Oct 23, 2025, 02:25 AM UTC· resolved Oct 23, 2025, 01:43 PM UTC

1. monitoring Oct 23, 2025, 02:25 AM UTC

   🚨Recovery and Monitoring Status: Server Access Issues✅ We experienced a temporary inability to access the MagicPod server last night, but we have completed our response and the system has now been restored. We are currently in a 24-hour observation period to confirm stable operation. ■ Incident Details and Recovery \- Resolved server access issues caused by last night's release operation \- Addressed the problem that occurred between 22:39 and 22:43 This issue is similar to the problem that occurred on October 11th. We had been preparing a release to fix this issue, but unfortunately, it recurred before we could implement the fix. We plan to release the fix this weekend. If no issues occur during the observation period, we will consider this matter fully resolved. We sincerely apologize for the delayed notification regarding this incident. We will review and reinforce our notification process. We apologize for any inconvenience this may have caused. We will continue our efforts to provide stable service..

2. resolved Oct 23, 2025, 01:43 PM UTC

   📋 Completion of Observation Period We are pleased to inform you that the observation period for the outage that occurred yesterday 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. .

Read the full incident report →