Identified - Processor rebooted H104 working. H102 still having issues including Projector Temp warnings.
Last update on
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams. For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS — will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. The AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.
Last update on
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 19, 2026 - 02:00 UTC
Last update on
The monitor is down in the following regions: us-east and us-west
Last update on
Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. While we work on the permanent fix, we recommend impacted users upgrade to the latest Outlook version. Current status: We've identified a code issue within a recent Microsoft Teams Meeting Add-in update under version 26043.2016.4478.2773, which is causing a compatibility issue with classic Outlook, and resulting in functionality issues. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook, though we recommend affected users that are on the latest updated Microsoft Teams version to also upgrade to the latest Outlook version to avoid further complications. We're working on deploying a fix to resolve the compatibility issue, and we anticipate being able to provide a remediation timeline by our next scheduled update. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams Meeting Add-in version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Thursday, March 19, 2026, at 10:30 AM UTC
Last update on
A fix has been implemented and we are monitoring the results.
Last update on
Cloud & Infrastructure Providers
Increased Error Rates
Amazon Web Services (Cloud Infrastructure)
MAD (Madrid) on 2026-03-19
Cloudflare (Cloud Infrastructure)
Google Cloud (Cloud Infrastructure)
Microsoft Azure (Cloud Infrastructure)
Communication & Collaboration Tools
BrightArrow Login
Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled
Exchange Online (Email Service)
Microsoft 365 suite (Email Services & Other)
Barracuda (Email Protection)
Buckley: Zoom Phone System
Google Workspace (Drive, Docs, Classroom, etc.)
Zoom (Phones, Web Conferencing)
Monitors
Benevity
Transact (G-Card, Campus Cash)
Apple School Manager (ASM) Login
ATT (Internet Service Provider)
Buckley: Cisco ISE (Identity Services Engine)
Buckley: Disney Pavilion Building
Buckley: Entertainment Checklist (onsite access only)
Buckley: Hillside Building
Buckley: LS Admin + Classroom E-6
Buckley: LS Classroom 7-13
Buckley: LS Science Center
Buckley: ManageEngine (Self-service password portal)
Buckley: Operations Building
Buckley: Printing Services
Buckley: Web Filter Appliance(s)
Buckley: Wi-Fi Controller(s)
Buckley: Yana Agapitova (LS Assembly)
CampBrain (Auxiliary Programs)
Clarity Login (Financial Aid)
College Board AP Students
ExploreLearning (Reflex Math Subscription)
Follett Software (Library Services)
GoFundMe Pro Login (Giving)
Graduway (Alumni Platform)
Helper Helper App Login (Community Service App)
Microsoft Entra (Authentication, SSO, MFA)
PTC Wizard (Parent Teacher Conference Portal)
ReadySub Login (Substitute Portal)
SchoolPass (Transportation, Visitor Management)
Scoir (College Counseling Service)
Spectrum (Internet Service Provider)
SysCloud (Backup Service)
Wix (Technology Service Portal)
The Buckley School Website