Previous incidents
Door Access, Emails, and 1 other service are down
Resolved Apr 12, 2026 at 5:11am UTC
Sub Systems recovered.
3 previous updates
Sub Systems is down
Resolved Apr 4, 2026 at 11:11am UTC
Sub Systems recovered.
7 previous updates
Sub Systems is down
Resolved Apr 3, 2026 at 8:56pm UTC
Sub Systems recovered.
1 previous update
ManageRegister is down
Resolved Apr 2, 2026 at 4:58am UTC
ManageRegister recovered.
1 previous update
ManageRegister is down
Resolved Mar 31, 2026 at 7:08pm UTC
ManageRegister recovered.
1 previous update
ManageShifts is down
Resolved Mar 21, 2026 at 1:25pm UTC
ManageShifts recovered.
1 previous update
Sub Systems is down
Resolved Mar 18, 2026 at 1:31pm UTC
Sub Systems recovered.
1 previous update
Sub Systems is down
Resolved Mar 17, 2026 at 9:11am UTC
Sub Systems recovered.
1 previous update
Door Access is down
Resolved Mar 16, 2026 at 5:13pm UTC
Door Access recovered.
1 previous update
Portals, Time Clock, and 1 other service are down
Resolved Mar 8, 2026 at 3:07am UTC
Time Clock recovered.
5 previous updates
Sub Systems is down
Resolved Mar 6, 2026 at 6:21am UTC
Sub Systems recovered.
1 previous update
Time Clock is down
Resolved Mar 5, 2026 at 5:52pm UTC
Time Clock recovered.
1 previous update
Portals and Time Clock are down
Resolved Feb 26, 2026 at 5:24pm UTC
Portals recovered.
5 previous updates
Sub Systems is down
Resolved Feb 25, 2026 at 7:36pm UTC
Sub Systems recovered.
1 previous update
Sub Systems is down
Resolved Feb 24, 2026 at 6:41pm UTC
Sub Systems recovered.
1 previous update
AWS Host Level Degradation Causing Service Interruption
Resolved Feb 23, 2026 at 2:07pm UTC
Instance became intermittently unresponsive. SSH access was timing out, EC2 Serial Console failed to connect, and stop operation was unusually slow. Status checks showed insufficient data during the event.
Initial investigation after regaining SSH showed no memory pressure, no swap usage, and no disk errors. CPU credit balance remained healthy at over 500 credits. However, vmstat revealed high CPU steal time, peaking above 50 percent, indicating significant hypervisor level contention.
No e...