We are currently experiencing and issue with delivery of Email messages through our email provider(s).
The team are currently investigating the issue and will provide an update soon.
Thank you for you patience.
OASIS Product Team
We identified the issue causing the issues with OASIS and currently implementing an appropriate mitigation.
We will continue to monitor this issue over the next few hours.
Thank you for you patience.
OASIS Product Team
We now have more detail on the cause of the email delays.
Our sending logs show that Microsoft mail servers are temporarily rejecting incoming messages from our provider with the following responses:
451 4.3.2 Temporary server error. Please try again later
451 4.7.500 Server busy. Please try again later
Both of these are temporary deferrals issued by Microsoft rather than permanent failures. They instruct the sending server to hold the message and retry, which is what is producing the delays being seen.
This confirms the issue sits with delivery into Microsoft hosted mailboxes and not with our platform or with our sending provider. It is consistent with the delays continuing after we moved from AuthSMTP to SMTP2GO.
Email is not being lost. Deferred messages remain queued and are retried automatically until Microsoft accepts them. SMTP2GO is continuing to raise and track this with Microsoft.
We will post a further update as the situation changes.
OASIS Product Team
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
Here is a status page incident you can post, drafted for a client facing audience.
Our SMS provider, Textmagic, is currently experiencing a service outage caused by an issue at their upstream server provider. The outage affects all of their services, including outbound SMS.
As a knock on effect, OASIS is currently unable to deliver SMS messages. This impacts:
- Multi factor authentication codes sent by SMS
- Any SMS notifications or alerts configured within your OASIS system
OASIS itself remains fully available and all other functionality is working normally. Users who have an authenticator app registered for multi factor authentication can continue to sign in as usual. Any messages queued during the outage are expected to be delivered once Textmagic restore service.
Textmagic have confirmed they are working on a fix. We are monitoring their status page and will update this incident as soon as we have more information.
If you are unable to sign in and have no alternative authentication method available, please contact the IT Works support desk.
Textmagic status page: https://status.textmagic.com/incidents/v71g6y6bgn25
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
We are aware of an issue affecting the delivery of SMS messages sent from OASIS. This is caused by a service disruption at our SMS provider, TextMagic, resulting from an outage at one of their external network providers. You can follow their progress on the TextMagic status page.
Users are affected in two ways:
Signing in with SMS multi-factor authentication — verification codes sent by text message may be delayed or may not arrive. If it is critical that you have access to OASIS during SMS outages such as this, we would recommend using a One Time Code (OTC) authenticator app rather than SMS.
Outbound SMS notifications — any text messages sent from OASIS (for example, appointment reminders or notifications to service users) may be delayed or fail to deliver while the issue is ongoing. Please consider using alternative contact methods for anything time-sensitive.
No OASIS systems or data are affected, this is limited to SMS delivery. TextMagic are investigating as a high priority, and we will post an update as soon as the issue is resolved.
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
We are aware users are experiencing increased error messages with OASIS from our internal monitoring system.
The team identified routine internal maintenance process not operating as expected.
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
We are aware users are experiencing access issues with OASIS and reports we have received from clients directly.
This will be observable when interacting with OASIS by saving and navigating around.
We are investigating the issue which we currently believe to be related to a Cloudflare outage.
We will provide an update soon.
OASIS Product Team
We identified the issue causing the access issue with OASIS, it relates to a Cloudflare outage. They haven't formally acknowledged this on their status portal but they are having ongoing issues.
OASIS is sporadically accessible we will continue to monitor any update from Cloudflare.
Thank you for you patience.
OASIS Product Team
Cloudflare have provided an update on their status page acknowledging a global network issues. Cloudflare Status
We will continue to monitor the progress and provide updates as necessary.
OASIS Product Team
OASIS is continuing to experience sporadic access issues as a result of the Cloudflare outage.
There have been an number of updates on the Cloudflare status page indicating they are seeing services recover as they continue remediation efforts. Cloudflare Status - Cloudflare Global Network experiencing issues
We will provide further updates as soon as we have them.
OASIS Product Team
Cloudflare have identified the issue impacting on their global network outage and are currently implementing a fix. Cloudflare Status - Cloudflare Global Network experiencing issues
We will provide further updates as they are available to us.
OASIS Product Team
We have received confirmation from Cloudflare that their global network issue has been resolved. OASIS services are now fully available and users are able to access the platform again.
This incident will remain open in a monitoring phase so that we can keep you informed of any changes to the current status as it remains open and being monitored by Cloudflare.
Cloudflare is a fundamental part of how the modern internet operates. Their infrastructure supports a very large proportion of global internet traffic and underpins the delivery of countless online services. As a result, issues within their network, although rare, can have far reaching effects that extend well beyond any single provider. While we allowed Cloudflare the necessary time to restore their systems, we were also preparing internally and assessing our options should the disruption have continued for a longer period.
We appreciate your patience throughout this incident.
OASIS Product Team
Following monitoring we are marking this issue as resolved as Cloudflare have closed of the issue.
OASIS Product Team
We are aware users are experiencing performance issues with OASIS from our internal monitoring system and reports we have received from clients directly.
This will be observable when interacting with OASIS by saving and navigating around or an increased number of application errors presenting to users.
The team are currently working to identify the the cause of the performance issue and will provide an update to the incident soon.
OASIS Product Team
We are still investigating the root cause of the performance issue. However, OASIS is operating as expected. We will post an update on the root cause soon.
Thank you for you patience.
OASIS Product Team
We are pleased to confirm that this issue has now been resolved. The investigation found that the cause was increased CPU load from encryption processes used when removing data from completed client migrations.
To help prevent this from happening again, these processes will now be carried out outside periods of peak use on OASIS.
Thank you for your patience and understanding.
OASIS Support Team
We have been made aware the OASIS report wizard is not applying filters correctly. The issue has been identified and will apply a patch to OASIS this evening.
We apologise for any inconvenience this has caused and will provide an update when a fix for this is deployed tonight.
OASIS Product Team
We have deployed the OASIS Report Wizard fixes to OASIS so filters should be apply correctly now.
OASIS Product Team
We are aware users are experiencing performance issues with OASIS from our internal monitoring system and reports we have received from clients directly.
This will be observable when interacting with OASIS by saving and navigating around or an increased number of application errors presenting to users.
The team are currently working to identify the the cause of the performance issue and will provide an update to the incident soon.
OASIS Product Team
We have identified the server causing the system timeouts. We have brought this system offline while we restart the services and will attempt to integrate back into the platform as soon as the processes are online.
Thank you for you patience.
OASIS Product Team
The server responsible for the issue has been reinstated. We will continue to monitor OASIS closely for any unusual behaviour.
We apologise for any inconvenience this incident may have caused.
OASIS Product Team
This issue has now been resolved.
We are aware of an issue with users using linked accounts being asked to login when moving between deployments.
The team are investigating this issue and will provide an update shortly.
Apologies for any inconvenience caused.
OASIS product Team
We have rolled out an update to address the issue with linked account operations.
The team will monitor the issue for the next 24 hours.
OASIS Product Team
Issue has been resolved.
We are aware of an issue in OASIS when an organisation is using the functionality to stream documents for compatible files types is enabled. This issue will present as an error when you click on the uploaded document.
Our team are currently looking into this and will provide an update in the next hour.
Thank you for your patience.
OASIS Product Team
This issue has been resolved.
OASIS Product Team