User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Education
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: MI1017017: Microsoft 365 & Exchange Online Connectivity Issues
Source: the vendor's status page · We are not affiliated with University of Alaska IT.
Estimated fix: Not enough University of Alaska IT history yet; similar Education outages lasted 2 h (median, typically 18 min–9 h; 11 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 59 min ago. Last stored result reached it in 826 ms.
Minor incident
MI1017017: Microsoft 365 & Exchange Online Connectivity Issues Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 06:00 | 0 | 0.0 | 502 ms | 0 |
| 08:00 | 0 | 0.0 | 545 ms | 0 |
| 10:00 | 0 | 0.0 | 712 ms | 0 |
| 12:00 | 0 | 0.0 | 464 ms | 0 |
| 14:15 | 0 | 0.0 | 498 ms | 0 |
| 16:15 | 0 | 0.0 | 573 ms | 0 |
| 18:15 | 0 | 0.0 | 504 ms | 0 |
| 20:15 | 0 | 0.0 | 456 ms | 0 |
| 21:45 | 0 | 0.0 | 639 ms | 0 |
| 23:30 | 0 | 0.0 | 456 ms | 0 |
| 01:30 | 0 | 0.0 | 405 ms | 0 |
| 03:45 | 0 | 0.0 | 826 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
KUAC File Share – Final Data Migration to NetApp CIFS and Cutover
This change will complete the migration of the KUAC file share from the existing Windows file server to the NetApp CIFS share. The initial data migration, destination folder structure, and Active Directory security groups have already been prepared. Access testing has been coordinated with Chris Wadeson and KUAC users. During the scheduled change window, we will notify affected users, perform…
PROD Quarterly Oracle PSU Patching for Banner, Degree Works, UAOnline, and related systems
PROD environment Banner and related hosted systems will have current operating systems patches applied. This includes outages for the following services. Banner Database Banner Admin UAOnline Banner 9 Self Service All Degree Works instances Banner Job Submission Automic Application Manager Banner Workflow Banner Communication Management Jasper Reports Banner Access Manager Maps server
PROD Zoom: Enable Zoom Workflows for Testing and Documentation
This change is to enable Zoom Workflows for a small testing group, with an eventual release for general use in January 2027. Workflows is a no-code, AI-powered automation tool that allows users to create sequential, multi-step automated processes triggered by events across Zoom Workplace and integrated third-party applications.
Final 2026 Quarterly OnBase PROD update/refresh
This short downtime for all 4 OnBase servers is needed to apply the cumulative Windows updates as well as to reset the license cache and clean out the OnBase cruft. In addition, .NET versions 8 (if needed) and 10 will be installed IAW #990399. It includes work on: sw-onbase-pw2.apps.ad.alaska.edu ( Web server ) sw-onbase-pa2.apps.ad.alaska.edu ( Application server )…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for University of Alaska IT yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when University of Alaska IT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send University of Alaska IT alerts to Slack, Discord or a webhook — free.
We track University of Alaska IT (alaska.edu) as part of the Education group. The University of Alaska has three accredited universities, each with different strengths, different focus, and a unique student experience.
University of Alaska IT publishes an official status page at status.alaska.edu; when we can read it, its incident level is folded into the status shown here.
Common problems for education services: learning management systems and student portals slowing down around assignment deadlines, exams and registration.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 548 ms average, 405–826 ms range across 12 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: MI1017017: Microsoft 365 & Exchange Online Connectivity Issues
We have not recorded a public University of Alaska IT incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
548 ms on average over the last 24 hours (405–826 ms).
Yes, at https://status.alaska.edu.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For education services, watch for learning management systems and student portals slowing down around assignment deadlines, exams and registration. If many people report University of Alaska IT here at once, the problem is on University of Alaska IT's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with University of Alaska IT. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.