Email delivery has returned to normal. Microsoft has accepted responsibility for the current email delays. More details can be found on their status page and below:

Issue ID: EX1467029

Affected services: Exchange Online

Status: Service degradation

Issue type: Incident

Start time: Sep 4, 2026, 10:19 PM GMT+12

Microsoft is no longer deferring messages from our sending provider, and the queue of delayed messages has now cleared. Delivery times to Microsoft hosted mailboxes are back within expected levels.

Summary of the incident: outbound email began experiencing delivery problems while sending was handled by AuthSMTP. We moved sending to SMTP2GO, which improved delivery for a period before delays returned. Sending logs confirmed that Microsoft mail servers were temporarily deferring messages with 451 4.3.2 Temporary server error and 451 4.7.500 Server busy. These were temporary responses on the Microsoft side that caused messages to be queued and retried rather than failing.

No email was lost during the incident. Messages that were delayed have since been delivered, although some may have arrived out of order or later than the time they were sent.

OASIS Product Team

Textmagic have confirmed their service is fully restored and SMS delivery from OASIS has returned to normal. All queued messages have now been sent. Thank you for your patience during this third party outage.

OASIS Product Team

Following yesterday evening's issue affecting the delivery of SMS messages sent from OASIS, we can confirm that service has been restored. Our SMS provider, TextMagic, resolved the outage at their external network provider some time ago, and SMS delivery has been operating normally since.

SMS multi-factor authentication — verification codes are being delivered as normal, and users can sign in using SMS MFA without issue.

Outbound SMS notifications — text messages sent from OASIS are being delivered as normal. Please note that messages sent during yesterday evening's outage may not have been delivered, so if you sent anything time-sensitive during that period, we recommend checking with the recipient or re-sending where appropriate.

As a reminder, if reliable access to OASIS is critical for you, we recommend using a One Time Code (OTC) authenticator app as your MFA method, as this does not depend on SMS delivery.

Thank you for your patience, and apologies for the delay in posting this update.

OASIS Product Team

All systems now operational.

The root cause was a scaling operation which triggered an SQL instance restart, an operation which often happens during Microsoft's maintenance window without service interruption.

An ongoing process triggered a protection mechanism called rapid fail protection disabled the applications as a result of excessive error reporting.

We apologise for any inconvenience.

OASIS Product Team

Following monitoring we are marking this issue as resolved  as Cloudflare have closed of the issue.

OASIS Product Team