tag:mondoze.instatus.com,2005:/history Mondoze Status - Incident history 2026-08-13T17:18:00.000+00:00 Mondoze tag:mondoze.instatus.com,2005:Maintenance/cmsseug5q03nz0zqx8awn4k8b 2026-08-13T17:18:00.000+00:00 2026-08-13T22:46:00.000+00:00 Service Disruption – Upstream Peering Issue (Resolved) Type: Maintenance

Duration: 5 hours

Affected Components: MY01

Aug 13, 22:46:00 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..

]]> tag:mondoze.instatus.com,2005:Maintenance/cmr3eo9gt00dm0kmsf9xrcc90 2026-07-02T13:00:00.000+00:00 2026-07-02T11:12:58.359+00:00 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**.

]]> tag:mondoze.instatus.com,2005:Incident/cmix3qme301ptvkewis5a0uoc 2025-12-08T12:02:36.891+00:00 2025-12-08T12:02:36.908+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmhdv7tad005pvo3zomv4r5vz 2025-10-30T20:16:42.756+00:00 2025-10-30T20:16:42.768+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmhdv7qzf003wlwxq1j4bfi69 2025-10-30T20:16:39.770+00:00 2025-10-30T20:16:39.792+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmh7jvmqi02yjghe826g2t5a3 2025-10-26T10:12:41.562+00:00 2025-10-26T10:12:41.580+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmh7b4zot01wylvy4obxe5tmu 2025-10-26T06:08:01.707+00:00 2025-10-26T06:08:01.725+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmgzw665g0133t0wi012pt2w5 2025-10-21T01:34:39.267+00:00 2025-10-21T01:34:39.284+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmgzw657a0833zejaleqd7mqg 2025-10-21T01:34:38.037+00:00 2025-10-21T01:34:38.048+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmgzw62mx017796rjushfquq6 2025-10-21T01:34:34.713+00:00 2025-10-21T01:34:34.731+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmgeyfd1503z0xl98dfvvjjx6 2025-10-06T09:54:37.625+00:00 2025-10-06T09:54:37.645+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmclmaprc006y6o2vwzedi9w2 2025-07-02T07:10:39.335+00:00 2025-07-02T07:10:39.358+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmclmapex00z4lj483jb1wcli 2025-07-02T07:10:38.888+00:00 2025-07-02T07:10:38.907+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmclmao3f00c5v26rfjzzf56k 2025-07-02T07:10:37.178+00:00 2025-07-02T07:10:37.196+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmclmakie00bxv26r7m89d0o6 2025-07-02T07:10:32.533+00:00 2025-07-02T07:10:32.555+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmcl5ot2q001fflwmmfl6l3c3 2025-07-01T23:25:43.345+00:00 2025-07-01T23:41:47.348+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmcl3fuck00tqxilp6lkznm98 2025-07-01T22:22:45.860+00:00 2025-07-01T22:22:45.877+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmcl3fttc01kbyv0f62xoa4if 2025-07-01T22:22:45.167+00:00 2025-07-01T22:22:45.178+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmcl3fn5j01ftyv0fyotvprnp 2025-07-01T22:22:36.535+00:00 2025-07-01T22:22:36.558+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmckeguzu0065qlr0r62sutz1 2025-07-01T10:43:42.954+00:00 2025-07-01T10:43:42.964+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmckegpqo005zqlr0eufj7njl 2025-07-01T10:43:36.144+00:00 2025-07-01T10:43:36.165+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmckegpq40019qjejrnreysti 2025-07-01T10:43:36.124+00:00 2025-07-01T10:43:36.145+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmckego720016g1m0gbopezzg 2025-07-01T10:43:34.141+00:00 2025-07-01T10:43:34.165+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmckaaeik000lxun2imgsmgb1 2025-07-01T08:46:43.195+00:00 2025-07-01T08:46:43.219+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmckaa97w005ly45op54z718a 2025-07-01T08:46:36.332+00:00 2025-07-01T09:22:31.129+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmcdxnqvm0031q4n9k0gg3abj 2025-06-26T22:06:33.682+00:00 2025-06-26T22:06:33.698+00:00 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..

]]> tag:mondoze.instatus.com,2005:Incident/cmbuh5a3p00e1899o8t283nju 2025-06-13T07:16:40.932+00:00 2025-06-13T07:16:40.949+00:00 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..

]]>