59 University Of Alaska incidents · 2025年6月 — official updates, affected components, duration and resolution details.
我们收到报告称,UAOnline公司目前正面临问题。 身份访问管理小组了解并查明了原因。 证书的签发给最近重新设置其证书的用户造成了错误的密码错误. 我们将每隔3小时更新一次,以努力解决问题。 谢谢你在解决这个问题期间的耐心!
IAM团队已经与UAOnline确定了这一问题,并实施了固定方案,目前正在监测其有效性和稳定性。 再次感谢你在解决这个问题期间的耐心! 您可以在工作日( 5: 00PM) 结束时或新信息可用时等待进一步更新.
IAM团队已与UAOnline服务公司解决了这个问题,并证实修复情况稳定. 导致发行的证书更新被退回。 请向校园的IT服务台报告这项服务的任何持续问题,并再次感谢你在解决这个问题期间的耐心!
自动翻译自官方事件更新。
我们收到报告称,各种网站和服务目前都面临可靠性问题。 OIT网络和PAWS团队正在调查,并怀疑这是与AWS等网络主机的全球性问题. 我们将在新信息公布后,在今天的办公日(下午5:00PM AKDT)结束时提供最新情况。 谢谢你在解决这个问题期间的耐心!
亚马逊报导从下午2:49到下午4:06(https://health.aws.amazon.com/health/status), 我们将监测服务稳定性,直到明天的营业日开始。 再次感谢你在解决这个问题期间的耐心! 你可以期待在8: 00AKDT再次更新.
据报受影响的服务自昨天晚上AWS修好以来保持稳定,我们正在考虑解决这一事件。 请向校园的IT服务台报告与普遍服务站点及服务的持续问题, 再次感谢你在解决这个问题期间的耐心!
大学网站和VPN 外部无障碍 问题影响分析 事件: 20260921 {\fn方正粗倩简体\fs12\an8\1cHFFFF00\b0}背景 阿拉斯加大学为位于远程且需要访问大学网络资源的大学附属用户提供虚拟私人网络\(VPN\)连接. 此外,该大学还接待了面临全球访问的公众网站。 这些服务以及其他服务都依赖于大学网络与更广泛的互联网之间的连通性,由我们的商品互联网服务提供商阿拉斯加通信系统公司提供。 打破问题 09/21/2026年下午3:30左右,大学网络外的远程用户报告了装入大学网站的问题,并额外报告了与大学VPN的连接中断. 现场技术员报告说,从大学网络内部可以获取虚拟网络和网络资源。 OIT电信服务调查并发现,网站和VPN连接正在大学网络内部工作,我们的网络与ACS的对等似乎在正常运行并接收/广告路线. 来自另一个远程工作和体验连通性问题的工作组的一位OIT技术员报告说,在进入大学网络之前,该大学的商品互联网服务提供商阿拉斯加通信系统(Alaska Communications Systems\(ACS\)网络内,从其家乡到多个大学资源的微量路径都失败了。 信息技术 大约下午4:30的电信服务收到ACS的电子邮件通讯,确认其网络内有网络事件,随后就在下午5:30前收到电子邮件,网络事件得到解决,服务稳定了. 目标国家/目标 阿拉斯加大学网络与互联网的连通性应始终保持在线,提供网站和VPN连接等UA网络资源的远程访问. # 根源分析 这被确定为由大学网络外,商品互联网服务提供商\(ACS\)网络内的事件所引发,ACS报告解析" 网络事件影响服务稳定,服务恢复完成. 虽然没有点到点的广域网电路或商品互联网对接受到 直接 的影响,但一些通过这些商品互联网对接的ACS网络的网络流量在供应商活动期间受到影响。 制定反措施 商品互联网服务提供商\(ACS\)解决了内部网络事件. 反措施的执行情况 随着我们意识到影响商品互联网连接的潜在问题,OIT电信服务公司将在未来接触服务供应商。 # 后续/审查 ACS提供内部网络事件解析的电子邮件确认.
自动翻译自官方事件更新。
我们收到报告说,alaska.edu和uaf.edu网站目前遇到问题。 OIT平台,Apps & Web Services(PAWS)团队目前正在调查,我们将每隔3小时进行更新. 目前的工作轮廓使用不同的浏览器;Google Chrome的成功率很高。 谢谢你在解决这个问题期间的耐心!
Alaska.edu和uaf.edu网站目前遇到问题。 OIT平台,Apps & Web Services(PAWS)团队正与Security合作,他们已经确定了这个问题. 证书应在小时之内更新,一旦解决,即更新状态. 目前的工作轮廓使用不同的浏览器;Google Chrome的成功率很高。 谢谢你在解决这个问题期间的耐心!
PAWS已经用alaska.edu和uaf.edu网站解决了这个问题,并证实修复工作是稳定的。 请向校园的IT服务台报告这项服务的任何持续问题,并再次感谢你在解决这个问题期间的耐心!
大学网站和VPN 外部无障碍 问题影响分析 事件: 20260921 {\fn方正粗倩简体\fs12\an8\1cHFFFF00\b0}背景 阿拉斯加大学为位于远程且需要访问大学网络资源的大学附属用户提供虚拟私人网络\(VPN\)连接. 此外,大学还接待了面临网站的公众,这些网站打算进入全球。 这些服务以及其他服务都依赖于大学网络与更广泛的互联网之间的连通性,由我们的商品互联网服务提供商阿拉斯加通信系统公司提供。 打破问题 09/21/2026年下午3:30左右,大学网络外的远程用户报告了装入大学网站的问题,并额外报告了与大学VPN的连接中断. 现场技术员报告说,从大学网络内部可以获取虚拟网络和网络资源。 OIT电信服务公司调查并发现,网站和VPN的连接正在大学网络内部工作,我们的网络与ACS的对等似乎在正常的恢复/广告路线. 来自另一个远程工作和体验连通性问题的工作组的一位OIT技术员报告说,在进入大学网络之前,该大学的商品互联网服务提供商阿拉斯加通信系统(Alaska Communications Systems\(ACS\)网络内,从其家乡到多个大学资源的微量路径都失败了。 信息技术 大约下午4:30的电信服务收到ACS的电子邮件通讯,确认其网络内有网络事件,随后就在下午5:30前收到电子邮件,网络事件得到解决,服务稳定了. 目标国家/目标 阿拉斯加大学网络与互联网的连通性应始终保持在线,提供网站和VPN连接等UA网络资源的远程访问. # 根源分析 这被确定为由大学网络外,商品互联网服务提供商\(ACS\)网络内的事件所引发,ACS报告解析" 网络事件影响服务稳定,服务恢复完成. 虽然没有点到点的广域网电路或商品互联网对接受到 直接 的影响,但一些通过这些商品互联网对接的ACS网络的网络流量在供应商活动期间受到影响。 制定反措施 商品互联网服务提供商\(ACS\)解决了内部网络事件. 反措施的执行情况 随着我们意识到影响商品互联网连接的潜在问题,OIT电信服务公司将在未来接触服务供应商。 # 后续/审查 ACS提供内部网络事件解析的电子邮件确认.
自动翻译自官方事件更新。
Google Chat目前面临问题, 这是一个供应商方面的问题,谷歌表示他们的技术人员目前正在调查. 现场更新可以在他们的状态盘上查看:https://www.google.com/appsstatus/dashboard/incidents/y2ufhCB886p7rveYNnko'. Google Chat用户正在经历一个问题,即他们收到新消息的通知,但实际消息无法出现在他们的聊天应用程序中,除非用户刷新他们的视图. 用户可以刷新以查看新信件. 我们将在获得新信息后每隔3小时提供最新情况。 谢谢你在解决这个问题期间的耐心!
Google报告该问题已经解决. 他们的状态仪表板: "Google Chat的问题从2026-08-28 13:45 PDT开始,所有受影响的用户都得到了解决. 从初步分析来看,这一问题是最近为减轻影响而回滚而发生的。 我们感谢你在我们努力解决问题时的耐心。” 感谢你们花时间来遵守这项决议!
这种中断是供应商停业造成的,与大学业务无关.
自动翻译自官方事件更新。
我们收到报告说,Canvas目前正面临问题。 NTS系统工程组目前正在调查,我们将每隔2小时进行更新。 谢谢你在解决这个问题期间的耐心!
NTS系统工程公司介绍了目前认识到的问题: "一些堆叠的Canvas课程正在经历一个问题. 这些课程是根据班纳的课程信息作为个人或堆放物产生的。 在Canvas的航道炮弹随后被教官或管理人员堆放或拆卸. 将Banner数据连接到Canvas的提供系统运行了8月24日的完整再提供,以修复Canvas各地的一些入学差异. 这解决了入学问题,但同时也使所发生的任何手工堆放/堆放行动失效。 对于受影响的课程,教员将看到其课程未出版、空出并回到原来的布局。 对于学生来说,看起来他们的课程会消失". 再次感谢你在我们努力全面解决这些问题时的耐心;我们将继续在得到新信息后每隔两小时提供最新情况.
NTS系统工程确定了378个可能受影响的课程。 所有课程材料都可以收回,教员有一些前进的选择。 NTS将努力收回任何在提供之前收到的学生申请. 教官有两个选择: 1. 与系统合作开办Canvas课程 -- -- 这些课程壳可包含8月24日提供课程之前的课程内容。 教官随后可以出版并继续上课. 2. 更新Banner课程的交叉列表 - 延后课程,并与部门课程调度器合作,提交修改Banner课程的交叉列表结构的建议,以匹配您在Canvas想要的内容. 更改完成后,新的系统生成了Canvas课程,就可以从8月24日提供之前的课程内容入住. 如果这影响了课程,请与课程的 SRN 和您选择的 URN 电子邮件 [email protected] 。 NTS只能帮助恢复内容. 对于选择选项2的教员,您需要联系您的课程排程器。 书记官长知道这一事件,可以帮助计时员提出所需的建议.
NTS系统工程团队正在继续恢复课程内容并补救一次性问题. 设有受影响Canvas课程的教员可选择的两种方案是: 1. 与系统合作开办Canvas课程 -- -- 这些课程壳可包含8月24日提供课程之前的课程内容。 教官随后可以出版并继续上课. 2. 更新Banner课程的交叉列表 - 延后课程,并与部门课程调度器合作,提交修改Banner课程的交叉列表结构的建议,以匹配您在Canvas想要的内容. 更改完成后,新的系统生成了Canvas课程,就可以从8月24日提供之前的课程内容入住. 如果这影响到课程,请用电子邮件将课程的 PRNs 和您希望采取的选项发送 [email protected]。 NTS只能帮助恢复内容,不能再手动交叉列表或去掉交叉列表课程. 对于选择选项2的教员,您需要联系您的课程排程器。 书记官长知道这一事件,可以帮助计时员提出所需的建议。 再次感谢你在我们争取全面解决的过程中抽出时间! 这是我们工作日的最后更新,报告将在当天开始时再次开始(上午8:00 AKDT).
感谢您耐心地处理最近软件问题, NTS SE、OIT EAS和UAF登记员确定了一个变通办法,允许在Canvas手工交叉列名。 这修改了以往指导员如何开展工作的指导。 教官们现在可以选择让他们的Canvas课程与其事前配置相匹配. 教官也能够利用Canvas的交叉列名工具自行进行这种重组。 如果您还遇到问题, 请提交 [email protected] 的入场券, 包括受影响部分的 CNN .
我们发现了一个配置问题 导致Canvas的 跨列表课程中断 NTS SE,OIT EAS,UAF注册员执行了一个固定,允许在Canvas进行人工交叉列名. 我们正在监测局势。 如果您仍然遇到问题, 且尚未提交帮助票, 请提交帮助台@ alaska.edu 的帮助票, 包括受影响部分的 CRN .
Canvas课程仍然可以由Canvas管理员和教官无所顾忌地交叉列出,我们正在考虑目前解决这一事件。 如果您仍然遇到问题或需要恢复课程内容,且尚未提交帮助票,请通过电子邮件[email protected]提供您的问题/请求的描述,并包括受影响部分的CRN。 感谢您在这个问题得到解决时的耐心!
LMS 服务退化 问题影响分析 事件: 8/25/26 {\fn方正粗倩简体\fs12\an8\1cHFFFF00\b0}背景 Canvas LMS平台为教官和学生提供基于网络的数字课堂功能. 该平台的课程、条件和入学情况通过与金融行动联盟的信息系统平台和登记程序直接连接加以管理。 对于大多数在线课程和一些面对面课程,相关的Canvas课程外壳是所有课程、参考资料和年级的集中位置。 打破问题 8/21/26日,我们收到了不到5个用户的帆布支持票,他们报告说,他们的课程名册是失踪学生或一名教员。 经调查,我们发现Canvas LMS到Banner SIS集成的配置存在时间问题. 这个名为ILP的集成在课程入学符合某些标准时进行实时更新. 出现这一问题的原因是,课程的入学人数在课程本身达到由国际法学会监测和更新的要求之前正在发生变化。 解决这个问题的办法是重新提供课程。 重新提供将课程信息视为“新”信息, 这解决了个别报告的问题,但我们需要重新提供所有课程,并在整个学期继续重新提供。 根据国际劳工局论坛的研究,这是大多数遇到这一问题的机构的解决办法。 在下午3点左右的8/24/26, 我们用ILP的"bulk job"工具重新提供UAF的所有课程。 然后我们验证了几张新门票的入学人数,这些门票是为了确保修补产生预期的效果。 已经失学的课程得到纠正。 下午8时24分26分, 经调查,我们发现受影响的课程都是交叉列入清单的,教员通过交叉列入额外课程或除名课程,手动改变了生成的系统配置。 教官可以在Canvas平台上完成这项工作,任何课程都被列为教官。 当我们重新提供时,这个系统改变了Canvas课程的配置,以配合班纳,而不管教官做了什么,都未能完成. 早上8时25分26分9分,随着更多Canvas服务票的到来,Canvas的服务中断开始退化。 我们与所有行政官员进行了沟通,向他们通报了情况,在掌握更多信息之前不要在坎瓦斯举办交叉名单课程。 我们在Canvas平台上向教官和管理员发布了关于停电的通知。 我们取消了Canvas教官的许可,使他们能够交叉列出/取消他们的课程。 我们评估了可能受到影响的课程数量,并与每个课程的记录教员进行了沟通。 8/25/26,PM NTS-SE-12号向教员提供指导,如果该系统产生的Canvas课程与教员想要的不符,则与书记官长联系。 我们发现,教员经常在Canvas开设跨模式的交叉名单课程,以便他们能够用一个课程壳管理一个课程的所有部分。 Canvas的功能允许他们这样做,而不要求他们互相揭露交叉上市的入学情况. 这是Canvas交叉列名和书记官长交叉列名之间的重要区别:书记官长的交叉列名/分类一词意味着入学人数集中在一起,预计学生将彼此接触。 书记官长的政策禁止跨模式的交叉列名。 这是由于参议院院系担心学生课程评价中的匿名性,学生可以通过他们的反应方式确定。 还提供了其他指导,指示教官与NTS服务台联系,以收回任何丢失的Canvas课程内容。 这些解决办法对许多依赖Canvas交叉名单能力的教员没有效果。 8/25/26,PM NTS-SE, 注册官和OIT-EAS工作组举行会议,审查和测试ILP的设置和选择,使教官脱离停工。 该小组确定了在不影响交叉列出课程的情况下重新提供的办法。 该小组确定了改变Canvas跨列表配置的现有实时更新进程。 小组测试了一个固定,允许教员在Canvas手动交叉列表,然后在我们测试的环境中验证. 修正是允许教员重新列出和(或)提交NTS服务台的罚单,以便我们的团队重新列出并恢复损失的内容。 所有未来的再规定都将使用排除交叉列表信息的配置. 在停机更新中和通过Canvas LMS平台公告中传达了该修补. 教官在Canvas可以交叉名单的许可重新启用. 管理人员被告知,他们现在可以交叉列出教员名单。 至12时 我们通过门票工作时,停电被移去监测。 最迟于上午8时28分/26分 断电问题得到解决。 目标国家/目标 这个问题改变了目标状态. 教官们应该能够手动将他们的课程贝壳在Canvas列出交叉列表或去除交叉列表,无论课程是如何在班纳编码. Banner ILP种子不应改变或设定交叉列表配置,也不应通过实时监测来监视或更新交叉列表状态. 活跃的用户在Banner ILP系统进行初始供给后,应经历一致使用同一Canvas课程外壳,除非教员或管理员手动更改.
自动翻译自官方事件更新。
一些AT&T移动客户目前无法完成校园电话号码的呼叫. 这个问题被确定为源自AT&T的网络,而不是我们的电话系统或服务. 我们正在监测局势,一旦确认电话正常运转,我们将提供最新情况.
我们没有进一步的报告 问题呼叫大学, 费尔班克斯北星 Borough校区确认 他们的类似问题已经解决。 我们正在考虑这个时候解决了这一停电问题;如果你继续有任何问题通过电话联系任何UA校园,请打电话给你的校园信息技术服务台! 非常感谢你的时间.
这种中断是供应商停业造成的,与大学业务无关.
自动翻译自官方事件更新。
我们收到报告称,UAF校园周围的读卡器目前遇到问题。 OIT PAWS团队已意识到,并正在积极致力于回收控制这个系统的服务器. 我们将每隔一个小时提供最新情况,以努力解决问题。 建筑协调员可能知道某些房间的替代进入方法和路线,但目前还没有广泛的工作。 谢谢你在解决这个问题期间的耐心!
我们正在继续努力解决这个问题。
OIT PAWS报告说,列内尔卡刷卡系统的服务器已成功重启并正在运行.
# ** Root 原因分析 – Argus 服务器事件** □ ** 执行摘要** Argus服务器经历了Windows C:驱动器上可用空间的快速损失. 在调查期间,PAWS确定了在Lenel应用程序日志目录中发生的重大磁盘活性. 可用的磁盘空间继续减少,最终达到约37 MB. PAWS清洁地关闭了服务器,以防止操作系统能达到可得到的0个磁盘空间,并可能造成额外的系统问题. PAWS扩展了 C: 驱动并成功将服务器返回服务. 回收后,磁盘利用率得到稳定,还有大约20GB的自由空间。 PAWS负责基本的Windows服务器基础设施,但不管理或支持Lenel应用程序. 应用程序生成的磁盘活动增加的原因尚未确定,需要应用程序所有人/供应商进行调查。 □** 事件影响** 阿尔格斯服务器在事件和基础设施恢复活动期间变得无法使用,导致依赖服务器的服务中断. 报告的影响包括对营地门卡阅读器的功能。 □** 时间线** ** 所有时间都是阿拉斯加时间。 ** ** 几乎11:04 AM** – PAWS接到一个涉及Argus服务器的问题的通知,并向营地门卡阅读器报告了影响。 相关事件为TDX 991008. ** 接近11:23 AM ** – PAWS确定Windows C:驱动器上可用的空间会迅速减少. 资源监视器显示在下列范围内发生了重大的写作活性: “ C:\ 方案数据/ Ln\ logs” PAWS试图恢复现有的磁盘容量;然而,C:利用率继续提高。 C:驱动器最终达到可使用空间的约**37 MB**. PAWS清洁地关闭了VM来防止Windows系统驱动器到达0可得到的空间,并可能引发额外的操作系统问题. PAWS进行了提高系统驱动能力所需的基础设施工作。 ** 3:34 PM** — 基础设施工程已经完成,C:驱动器也扩大了。 服务器被带回在线,PAWS验证了正常的服务器和磁盘操作. ** 约下午3:49 - 该服务器已启用。 次日,C:保持了约**19.9GB免费**的平稳状态,没有再发生快盘消耗. □** 轮回原因** 服务器停用的直接原因是Windows C:驱动器上的现有容量已耗尽. 在事件中, PAWS 观察到在 Lenel 应用程序日志目录内有大量磁盘写入活动: “ C:\ 方案数据/ Ln\ logs” 这项活动迅速消耗了系统驱动器的剩余能力。 应用程序产生的磁盘活动增加的根本原因**尚未确定**。 PAWS负责管理基本的服务器基础设施,但不管理,配置或支持Lenel应用程序. 确定应用程序为何产生增加的磁盘活性,需要应用程序所有人/供应商进行调查,并且不在这种基础设施RCA的范围之内。 □ ** 责任因素** ** 有限可用的系统磁盘容量** 服务器没有足够的剩余C:驱动能力来吸收应用程序生成的磁盘利用率的出乎意料的增加. 可用容量最终会降至约**37 MB**,需要PAWS关闭服务器来阻止Windows达到可使用磁盘空间0. □ ** 决议** PAWS完成了下列基础设施恢复行动: * 调查迅速下降的C:驱动能力。 * 识别与磁盘活动增加有关的源目录。 * 在系统驱动器达到0个可用空间之前,清理关闭服务器. * 提高Windows C的可用能力:驱动。 * 返回服务器服务。 * 验证正常服务器和磁盘操作。 * 回收后继续监测磁盘利用率。 恢复后,C:驱动器稳定在约**19.9GB免费**. □** 补救和预防行动** **磁盘能力监测** PAWS将审查Argus服务器的磁盘容量监测和警报阈值,以便在系统驱动容量接近临界值时提供足够的通知. ** 服务能力** PAWS将继续监测C:驱动利用率,以核实额外能力在正常服务器条件下提供足够的操作头室. ** 申请调查** 应用程序所有者/供应商需要确定列内尔所生成的磁盘活动出乎意料地增加的原因并找出可能需要的任何应用程序级纠正行动. 应用程序配置、记录、保留和应用级补救不在PAWS服务器管理范围之内。 □ ** 现状** Argus服务器在线运行. C:在后续监测期间,驱动力保持稳定,约为**19.9 GB免费**,没有再次发生事件期间观察到的快速磁盘消耗. PAWS认为事件**服务器基础设施部分已得到解决**. Lenel应用行为的根本原因仍未确定,需要应用程序所有人/供应商跟进.
自动翻译自官方事件更新。
我们收到报告说,班纳目前正面临问题。 OIT EAS小组目前正在调查中,我们将每隔1小时进行更新。 已经确定了一个运行正常的工作方向:打开一个私人或隐形浏览器窗口进入Banner。 如果站点仍然在缓慢/没有加载,关闭并打开另一个新的私人或隐形窗口;它可能需要一些尝试,但一旦实现可靠的连接,你可以继续使用该会话直到问题得到解决! 谢谢你在解决这个问题期间的耐心!
OIT EAS小组已经与Banner确定了这一问题,并实施了固定措施,目前正在监测其有效性和稳定性。 再次感谢你在解决这个问题期间的耐心! 您可以在工作日5:00PM结束或获得新信息时等待进一步更新.
OIT EAS团队已经与"班纳"(Banner)解决了这个问题,并确认了固定状态是稳定的. 问题于8月10日解决. 请向校园的IT服务台报告这项服务的任何持续问题,并再次感谢你在解决这个问题期间的耐心!
班纳雇员服务 问题影响分析 事件发生时间:2026年8月10日 上午10:30至10:53 {\fn方正粗倩简体\fs12\an8\1cHFFFF00\b0}背景 Banner雇员自助服务应用程序是雇员提交计时表、查看其休假结余以及与阿拉斯加大学系统就业有关的类似项目的主要服务。 销售商Ellucian是Banner大学和Banner自助服务公司的东道主,负责通过监测和纠正行动确保提供这些课程。 打破问题 在上午10点35分左右,UAF NTS服务台联系了Slack的Banner团队,告知他们在Banner极端缓慢的报道. 一项简短的审查表明,只有雇员自助服务单元遇到问题。 服务台建议围绕尝试一个无名浏览器,为一些人工作。 EAS团队向埃尔卢西安伸出援手,并创造了一张P1入场券. 服务按预期在上午10时53分左右重新开始运作。 目标国家/目标 Banner和Banner Self Services的所有组件都应满足日常维护窗口和其他预定出行时间的预期。 # 根源分析 修复期间参与的埃尔卢西亚云层小组分享了与这一事件有关的以下信息。 对其监测的审查表明,性能退化始于上午10:42,10:50时完全无法进行。 与集装箱有关的自动化工作在上午10时53分成功启动,雇员自助服务10时57分完全稳定。 Ellucian没有评估任何与停产原因有关的进一步情况。 EAS团队意识到Banner员工自助服务软件中存在产品缺陷,该软件被证明造成此类事件,首次经验于今年3月和4月,涉及产品缺陷,在生产中尚未纠正,但计划应用. 制定反措施 为了今后解决这个问题,我们期望,采用最近的缺陷解决办法将纠正这一问题。 反措施的执行情况 2026年9月12-13日:部署解决已查明缺陷的班纳相关升级. # 后续/审查 2026年9月14日:对解析能力进行了验证升级部署.
自动翻译自官方事件更新。
我们收到报告说,Iru网络登录选项目前遇到问题。 NTS技术支助服务小组目前正在调查,我们将每隔3小时提供最新情况。 切换到本地登录应该允许您登录您的 Mac 。 谢谢你在解决这个问题期间的耐心!
NTS技术支助服务小组目前正在调查这一问题的原因。 如果无法登录到您的 UA Mac, 他们会尝试切换到本地登录 。 要切换到本地登录 : 1. 点击屏幕右上角的剖面图标(圆内人). 2. 选择切换到本地登录。 3. 在屏幕下方中心附近的用户名和密码字段中输入您的大学登录证书。 4. 点击签名 进入登录。 如果您仍无法登录,请联系当地信息技术服务台寻求进一步援助。 感谢大家在我们努力争取全面解决的过程中继续表现出耐心;我们将每隔3小时,在获得新信息后,作进一步更新.
NTS TSS小组目前正在调查这一问题的原因。 Iru 同步您的密码的提示, 安全地忽略了您所能做的, 而我们调查为什么它被激发。 如果无法登录到您的 UA Mac, 他们会尝试切换到本地登录 。 要切换到本地登录 : 1. 点击屏幕右上角的剖面图标(圆内人). 2. 选择切换到本地登录。 3. 在屏幕下方中心附近的用户名和密码字段中输入您的大学登录证书。 4. 点击签名 进入登录。 如果您仍无法登录,请联系当地信息技术服务台寻求进一步援助。 感谢大家在我们争取全面解决的过程中继续表现出耐心;我们将每隔一个小时并在获得新信息时提供进一步的更新.
NTS TSS小组正在继续调查这一问题的原因。 目前没有进一步的更新. Iru 同步您的密码的提示, 安全地忽略了您所能做的, 而我们调查为什么它被激发。 如果无法登录到您的 UA Mac, 他们会尝试切换到本地登录 。 要切换到本地登录 : 1. 点击屏幕右上角的剖面图标(圆内人). 2. 选择切换到本地登录。 3. 在屏幕下方中心附近的用户名和密码字段中输入您的大学登录证书。 4. 点击签名 进入登录。 如果您仍无法登录,请联系当地信息技术服务台寻求进一步援助。 感谢大家在我们争取全面解决的过程中继续表现出耐心;我们将每隔一个小时并在获得新信息时提供进一步的更新.
最近我们解决了一个问题 杜奥认证的意外变化 影响了整个校园的MacOS计算机登录 如果您使用大学管理的Mac,你的登录经验现在恢复到正常操作. 然而,您第一次在此修正后登录到您的计算机时, 您可能会看到另外一两个 Duo 认证提示 。 今天第一次在您的Mac上签字时: 1. 在主macOS登录屏幕上输入您通常的账户证书。 2. 完成Duo提示: 系统权限刷新后, 您可能会被提示通过 Duo 认证额外时间 。 3. 批准您的Duo移动应用程序、硬件代号上的请求,或者通过您所选择的正常的多功能省方法。 4. 在“让我们”账户中选择下一个账户,以保持您的账户安全。 5. 在设置时选择下一个即时登录方法。 如果您继续遇到登录错误, 请重复提醒您在登录时同步密码, 或其他任何登录您的 Mac 的问题, 请联系您的校园 IT 服务台 .
这一事件已经得到解决.
IRU 认证退出 问题影响分析 事件: 20260803 {\fn方正粗倩简体\fs12\an8\1cHFFFF00\b0}背景 IRU认证服务为被管理的macOS设备提供用户认证能力,并通过Kandji Passport提供网络访问. 该服务依赖于Kandji Passport,Microsoft Entra ID,有条件访问政策和Duo MFA之间的集成,为用户提供安全认证. 打破问题 2026年8月3日,用户尝试访问IRU服务时遇到认证问题. 这个问题影响了试图通过Kandji Passport网络登录进行认证的用户,并影响了完成登录进程的能力. 这个问题通过Entra ID签名登录,有条件访问政策,Duo MFA认证流量,和Kandji Passport认证服务来调查. 目标国家/目标 一个功能认证到IRU管理的macOS设备. # 根源分析 对微软有条件访问方法的修改,自2026年6月15日起生效: * [https://learn.microsoft.com/en-us/entra/identity/有条件的获取/概念-执行-资源-排斥](https://learn.microsoft.com/en-us/entra/identity/enteral-access/ conception-forcement-resources-排斥) * [https://techcommunity.microsoft.com/blog/microsoft-en-blog/upcoming-conference-access-change-improved-for-policys- with-resour/4488925](https://techcommunity.microsoft.com/blog/microsoft-en-blog/upcompress-access-en-access-efferfor-policies-wi-resour/4488925] (中文(简体中文) ). 上述改动现在要求将DUO设定为M365用户账户的默认登录方法. 制定反措施 通过将用户添加到Entra群中,从而可以使用更新型的DUO认证方法来制定即时应对措施. 反措施的执行情况 信息技术工作人员完成了一项改动,增加了所有用户,以接受这一修正。 # 后续/审查 定期审查长期解决方案的执行进展情况.
自动翻译自官方事件更新。
无法访问vdi.alaska.edu,但已查明停电原因。 任何通过vdi.alaska.edu的桌面访问,可能还有厚厚的客户端,都无法从该地址访问或使用虚拟机,直到问题得到解决.
阿联酋已查明如何访问vdi.alaska.edu,并正在努力解决这一问题。 任何通过vdi.alaska.edu的桌面访问,可能还有厚厚的客户端,将无法使用该地址的虚拟机. 感谢你在解决这个问题期间的耐心。 请在上午11点50分更新,之后每小时更新.
阿联酋已查明如何访问vdi.alaska.edu,并正在努力解决这一问题。 任何通过vdi.alaska.edu的桌面访问,可能还有厚厚的客户端,将无法使用该地址的虚拟机. 感谢你在解决这个问题期间的耐心。 请在下午12:50更新.
阿联酋已查明如何访问vdi.alaska.edu,并正在努力解决这一问题。 任何通过vdi.alaska.edu的桌面访问,可能还有厚厚的客户端,将无法使用该地址的虚拟机. 感谢你在解决这个问题期间的耐心。 请在下午1: 50更新.
阿联酋已查明如何访问vdi.alaska.edu,并正在努力解决这一问题。 任何通过vdi.alaska.edu的桌面访问,可能还有厚厚的客户端,将无法使用该地址的虚拟机. 感谢你在解决这个问题期间的耐心。 请在下午5点收到最新消息.
阿联酋已与vdi.alaska.edu解决了这个问题,并证实定律稳定. 这将会在下午5点开始监控,直到业务结束。 请向校园的IT服务台报告这项服务的任何持续问题,并再次感谢你在解决这个问题期间的耐心!
阿联酋已与vdi.alaska.edu解决了这个问题,并证实定律稳定. 请向校园的IT服务台报告任何持续的问题,并再次感谢你在解决这个问题期间的耐心!
[vdi.alaska.edu] (http://vdi.alaska.edu) 访问中断. 已过期的统一访问网关证书 。 时间:07/23/2026 下午4: 00. {\fn方正粗倩简体\fs12\an8\1cHFFFF00\b0}背景 [vdi.alaska.edu](http://vdi.alaska.edu)提供用户访问VMware/Omnissa Horizon VDI环境. 两种统一访问网关设备\(存在于VXrail平台\)都为想要在校园或远程访问其VDI的用户提供外部访问层. 打破问题 每张UAG上的两张证书都于2026年7月23日3:59 PM过期. 7月24日(星期五)上午8:30左右,当用户报告说,他们在解析到[vdi.alaska.edu](http://vdi.alaska.edu)时无法访问他们的“我的桌面”VDI环境时,就注意到了这个问题。 当一个用户试图通过他们的浏览器决定[vdi.alaska.edu](http://vdi.alaska.edu)时,他们收到了一个“你的连接不是私人的”通知,然后将被禁止到达[vdi.alaska.edu](http://vdi.alaska.edu). 地平线页面。 为恢复服务而采取的行动: 请求 PAWS 提供更新证书. 此证书包含主域名 [vdi.alaska.edu] (http://vdi.alaska.edu) ,但也包含替代名\\(两个UAG名\) [fbk-uag1.apps.ad.alaska.edu] (http://fbk-uag1.apps.ad.alaska.edu). [fbk-uag2.apps.ad.alaska.edu] (http://fbk-uag2.apps.ad.alaska.edu) (中文(简体) ). [fbk-uag1.io.apps.ad.alaska.edu] (http://fbk-uaf1.io.alaska.edu). [fbk-uag2.io.alaska.edu] (http://fbk-uag2.io.alaska.edu). 停止服务的期限和恢复服务时间: 7月23日星期四下午4: 00 - 星期五晚上24: 00. 目标国家/目标 UAG 双方应不断提供有效、可信赖的证书以及外部和内部的VDI访问 # 根源分析 # 两种UAG设备都提交了过期的TLS证书. TSS收到了一份VXrail服务器电器清单,这些电器估计其证书到期的时间。 这两种UAG设备都未列入清单,因此我们无法决定其证书何时到期。 制定反措施 我创建了一个主证书电子表格, 现在包含两个 UAG 的证书信息, 包括过期日期 。 我将分享给TSS团队的负责人, 要求访问 Certinext 服务, 供将来的证书更新 。 执行时间表: 以上内容应允许我们在证书到期前申请并执行证书。 # 后续/审查 通过监控主证书电子表格来验证两个UAG的证书过期日期 。 向PAWS申请续签证书,计划简短的CAB出局,将证书应用到两个UAG,然后确认续签成功并进行访问
自动翻译自官方事件更新。
We have received reports that Banner Admin is currently experiencing issues at login. A workaround has been identified for some users: attempt to load https://banner.alaska.edu/ in new incognito/private browser windows until the login screen successfully loads. The OIT Enterprise Applications Services (EAS) team is currently investigating, and we will be making updates at 1-hour intervals. Thank you for your patience during the resolution of this issue!
Ellucian, the vendor for Banner, has identified the issue and implemented a fix, which is being monitored for effectiveness and stability. Thank you again for your patience during the resolution of this issue! You can expect another update at the end of the business day (5:00PM) or if new information becomes available.
The fix applied to Banner Admin has remained stable, and we are considering the outage resolved at this time. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during its resolution!
UAOnline and Banner Admin Login Issue Problem Impact Analysis Event Occurrence: May 28, 2026 4am to 11:15am, May 29, 2026 4am to 9am # Background UAOnline is the self service portal for Ellucian Banner used as the university’s Enterprise Resource Planning \(ERP\) system. These systems are hosted in Ellucian cloud and require period maintenance including security certificate updates for trust between UA and Ellucian systems. The Banner software periodically has system defects that are addressed by daily application restarts. # Break Down of the Problem On May 28th at 6:56am, a notice was sent to the Banner team through slack that a person was receiving an error when attempting to access the Employee Dashboard. The vendor Ellucian was notified of the event and identified the issue and implemented a work around. On May 29th at 8:11am, the same issue was reported through the Banner team slack channel for Banner Admin. The same ticket opened the prior day was used to report the issue and they used the same work around from the day before to restore service prior to 9:00am. # Target State / Goal Banner self service \(Employee Dashboard\) and Banner Admin services should be available to customers 24/7 except during pre-defined maintenance windows. # Root Cause Analysis Ellucian in preparation for an upcoming security certificate renewal staged changes in the production environment for the following weekend’s activity. There were mitigations in place due to Banner product defects that would restart Banner service instances daily at 4am. The restart process triggered the inclusion of these new certificates, causing a mismatch of certificates that prevented Single Sign On services from connecting for both Banner admin and the employee self service module. # Develop Countermeasures * Complete the implementation of the new certificates. * Provide feedback to the vendor to ensure their staff are properly equipped to avoid this in the future. # Implementation of Countermeasures May 30, 7:00 PM: Complete implementation of certificate change over for the whole system. June 2, 11:00AM: Convey feedback to vendor on how they need to change. # Follow Up / Review May 30-31: Validate certificate replacement is working for all systems. June 2: Vendor notified and RCA was provided by vendor, confirming what occurred.
We have received reports that forms in Banner admin are not loading, and UAOnline's Employee login is experiencing authentication issues. The OIT EAS team is currently reaching out to the vendor, and we will be making updates at 30-minute intervals. Thank you for your patience during the resolution of this issue!
OIT EAS has contacted the vendor for Banner and are monitoring their communication channels for updates. We will continue to make updates as new information becomes available and at 30-minute intervals. Thank you again for your time and patience while we work towards a resolution!
OIT EAS reports the vendor's technicians are engaged and working on both Banner/UAOnline issues experienced. We will continue to make updates as new information becomes available and at 30-minute intervals. Thank you again for your time and patience while we work towards a resolution!
The issue is continuing to be worked, and there is no new information available at this time. We will continue to make updates as new information becomes available and at 30-minute intervals. Thank you again for your time and patience while we work towards a resolution!
Ellucian, the vendor for Banner, has identified the issue and implemented a fix, which is being monitored for effectiveness and stability. Thank you again for your patience during the resolution of this issue! You can expect further updates at the end of the business day (5:00PM) or as new information becomes available.
The fix applied to Banner Admin and the UAOnline Employee Dashboard has remained stable, and we are considering the outage resolved at this time. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during the resolution of this issue!
UAOnline and Banner Admin Login Issue Problem Impact Analysis Event Occurrence: May 28, 2026 4am to 11:15am, May 29, 2026 4am to 9am # Background UAOnline is the self service portal for Ellucian Banner used as the university’s Enterprise Resource Planning \(ERP\) system. These systems are hosted in Ellucian cloud and require period maintenance including security certificate updates for trust between UA and Ellucian systems. The Banner software periodically has system defects that are addressed by daily application restarts. # Break Down of the Problem On May 28th at 6:56am, a notice was sent to the Banner team through slack that a person was receiving an error when attempting to access the Employee Dashboard. The vendor Ellucian was notified of the event and identified the issue and implemented a work around. On May 29th at 8:11am, the same issue was reported through the Banner team slack channel for Banner Admin. The same ticket opened the prior day was used to report the issue and they used the same work around from the day before to restore service prior to 9:00am. # Target State / Goal Banner self service \(Employee Dashboard\) and Banner Admin services should be available to customers 24/7 except during pre-defined maintenance windows. # Root Cause Analysis Ellucian in preparation for an upcoming security certificate renewal staged changes in the production environment for the following weekend’s activity. There were mitigations in place due to Banner product defects that would restart Banner service instances daily at 4am. The restart process triggered the inclusion of these new certificates, causing a mismatch of certificates that prevented Single Sign On services from connecting for both Banner admin and the employee self service module. # Develop Countermeasures * Complete the implementation of the new certificates. * Provide feedback to the vendor to ensure their staff are properly equipped to avoid this in the future. # Implementation of Countermeasures May 30, 7:00 PM: Complete implementation of certificate change over for the whole system. June 2, 11:00AM: Convey feedback to vendor on how they need to change. # Follow Up / Review May 30-31: Validate certificate replacement is working for all systems. June 2: Vendor notified and RCA was provided by vendor, confirming what occurred.
There is an Active Directory issue that is preventing users from logging into certain systems. The PAWS/Networking/Security teams are actively troubleshooting and investigating the issue.
An Active Directory issue is currently affecting UAF Servers and Services. The PAWS, Networking, and Security teams are actively troubleshooting and investigating the issue. If you are a user logging into a server remotely using VDI, VPN, or other services, such as WiFi, that use your UA AD credentials, they may show as invalid. The cause is still being identified and the scope of the affected systems and services are still being assessed.
An Active Directory issue is currently affecting UAF Servers and Services. The PAWS, Networking, and Security teams are actively troubleshooting and investigating the issue. A possible cause is being investigated and an update will be sent out as soon as it's identified. If you are a user logging into a server remotely using VDI, VPN, or other services, such as WiFi, that use your UA AD credentials, they may show as invalid. The cause is still being identified and the scope of the affected systems and services are still being assessed.
There are no new updates as of 11:21AM. Reporting will continue until the end of day at 5PM. An Active Directory issue is currently affecting UAF Servers and Services. The PAWS, Networking, and Security teams are actively troubleshooting and investigating the issue. A possible cause is being investigated and an update will be sent out as soon as it's identified. If you are a user logging into a server remotely using VDI, VPN, or other services, such as WiFi, that use your UA AD credentials, they may show as invalid. The cause is still being identified and the scope of the affected systems and services are still being assessed.
There are no new updates as of 12:20PM. The issue is continuing to be investigated and reporting will continue until the end of day at 5PM. An Active Directory issue is currently affecting UAF Servers and Services. The PAWS, Networking, and Security teams are actively troubleshooting and investigating the issue. A possible cause is being investigated and an update will be sent out as soon as it's identified. If you are a user logging into a server remotely using VDI, VPN, or other services, such as WiFi, that use your UA AD credentials, they may show as invalid. The cause is still being identified and the scope of the affected systems and services are still being assessed.
Update (1:30 PM): The Authentication Issues affecting UAF servers and services is still under investigation. The PAWS, Networking, and Security teams are actively troubleshooting a potential cause. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be shared as soon as a cause is identified, with continuous reporting through 5:00 PM.
Update (2:45 PM): The Authentication Issues affecting UAF servers and services is still under investigation. The PAWS, Networking, and Security teams are actively troubleshooting a potential cause. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be shared as soon as a cause is identified, with continuous reporting through 5:00 PM.
Update (3:33 PM): The Authentication Issues affecting UAF servers and services is still under investigation. The PAWS, Networking, and Security teams are actively troubleshooting a potential cause. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be shared as soon as a cause is identified, with continuous reporting through 5:00 PM.
The Authentication Issues affecting UAF servers and services is still under investigation. The PAWS, Networking, and Security teams will continue remediation efforts tomorrow morning at 8:00 AM. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be posted here tomorrow morning. Thank you for your patience.
The Authentication Issues affecting UAF servers and services are still under investigation. The PAWS, Networking, and Security teams will continue remediation efforts this morning at 8:00 AM. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be posted here later today. Thank you for your patience.
As of 1PM on Sunday, May 17th, our teams are still actively troubleshooting the authentication issues. Teams are working with Cisco and Microsoft to investigate the cause. We will post more information as soon as it's available. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be posted here later today. Thank you for your patience while we find a solution.
As of 5PM on Sunday, May 17th, our teams are still actively troubleshooting the authentication issues. Teams are working with Cisco and Microsoft to investigate the cause. We will post more information as soon as it's available. At this time, university Wi-Fi, VPN and VDI services have been restored. User Impact: The UAF Devices Portal or other services using UA AD credentials may fail or show as invalid. Our next scheduled update is 11PM. Thank you for your patience while we find a solution.
As of 11PM on Sunday, May 17th, our teams are still actively troubleshooting the authentication issues. Teams are working with Cisco and Microsoft to investigate the cause. The next update will be tomorrow at 7AM. At this time, university Wi-Fi, VPN and VDI services have been restored. User Impact: The UAF Devices Portal or other services using UA AD credentials may fail or show as invalid.
As of 7AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. The next update will be later this morning at 8AM. At this time, university Wi-Fi, VPN and VDI services have been restored. User Impact: The UAF Devices Portal or other services using UA AD credentials may fail or show as invalid.
As of 8AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. More information will be available after the 9AM meeting with diagnostic teams from this weekend. The next update will be later this morning at 9AM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.
As of 9AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. More information will be available after meeting with diagnostic teams from this weekend. The next update will be later this morning at 10AM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.
As of 10AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. More information will be available after meeting with diagnostic teams from this weekend. The next update will be later this morning at 11AM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.
As of 11AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. More information will be posted as soon as it's available. The next update will be later today at 12PM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.
As of 12PM on Monday, May 18th, the current fixes in place are still holding steady. Our teams are continuing to work with Cisco and Microsoft on troubleshooting the authentication issues. More information will be posted as soon as it's available. The next update will be later today at 1PM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.
As of 1PM on Monday, May 18th, while we are in monitoring mode, all impacted systems have been restored and continue to be stable. More information will be posted as soon as it's available. The next update will be later today at 2PM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. User Impact: Some services using UA credentials may still fail or show as invalid.
As of 3PM on Monday, May 18th, all impacted systems have been restored and continue to be stable. The next update will be 8AM tomorrow. If you continue to experience service login errors, please contact the NTS Service Desk. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. User Impact: Some services using UA credentials may still fail or show as invalid.
As of 8AM on Tuesday, May 19th, all impacted systems have been restored and continue to be stable. The next update will be 8AM tomorrow. If you continue to experience service login errors, please contact the NTS Service Desk. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. User Impact: Some services using UA credentials may still fail or show as invalid.
As of 8AM on Wednesday, May 20th, the primary impacted services have been restored and are currently stable under monitoring. The next update will be tomorrow at 8AM, unless there are any significant changes. At this time, university Wi-Fi, UAF Devices Portal, VPN, and VDI services have been restored.
As of 8AM on Thursday, May 21st, the primary impacted services have been restored and are currently stable under monitoring. The next update will be tomorrow at 8AM, unless there are any significant changes. At this time, university Wi-Fi, UAF Devices Portal, VPN, and VDI services have been restored.
Our teams have resolved the issue with the Authentication service, and confirmed the fix to be stable. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during the resolution of this issue!
We have received reports that ELMO is currently experiencing issues. The UAS ELMO team is currently investigating, and we will be making updates at 30 minute intervals. Thank you for your patience during the resolution of this issue!
The UAS ELMO team has identified the issue with ELMO service and has implemented a fix, which is being monitored for effectiveness and stability. Thank you again for your patience during the resolution of this issue! You can expect further updates at the end of the business day (5:00PM) or as new information becomes available.
The affected components of ELMO appear to be stable. We will continue monitoring the stability of the fix over the weekend, and you can expect a final update at the start of business (8:00AM) Monday if there is no new information until then. Thank you again for your patience during the resolution of this issue!
The UAS ELMO team has resolved the issue with the ELMO, and confirmed the fix to be stable. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during the resolution of this issue!
We have received reports that UAOnline Employee Login is currently experiencing issues. The OIT Enterprise Applications (EAS) team is aware and has identified the cause. This issue appears to be related to an update to Banner over the weekend that is causing issues for some users. EAS is currently working with the vendor, Ellucian towards a permeant fix. For users experiencing issues, there is a workaround. If getting an error, simply change the "UAA" in the url to either "UAF" or "UAS". Once logged into UAOnline, you should be able to log out and use the Employee Login option without issue. We will make updates on this situation at the end of the business day 5:00pm and as new information becomes available. Thank you for your patience during the resolution of this issue!
There are still some users currently experiencing issues with the UAOnline Employee Login. The EAS team is continuing to work with the vendor, Ellucian, towards a permeant fix. For users experiencing issues, there is a workaround. If getting an error stating that the "MEP code is invalid", simply change the "UAA" in the url of the page displaying the error to either "UAF" or "UAS". Once logged into UAOnline, you should be able to log out and use the Employee Login option without issue. If the issue persists, please contact the NTS Service Desk. We will make updates on this situation at the start of the business day 8:00am and as new information becomes available. Thank you for your patience during the resolution of this issue!
The OIT EAS team has identified the issue with the UAOnline Employee Login and has implemented a fix, which is being monitored for effectiveness and stability. Thank you again for your patience during the resolution of this issue! You can expect further updates at the end of the business day (5:00PM) or as new information becomes available.
The OIT EAS team has resolved the issue with the UAOnline Employee Login, and confirmed the fix to be stable. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during the resolution of this issue!
We have received reports that our ticketing system, TeamDynamix (TDX), is currently experiencing issues processing replies to generated emails. The UAA Enterprise Service Management team is currently investigating, and we will be making updates when we open at 8:00am Alaska Time. Thank you for your patience during the resolution of this issue!
UAA ESM has applied a workaround and the affected components of TDX appear to be stable. We will continue monitoring the stability of the fix until the end of the business day (5:00PM) today, and you can expect a final update at that time if there is no new information until then. Thank you again for your patience during the resolution of this issue!
The UAA ESM team has resolved the issue with the affected components of TDX, and confirmed the fix to be stable. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during the resolution of this issue!
This outage was caused by an issue on our vendor’s side. They released the following information: “The issue was caused by a misconfiguration during a maintenance deployment and has now been fully resolved.“
We have received reports that the Banner Production instance (including UAOnline) is currently experiencing issues. The OIT Enterprise Applications Services team is aware and has contacted the vendor. We will be making updates at 1-hour intervals as they work towards a fix. Thank you for your patience during the resolution of this issue!
OIT EAS reports that Ellucian is going to perform a rolling restart of the affected components, so we expect to see services regain functionality one-at-a-time. We'll report on the status of each as new information becomes available, and at our 1-hour intervals! Thank you again for your time and understanding.
A fix has been implemented and users are reporting access. We will continue to monitor the service and update the status page at 5PM.
A fix has been implemented and users are reporting access. There have been no new developments, monitoring will continue until tomorrow morning at 8:00AM.
The affected components of Banner and UAOnline appear to be stable. We will continue monitoring the stability of the fix until the 24-hour mark, at approximately 12:52PM today, and you can expect a final update at that time if there is no new information until then. Thank you again for your patience during the resolution of this issue!
The affected components of Banner are still operational, and we are considering the fix to be stable and this outage resolved. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during the resolution of this issue!
We have received reports that multiple Banner Self-Service services (including UAOnline) are currently unavailable. The OIT Enterprise Applications Services team has reached out to the vendor and is currently investigating, and we will be making updates at 1-hour intervals. Please contact your campus IT helpdesk if you notice other Banner components are affected. Thank you for your patience during the resolution of this issue!
Some users are reporting that functionality has returned, but are still experiencing slowness. We're waiting for further updates from the vendor, Ellucian, and will continue to make updates as new information becomes available and at 1-hour intervals. Thank you for your time.
Ellucian reports that they have marked our incident as high-priority, located the cause, and are currently working on a fix. Further updates will continue at 1-hour intervals and as new information becomes available. Thank you for your time!
A fix has been implemented and users are reporting access. We will continue to monitor the service and update the status page at 5PM.
A fix has been implemented and users are reporting access. There have been no new developments, monitoring will continue until tomorrow morning at 8:00AM.
The affected components of UAOnline appear to remain operational! We will continue monitoring the stability of the fix until the 24-hour mark, at approximately 1:30PM today, and you can expect a final update at that time if there is no new information until then. Thank you again for your patience during the resolution of this issue!
UAOnline is experiencing slowness and timeouts as a result of a different incident, and details can be found here as we continue to follow that resolution: https://status.alaska.edu/incidents/2141hpy4lvlm
This issue with UAOnline was identified and the fix is stable.
UAOnline Partial Outages Problem Impact Analysis Event Occurrence: March \[15, 17, 20 , 23\] 2026 Employee Self Service; April 2, 2026 Employee Self Service; April 7, 2026 Finance Self Service; April 8, 2026 General Self Service # Background UAOnline is the self service portal for Ellucian Banner used as the university’s Enterprise Resource Planning \(ERP\) system. Banner and UAOnline are hosted by the vendor Ellucian, also the maker of the product. From time to time during initial validation of new upgrades, not all defects are experienced. The self service components of Banner include General, Employee, Finance, and Student self service. All of these are separate applications that are made available under the heading UAOnline and navigable between each area after initial login. # Break Down of the Problem Initially Employee Self Service \(ESS\) was impacted with unavailability on March 15, 17, and 20. Upon report of an issue with the instance the vendor was notified and the corrective action was to restart the service. Noted during these times that some end users were able to access the platform while others could not. On March 20th the service owner escalated further related to this issue. Ellucian shared 2 product defects related to ESS that they expected to cause the issue scheduled of the UA production environment in May. Ellucian recommends instituting daily restarts of the Employee Self Service instances to occur in the UA daily maintenance window of 4am to 5am. The earliest Ellucian could schedule was March 25, resulting in another outage on March 23rd and an escalation response to Ellucian to restore service. On April 2nd, after mitigation was in place, ESS failed again and Ellucian further escalated to prepare a fix to address the product defect specifically for ESS. A patched version of ESS was deployed on April 3rd in TEST and validation was reported back to Ellucian on April 6th to go into production. Further issues with ESS were not identified. On April 7th, Finance Self Service\(FSS\) went down and was reported to Ellucian and Ellucian configured daily restarts. April 8th, General Self Service \(GSS\) was reported down and escalations were entered with Ellucian. On April 10, all self service apps were scheduled to be updated similarly to ESS with daily restarts. All but GSS were successful with this update. # Target State / Goal The Banner and UAOnline services should be available 24 hours a day 7 days a week with the exception of scheduled and planned down time including the daily maintenance window. The system should always be responsive. # Root Cause Analysis Ellucian’s review of the application hosts that were failing showed the available disk filling up related to a large amount of logs being created in a very short period of time. Ellucian attempted to mitigate this with a daily restart, but demonstrated during this time that the issue could manifest in just a few hours. Ellucian traced to specific product defects that they believed were causing the excessive logging issue. They attempted to mitigate this issue by establishing daily restarts and by creating a non-standard custom WAR file for deployment and management of each Self Service Application. Ellucian later discovered that there was a bug in the text manager product component that when using a MEP environment like UA has, could cause the excessive generation of error log messages which is likely what was filling the disk. Ellucian has released an update for each of the Self Service applications out of band to address the product defect. # Develop Countermeasures * Deploy updated version of self service software that addresses the product defect. # Implementation of Countermeasures * May 10, 2026 - All self service application with the expectation of Employee Self Service \(ESS\) will be updated to the version where the underlying product defect is corrected. ESS has a new defect that will prevent immediate updating. * Future - Apply ESS tier 2 update which corrects the product defect, when the other dependent product defect is resolved. # Follow Up / Review May 11, 2026: Verify all self service applications are working as expected. July 5, 2026: Verify status of ESS to be upgraded.
We have received reports that Finance Self-Service Banner (the UAOnline 'Finance' tab) is currently experiencing issues. The OIT Enterprise Applications Services team has sent a high-priority ticket to the vendor, and we will be making updates at 3-hour intervals. Thank you for your patience during the resolution of this issue!
Ellucian has restarted the affected services; Finance SSB and its associated UAOnline tab appear to be functional again! We will monitor the stability of this fix and make another update at the end of the business day (5:00PM) today. Thank you again for your time while we followed the resolution of this issue!
Ellucian has restarted the affected services; Finance SSB and its associated UAOnline tab appear to be functional again. There have been no new developments, monitoring will continue until tomorrow morning at 8:00AM. Thank you again for your time while we followed the resolution of this issue.
The issue with Finance SSB, and its associated UAOnline tab, was identified. A fix was implemented and the solution is still working after being monitored all night. Marking this as resolved.
We have received reports that the Employee login for UAOnline (Employee SSB) is currently experiencing issues including slowness and intermittent login availability. The OIT Enterprise Applications Services team is currently investigating, and we will be making updates at 3-hour intervals. Thank you for your patience during the resolution of this issue!
Further reports indicate Faculty Self-Service (this includes the 'Faculty & Advisor Services' link in UAOnline) may also be impacted. OIT EAS has opened a ticket with the vendor for Banner, and are monitoring their channels of communication for updates. We will continue to make updates as new information becomes available, and at 3-hour intervals. Thanks so much for your time!
The vendor for Banner is currently investigating the cause of this issue. OIT EAS is monitoring their channels of communication for updates. Thank you for your continued patience as we work towards a full resolution. We will continue to make updates as new information becomes available, and at 3-hour intervals.
OIT EAS reports that the vendor has been instructed to restart the affected services, and are awaiting confirmation that the instructed actions have been taken. Once complete, the effectiveness of the solution will be determined. Thank you again for your patience! We will continue to make updates at 3-hour intervals and as new information becomes available.
The affected services have been reset, and Employee SSB and Faculty SSB through UAOnline both appear to be operational again. We will monitor the stability of this fix, and another update can be expected at the end of the business day (5:00pm) today! Please report any continued issues with Banner and UAOnline to your campus IT helpdesk. Thanks so much again for your time and patience as we followed the resolution of this incident.
The Employee SSB and Faculty SSB through UAOnline both are operational. We will continue to monitor the stability of this fix, and another update can be expected at the start of the business day (8:00am) tomorrow! Please report any continued issues with Banner and UAOnline to your campus IT helpdesk. Thanks so much again for your time and patience as we followed the resolution of this incident.
The affected components of UAOnline and Banner appear to remain operational! We will continue monitoring the stability of the fix until the 24-hour mark, at approximately 12:39PM today, and you can expect a final update at that time if there is no new information until then. Thank you again for your patience during the resolution of this issue!
We've received no further reports of UAOnline or Banner service degradation, and are marking this incident as resolved. Please report any issues with these services (and others!) to your campus IT helpdesk as usual. Thank you again, and happy Friday!
