UPDATE: May 24, 2022, 13:30 GMT +8
The root cause was isolated to a Web node in one of the server stacks.
Support teams confirmed that the issue was resolved following a full restart of the impacted server stack at 11:30am GMT +8.
The service was monitored after the restart and SMS are being processed successfully.
This will be the final notification for this incident.
