ORU IT Systems Status Page

Warn

Amazon Web Services

We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.

Last update on Jun 15, 2026 7:00 PM

Warn

Cloudflare

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun 15, 2026 - 18:00 UTC

Last update on Jun 15, 2026 7:00 PM

Warn

Adobe Document Cloud

Last update on Jun 15, 2026 7:02 PM

Warn

Google Cloud

**Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. Initial traffic mitigations have yielded positive results for some Cloud customers. In parallel, we are pursuing additional Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Further, we are augmenting out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India (expected to be done by Wednesday, 2026-06-17 PDT). We have optimized capacity across network backbones to increase available headroom. Additionally, we are further augmenting our Delhi backbone capacity (expected to be complete by Monday, 2026-06-15 PDT). We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Monday, 2026-06-15 17:00 PDT. **Symptoms** Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. **Workaround** There is no workaround at this time.

Last update on Jun 15, 2026 7:05 PM

Warn

Microsoft 365 Copilot Chat

Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully. Current status: We’re continuing to see failures in error logs provided by customers and internal service logs after the change reversion. While our review of the fresh set of error logs and our internal service health signals is ongoing, we’ll open more workstreams to mitigate the remaining impact based on our findings. Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues. Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact. Next update by: Monday, June 15, 2026, at 7:00 PM UTC

Last update on Jun 15, 2026 7:00 PM

Warn

OpenAI

We have identified that users are experiencing an error when attempting to create an account or logging in using Google OAuth for the impacted services. We are working on implementing a mitigation.

Last update on Jun 15, 2026 7:02 PM

Warn

Parchment

Notice: Learner Chat Currently Unavailable To ensure we can provide the best possible support during our current system updates, we have temporarily disabled our live chat feature. We are currently experiencing a high volume of inquiries regarding update enrollment failures and are working hard to resolve the issue. In the meantime, please reach out to us via a Support Ticket, and our team will get back to you as soon as possible. We appreciate your patience and look forward to bringing live chat back online soon.

Last update on Jun 15, 2026 7:05 PM

Warn

Salesforce

Salesforce has re-enabled integrations with Salesloft technologies, with the exception of any Drift app. Drift will remain disabled until further notice as part of our continued response to the security incident. This decision follows security measures and remediation steps implemented by Salesloft, which were independently validated by Mandiant. For full details and guidance from Salesforce, please continue to follow https://help.salesforce.com/s/articleView?id=005134951&type=1. For Salesloft’s latest investigation and remediation updates, see https://trust.salesloft.com/?uid=Update+on+Mandiant+Drift+and+Salesloft+Application+Investigations

Last update on Jun 15, 2026 7:04 PM