Duration: 3 hours

Affected Components: Cloud Browser, Generative AI Feature, MagicPod Web, Cloud Device

Feb 28, 04:00:00 GMT+0
Identified - Thank you for your continued use of MagicPod. Planned maintenance will be carried out on the MagicPod server during the following period. **Date and Time**: * Saturday, Feb 28, 04:00 - 07:00 UTC **Scope of Impact**: * During the above time period, MagicPod will be unavailable. * The exact duration of the outage may vary depending on the progress of the maintenance work. **Please note**: Please avoid creating tests and scheduling batch executions during the above time period. Should you have any queries, please do not hesitate to contact our support team..

Feb 28, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Feb 28, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 3 hours and 1 minute

Feb 9, 04:12:26 GMT+0
Resolved - 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..

Feb 9, 01:11:17 GMT+0
Investigating - 🚨 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. .

Duration: 2 hours

Affected Components: MagicPod Web

Feb 8, 02:00:00 GMT+0
Identified - Thank you for your continued use of MagicPod. Planned maintenance will be carried out on the MagicPod server during the following period. **Date and Time**: * Sunday, Feb 8, 02:00 - 04:00 UTC **Scope of Impact**: * During the above time period, MagicPod will be unavailable. * The exact duration of the outage may vary depending on the progress of the maintenance work..

Feb 8, 02:00:01 GMT+0
Identified - Maintenance is now in progress.

Feb 8, 04:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 4 hours

Affected Components: MagicPod Web, Cloud Browser, Generative AI Feature, Cloud Device

Jan 17, 04:00:00 GMT+0
Identified - Thank you for your continued use of MagicPod. Planned maintenance will be carried out on the MagicPod server during the following period. **Date and Time**: * Saturday, Jan 17, 04:00 - 08:00 UTC **Scope of Impact**: * During the above time period, MagicPod will be unavailable. * The exact duration of the outage may vary depending on the progress of the maintenance work. **Please note**: Please avoid creating tests and scheduling batch executions during the above time period. Should you have any queries, please do not hesitate to contact our support team..

Jan 17, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 17, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 1 day, 21 hours and 50 minutes

Affected Components: Cloud Browser

Dec 20, 02:32:16 GMT+0
Investigating - We are currently experiencing issues that prevent uses of the cloud browser. Our team is actively investigating the situation. .

Dec 20, 03:14:22 GMT+0
Monitoring - 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..

Dec 22, 00:22:34 GMT+0
Resolved - 📋 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. .

Duration: 13 hours and 42 minutes

Affected Components: Cloud Device

Dec 16, 16:00:00 GMT+0
Identified - Thank you for your continued use of MagicPod. Planned maintenance will be carried out on the cloud infrastructure utilised by MagicPod during the following period. **Date and Time**: * Wednesday, Dec 17, 01:00 - 05:00 UTC **Scope of Impact**: * Test execution on cloud devices will be unavailable for up to 15 minutes. * The exact duration of the outage may vary depending on the progress of the maintenance work. **Please note**: Please avoid scheduling batch executions during the above time period or adjust the timing accordingly. Should you have any queries, please do not hesitate to contact our support team..

Dec 16, 16:00:01 GMT+0
Identified - Maintenance is now in progress.

Dec 17, 05:41:41 GMT+0
Completed - Maintenance has completed successfully..

Duration: 1 hour

Affected Components: Cloud Device

Dec 5, 05:00:00 GMT+0
Identified - Thank you for your continued use of MagicPod. Planned maintenance will be carried out on the cloud infrastructure utilised by MagicPod during the following period. **Date and Time**: * Friday, Dec 5, 05:00 - 06:00 UTC **Scope of Impact**: * There may be a temporary increase in latency when executing or creating tests within the cloud environment. * The impact is expected to last approximately 10 minutes. **Please note**: If you have scheduled batch executions during the above timeframe, we recommend considering adjusting the execution times as a precaution. Should you have any queries, please do not hesitate to contact our support team..

Dec 5, 05:00:01 GMT+0
Identified - Maintenance is now in progress.

Dec 5, 06:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 1 day, 1 hour and 13 minutes

Affected Components: Cloud Browser

Dec 1, 04:47:44 GMT+0
Monitoring - ✅ 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..

Dec 2, 06:00:57 GMT+0
Resolved - 📋 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. .

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

Duration: 3 days, 15 hours and 44 minutes

Affected Components: Generative AI Feature

Oct 31, 09:16:23 GMT+0
Investigating - 🚨 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. .

Nov 4, 01:00:18 GMT+0
Resolved - 📋 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. .

Nov 1, 00:34:33 GMT+0
Monitoring - ✅ 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. .

Duration: 11 hours and 18 minutes

Affected Components: MagicPod Web

Oct 23, 02:25:42 GMT+0
Monitoring - 🚨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..

Oct 23, 13:43:36 GMT+0
Resolved - 📋 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. .