YCloud Outage History

Started Nov 05, 2026, 08:57 AM UTC· resolved Nov 05, 2026, 09:20 AM UTC

1. identified Nov 05, 2026, 08:57 AM UTC

   We are investigating elevated errors affecting the login, inbox.

2. identified Nov 05, 2026, 09:04 AM UTC

   We are continuing to investigate elevated errors, and are working with our infrastructure provider. We will provide another update as soon as we have more information.

3. monitoring Nov 05, 2026, 09:20 AM UTC

   A fix has been deployed for the issue affecting YCloud services and we are monitoring for recovery.

4. resolved Nov 05, 2026, 09:41 AM UTC

   All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

Read the full incident report →

Started Sep 15, 2026, 03:00 PM UTC· resolved Sep 15, 2026, 04:49 PM UTC

1. identified Sep 15, 2026, 03:00 PM UTC

   Hi valued customers, We are investigating an issue where messages may unable to send from YCloud Inbox. We have identified the root cause and are actively working on a fix. Best regards, YCloud Team

2. monitoring Sep 15, 2026, 03:35 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 15, 2026, 04:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 19, 2026, 08:59 AM UTC· resolved Jul 19, 2026, 09:37 AM UTC

1. identified Jul 19, 2026, 08:59 AM UTC

   We identified a WhatsApp Cloud API error. Some messages will response a '#200 OAuthException' error. More updates to follow shortly. Sun 19th July 17:00 UTC+8 YCloud Team

2. monitoring Jul 19, 2026, 09:32 AM UTC

   Monitoring The issue has been mitigated, and the affected services are recovering. We are continuing to monitor the situation closely to ensure service stability.

3. resolved Jul 19, 2026, 09:37 AM UTC

   Resolved The issue has been resolved, and all affected services are operating normally. We will continue to monitor system performance to ensure ongoing stability.

Read the full incident report →

Started Jun 12, 2026, 01:46 PM UTC· resolved Jun 12, 2026, 03:43 PM UTC

1. investigating Jun 12, 2026, 01:46 PM UTC

   At approximately 9:35 PM Beijing Time on June 12, the WhatsApp API appeared to experience a widespread outage. Further updates will follow as they become available.

2. resolved Jun 12, 2026, 03:43 PM UTC

   Around 23:38 (GTM+8), the fault was basically alleviated. Over the past period,Meta Platforms experienced a large-scale global outage , affecting services including but not limited to WhatsApp API, Meta Ads, Facebook Login, and related personal services such as Facebook and Instagram. For details on the progress and causes of the event, please follow: https://metastatus.com/whatsapp-business-api Based on past experience: Message requests that fail to send during a fault will not be automatically resent; if necessary, they need to be resent manually. User uplink messages during the fault period will most likely be retransmitted within a certain period in the future.

Read the full incident report →

Started May 19, 2026, 04:39 AM UTC· resolved May 19, 2026, 04:54 AM UTC

1. identified May 19, 2026, 04:39 AM UTC

   Currently, there appears to be a large-scale failure in the WhatsApp service. The fault is manifested as the absence of a sent receipt after message submission. Waiting for the WhatsApp team's update progress. YCloud Team

2. resolved May 19, 2026, 04:54 AM UTC

   【WhatsApp Service Alert 5.19】 Observation has now resumed, with the affected time period approximately from 12:00 to 12:45. Currently, it is observed that the WhatsApp service is backfilling webhook pushes. If there are no new issues, the alarm information will no longer be updated. YCloud Team

Read the full incident report →

Started Mar 25, 2026, 11:00 AM UTC· resolved Mar 25, 2026, 11:20 AM UTC

1. resolved Mar 25, 2026, 11:00 AM UTC

   During a rolling upgrade of our network acceleration nodes, an incorrect configuration by our operations team caused part of the traffic to fall back to the origin, resulting in a service disruption. The configuration has now been rolled back and the upgrade process has been stopped. Impact period: March 25, 19:00–19:20 GMT+8 Affected traffic: Approximately 30% of API requests We apologize for any inconvenience caused and are reviewing the process to prevent similar issues in the future.

Read the full incident report →

Started Mar 02, 2026, 06:10 PM UTC· resolved Mar 03, 2026, 03:38 AM UTC

1. identified Mar 02, 2026, 06:10 PM UTC

   Starting March 2, the delivery rate of Marketing template messages has significantly decreased, with a large number of failed code 131049 observed. This code (131049) indicates that Meta chose not to deliver the message to maintain a healthy ecosystem engagement. This issue has been confirmed by WhatsApp side, and they are working to resolve the issue. YCloud team will provide timely updates as soon as there is progress.

2. resolved Mar 03, 2026, 03:38 AM UTC

   The fix for the disruptions impacting Marketing Messages API has been deployed and this issue is now resolved. Thank you for your patience.

Read the full incident report →

Started Feb 27, 2026, 07:01 AM UTC· resolved Feb 27, 2026, 07:26 AM UTC

1. investigating Feb 27, 2026, 07:01 AM UTC

   We are currently investigating an issue that is causing some messages to time out and fail to send. Our engineering team is actively working on a resolution to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

2. resolved Feb 27, 2026, 07:26 AM UTC

   We have resolved the issue that caused message timeouts. This was due to a recent modification of our template API. We have rolled back the changes, and all services are now fully restored. We apologize for the disruption and thank you for your understanding.

Read the full incident report →

Started Feb 27, 2026, 07:01 AM UTC· resolved Feb 27, 2026, 07:37 AM UTC

1. investigating Feb 27, 2026, 07:01 AM UTC

   We are aware that some users are experiencing difficulties logging in. Our team is currently working to resolve this as quickly as possible. We apologize for the disruption and thank you for your understanding.

2. resolved Feb 27, 2026, 07:37 AM UTC

   We have resolved an issue that caused login failures for some users over a period of 37 minutes. This was due to a backend refactoring of our template functions.

Read the full incident report →