Mondoze Status - Incident history https://mondoze.instatus.com Mondoze Thu, 13 Aug 2026 17:18:00 +0000 Service Disruption – Upstream Peering Issue (Resolved) Type: Maintenance Duration: 26 days, 9 hours and 44 minutes Affected Components: MY01 Aug 14, 03:51:43 GMT+0 - Completed - **Update:** We experienced intermittent connectivity issues affecting some clients and regions due to a peering issue with one of our upstream uplink providers. **Incident window:** Aug 14, 2026, 1:18 AM – 6:37 AM (GMT+8) Services have been fully restored as of 6:37 AM (GMT+8). We are continuing to monitor closely with our uplink provider to ensure stability. We apologize for any inconvenience caused. If you're still experiencing issues, please contact our support team. Type: Maintenance

Duration: 26 days, 9 hours and 44 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>03:51:43</var> GMT+0</small><br><strong>Completed</strong> - **Update:** We experienced intermittent connectivity issues affecting some clients and regions due to a peering issue with one of our upstream uplink providers. **Incident window:** Aug 14, 2026, 1:18 AM – 6:37 AM (GMT+8) Services have been fully restored as of 6:37 AM (GMT+8). We are continuing to monitor closely with our uplink provider to ensure stability. We apologize for any inconvenience caused. If you're still experiencing issues, please contact our support team..</p> ]]> Thu, 13 Aug 2026 17:18:00 +0000 https://mondoze.instatus.com/maintenance/cmsseug5q03nz0zqx8awn4k8b https://mondoze.instatus.com/maintenance/cmsseug5q03nz0zqx8awn4k8b Scheduled Maintenance Notice Type: Maintenance Duration: 8 hours and 42 minutes Affected Components: MY01 Jul 2, 11:12:58 GMT+0 - Identified - # **Scheduled Maintenance Notice** **Dear Valued Customers,** Please be advised that our data center provider will be carrying out scheduled infrastructure maintenance involving the replacement of the facility’s Generator and Automatic Transfer Switch (ATS). To facilitate this work, a planned power shutdown will take place during the following period: **Maintenance Window** * **Start:** 2 July 2026, 9:00 PM (MYT) * **End:** 3 July 2026, 7:00 AM (MYT) **Service Impact** During the maintenance window, services hosted in the affected data center may be temporarily unavailable. This maintenance may affect: * All ISP Related Services Our engineers will closely monitor the maintenance and will restore all services immediately after the data center confirms that power has been fully restored. This maintenance is necessary to improve the reliability and resilience of the data center’s power infrastructure. We apologize for any inconvenience and appreciate your patience and understanding. If you have any questions or require assistance, please contact our support team before the scheduled maintenance begins. Thank you for your continued support. **Support Team** Jul 2, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 2, 21:41:37 GMT+0 - Completed - # **Maintenance Completed** **Dear Valued Customers,** We are pleased to confirm that the scheduled data center maintenance has been successfully completed. All affected services have been fully restored and are operating normally. Our team has completed the necessary post-maintenance checks to ensure service stability. We appreciate your patience and understanding throughout the maintenance window. If you experience any unexpected issues or require assistance, please do not hesitate to contact our support team. Thank you **Support Team** Type: Maintenance

Duration: 8 hours and 42 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>11:12:58</var> GMT+0</small><br><strong>Identified</strong> - # **Scheduled Maintenance Notice** **Dear Valued Customers,** Please be advised that our data center provider will be carrying out scheduled infrastructure maintenance involving the replacement of the facility’s Generator and Automatic Transfer Switch (ATS). To facilitate this work, a planned power shutdown will take place during the following period: **Maintenance Window** * **Start:** 2 July 2026, 9:00 PM (MYT) * **End:** 3 July 2026, 7:00 AM (MYT) **Service Impact** During the maintenance window, services hosted in the affected data center may be temporarily unavailable. This maintenance may affect: * All ISP Related Services Our engineers will closely monitor the maintenance and will restore all services immediately after the data center confirms that power has been fully restored. This maintenance is necessary to improve the reliability and resilience of the data center’s power infrastructure. We apologize for any inconvenience and appreciate your patience and understanding. If you have any questions or require assistance, please contact our support team before the scheduled maintenance begins. Thank you for your continued support. **Support Team**.</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>21:41:37</var> GMT+0</small><br><strong>Completed</strong> - # **Maintenance Completed** **Dear Valued Customers,** We are pleased to confirm that the scheduled data center maintenance has been successfully completed. All affected services have been fully restored and are operating normally. Our team has completed the necessary post-maintenance checks to ensure service stability. We appreciate your patience and understanding throughout the maintenance window. If you experience any unexpected issues or require assistance, please do not hesitate to contact our support team. Thank you **Support Team**.</p> ]]> Thu, 2 Jul 2026 13:00:00 +0000 https://mondoze.instatus.com/maintenance/cmr3eo9gt00dm0kmsf9xrcc90 https://mondoze.instatus.com/maintenance/cmr3eo9gt00dm0kmsf9xrcc90 MY01 outage Type: Incident Duration: 6 minutes Affected Components: MY01 Dec 8, 12:02:36 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Dec 8, 12:08:24 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>12:02:36</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>12:08:24</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 8 Dec 2025 12:02:36 +0000 https://mondoze.instatus.com/incident/cmix3qme301ptvkewis5a0uoc https://mondoze.instatus.com/incident/cmix3qme301ptvkewis5a0uoc SG01, MY01 outage Type: Incident Duration: 1 minute Affected Components: SG01, MY01 Oct 30, 20:16:42 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 30, 20:17:43 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 minute

Affected Components: ,

<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:16:42</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:17:43</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 30 Oct 2025 20:16:42 +0000 https://mondoze.instatus.com/incident/cmhdv7tad005pvo3zomv4r5vz https://mondoze.instatus.com/incident/cmhdv7tad005pvo3zomv4r5vz MY01 outage Type: Incident Duration: 1 minute Affected Components: MY01 Oct 30, 20:16:39 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 30, 20:17:29 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:16:39</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:17:29</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 30 Oct 2025 20:16:39 +0000 https://mondoze.instatus.com/incident/cmhdv7qzf003wlwxq1j4bfi69 https://mondoze.instatus.com/incident/cmhdv7qzf003wlwxq1j4bfi69 SG01, MY01 outage Type: Incident Duration: 2 minutes Affected Components: SG01, MY01 Oct 26, 10:12:41 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 26, 10:14:38 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 2 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>10:12:41</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>10:14:38</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Sun, 26 Oct 2025 10:12:41 +0000 https://mondoze.instatus.com/incident/cmh7jvmqi02yjghe826g2t5a3 https://mondoze.instatus.com/incident/cmh7jvmqi02yjghe826g2t5a3 SG01 outage Type: Incident Duration: 1 minute Affected Components: SG01 Oct 26, 06:08:01 GMT+0 - Investigating - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 26, 06:08:35 GMT+0 - Resolved - SG01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>06:08:01</var> GMT+0</small><br><strong>Investigating</strong> - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>06:08:35</var> GMT+0</small><br><strong>Resolved</strong> - SG01 is now operational! This update was created by an automated monitoring service..</p> ]]> Sun, 26 Oct 2025 06:08:01 +0000 https://mondoze.instatus.com/incident/cmh7b4zot01wylvy4obxe5tmu https://mondoze.instatus.com/incident/cmh7b4zot01wylvy4obxe5tmu SG01 outage Type: Incident Duration: 4 minutes Affected Components: SG01 Oct 21, 01:34:39 GMT+0 - Investigating - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 21, 01:38:46 GMT+0 - Resolved - SG01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>01:34:39</var> GMT+0</small><br><strong>Investigating</strong> - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>01:38:46</var> GMT+0</small><br><strong>Resolved</strong> - SG01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 21 Oct 2025 01:34:39 +0000 https://mondoze.instatus.com/incident/cmgzw665g0133t0wi012pt2w5 https://mondoze.instatus.com/incident/cmgzw665g0133t0wi012pt2w5 SG01, MY01 outage Type: Incident Duration: 4 minutes Affected Components: SG01, MY01 Oct 21, 01:34:38 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 21, 01:38:36 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>01:34:38</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>01:38:36</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 21 Oct 2025 01:34:38 +0000 https://mondoze.instatus.com/incident/cmgzw657a0833zejaleqd7mqg https://mondoze.instatus.com/incident/cmgzw657a0833zejaleqd7mqg MY01 outage Type: Incident Duration: 13 days, 18 hours and 17 minutes Affected Components: MY01 Oct 21, 01:34:34 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Nov 3, 19:51:46 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 13 days, 18 hours and 17 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>01:34:34</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>19:51:46</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 21 Oct 2025 01:34:34 +0000 https://mondoze.instatus.com/incident/cmgzw62mx017796rjushfquq6 https://mondoze.instatus.com/incident/cmgzw62mx017796rjushfquq6 SG01 outage Type: Incident Duration: 4 minutes Affected Components: SG01 Oct 6, 09:54:37 GMT+0 - Investigating - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 6, 09:58:27 GMT+0 - Resolved - SG01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>09:54:37</var> GMT+0</small><br><strong>Investigating</strong> - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>09:58:27</var> GMT+0</small><br><strong>Resolved</strong> - SG01 is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 6 Oct 2025 09:54:37 +0000 https://mondoze.instatus.com/incident/cmgeyfd1503z0xl98dfvvjjx6 https://mondoze.instatus.com/incident/cmgeyfd1503z0xl98dfvvjjx6 SG01, MY01 outage Type: Incident Duration: 4 minutes Affected Components: SG01, MY01 Jul 2, 07:10:39 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 2, 07:14:36 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:10:39</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:14:36</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 2 Jul 2025 07:10:39 +0000 https://mondoze.instatus.com/incident/cmclmaprc006y6o2vwzedi9w2 https://mondoze.instatus.com/incident/cmclmaprc006y6o2vwzedi9w2 SG01 outage Type: Incident Duration: 4 minutes Affected Components: SG01 Jul 2, 07:10:38 GMT+0 - Investigating - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 2, 07:14:41 GMT+0 - Resolved - SG01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:10:38</var> GMT+0</small><br><strong>Investigating</strong> - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:14:41</var> GMT+0</small><br><strong>Resolved</strong> - SG01 is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 2 Jul 2025 07:10:38 +0000 https://mondoze.instatus.com/incident/cmclmapex00z4lj483jb1wcli https://mondoze.instatus.com/incident/cmclmapex00z4lj483jb1wcli MY01 outage Type: Incident Duration: 1 minute Affected Components: MY01 Jul 2, 07:10:37 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 2, 07:11:28 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:10:37</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:11:28</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 2 Jul 2025 07:10:37 +0000 https://mondoze.instatus.com/incident/cmclmao3f00c5v26rfjzzf56k https://mondoze.instatus.com/incident/cmclmao3f00c5v26rfjzzf56k SG01, MY01 outage Type: Incident Duration: 4 minutes Affected Components: MY01, SG01 Jul 2, 07:10:32 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 2, 07:14:30 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:10:32</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:14:30</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 2 Jul 2025 07:10:32 +0000 https://mondoze.instatus.com/incident/cmclmakie00bxv26r7m89d0o6 https://mondoze.instatus.com/incident/cmclmakie00bxv26r7m89d0o6 MY01 outage Type: Incident Duration: 16 minutes Affected Components: MY01 Jul 1, 23:41:47 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Jul 1, 23:25:43 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 16 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>23:41:47</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>23:25:43</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 23:25:43 +0000 https://mondoze.instatus.com/incident/cmcl5ot2q001fflwmmfl6l3c3 https://mondoze.instatus.com/incident/cmcl5ot2q001fflwmmfl6l3c3 MY01 outage Type: Incident Affected Components: MY01 Jul 1, 22:22:45 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 1, 22:22:49 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Affected Components:

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:45</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:49</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 22:22:45 +0000 https://mondoze.instatus.com/incident/cmcl3fuck00tqxilp6lkznm98 https://mondoze.instatus.com/incident/cmcl3fuck00tqxilp6lkznm98 MY01 outage Type: Incident Affected Components: MY01 Jul 1, 22:22:45 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 1, 22:22:49 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Affected Components:

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:45</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:49</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 22:22:45 +0000 https://mondoze.instatus.com/incident/cmcl3fttc01kbyv0f62xoa4if https://mondoze.instatus.com/incident/cmcl3fttc01kbyv0f62xoa4if SG01, MY01 outage Type: Incident Affected Components: SG01, MY01 Jul 1, 22:22:36 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 1, 22:22:38 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Affected Components: ,

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:36</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:38</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 22:22:36 +0000 https://mondoze.instatus.com/incident/cmcl3fn5j01ftyv0fyotvprnp https://mondoze.instatus.com/incident/cmcl3fn5j01ftyv0fyotvprnp MY01 outage Type: Incident Duration: 11 hours and 39 minutes Affected Components: MY01 Jul 1, 10:43:42 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 1, 22:22:43 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 11 hours and 39 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>10:43:42</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:43</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 10:43:42 +0000 https://mondoze.instatus.com/incident/cmckeguzu0065qlr0r62sutz1 https://mondoze.instatus.com/incident/cmckeguzu0065qlr0r62sutz1 MY01 outage Type: Incident Duration: 11 hours and 39 minutes Affected Components: MY01 Jul 1, 10:43:36 GMT+0 - Investigating - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 1, 22:22:45 GMT+0 - Resolved - MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 11 hours and 39 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>10:43:36</var> GMT+0</small><br><strong>Investigating</strong> - MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:45</var> GMT+0</small><br><strong>Resolved</strong> - MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 10:43:36 +0000 https://mondoze.instatus.com/incident/cmckegpqo005zqlr0eufj7njl https://mondoze.instatus.com/incident/cmckegpqo005zqlr0eufj7njl SG01 outage Type: Incident Duration: 11 hours and 39 minutes Affected Components: SG01 Jul 1, 10:43:36 GMT+0 - Investigating - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 1, 22:22:38 GMT+0 - Resolved - SG01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 11 hours and 39 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>10:43:36</var> GMT+0</small><br><strong>Investigating</strong> - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:38</var> GMT+0</small><br><strong>Resolved</strong> - SG01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 10:43:36 +0000 https://mondoze.instatus.com/incident/cmckegpq40019qjejrnreysti https://mondoze.instatus.com/incident/cmckegpq40019qjejrnreysti SG01, MY01 outage Type: Incident Duration: 11 hours and 39 minutes Affected Components: MY01, SG01 Jul 1, 10:43:34 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 1, 22:22:45 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 11 hours and 39 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>10:43:34</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:22:45</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 10:43:34 +0000 https://mondoze.instatus.com/incident/cmckego720016g1m0gbopezzg https://mondoze.instatus.com/incident/cmckego720016g1m0gbopezzg SG01, MY01 outage Type: Incident Duration: 36 minutes Affected Components: SG01, MY01 Jul 1, 08:46:43 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 1, 09:22:39 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 36 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>08:46:43</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>09:22:39</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 08:46:43 +0000 https://mondoze.instatus.com/incident/cmckaaeik000lxun2imgsmgb1 https://mondoze.instatus.com/incident/cmckaaeik000lxun2imgsmgb1 SG01, MY01 outage Type: Incident Duration: 36 minutes Affected Components: SG01, MY01 Jul 1, 09:22:31 GMT+0 - Resolved - SG01, MY01 is now operational! This update was created by an automated monitoring service. Jul 1, 08:46:36 GMT+0 - Investigating - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 36 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>09:22:31</var> GMT+0</small><br><strong>Resolved</strong> - SG01, MY01 is now operational! This update was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>08:46:36</var> GMT+0</small><br><strong>Investigating</strong> - SG01, MY01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Tue, 1 Jul 2025 08:46:36 +0000 https://mondoze.instatus.com/incident/cmckaa97w005ly45op54z718a https://mondoze.instatus.com/incident/cmckaa97w005ly45op54z718a SG01 outage Type: Incident Duration: 1 minute Affected Components: SG01 Jun 26, 22:06:33 GMT+0 - Investigating - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 26, 22:07:34 GMT+0 - Resolved - SG01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>22:06:33</var> GMT+0</small><br><strong>Investigating</strong> - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>22:07:34</var> GMT+0</small><br><strong>Resolved</strong> - SG01 is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 26 Jun 2025 22:06:33 +0000 https://mondoze.instatus.com/incident/cmcdxnqvm0031q4n9k0gg3abj https://mondoze.instatus.com/incident/cmcdxnqvm0031q4n9k0gg3abj SG01 outage Type: Incident Duration: 20 minutes Affected Components: SG01 Jun 13, 07:16:40 GMT+0 - Investigating - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 13, 07:36:43 GMT+0 - Resolved - SG01 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 20 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>07:16:40</var> GMT+0</small><br><strong>Investigating</strong> - SG01 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>07:36:43</var> GMT+0</small><br><strong>Resolved</strong> - SG01 is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 13 Jun 2025 07:16:40 +0000 https://mondoze.instatus.com/incident/cmbuh5a3p00e1899o8t283nju https://mondoze.instatus.com/incident/cmbuh5a3p00e1899o8t283nju