Wireless Network Slowdown & Connectivity
Last updateresolvedOct 26 · 21:06 UTC
This incident has been resolved.
Reported by ASU System ITS on their status page.
checked Oct 28, 2026 7:17 PM UTC · ASU System ITS's official status page
ASU System ITS is up and running.
ASU System ITS is currently operational with all systems functioning normally.
All components operational
Be the first to know
Statusfield watches ASU System ITS alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
ASU System ITS incident history
2 reports published by ASU System ITS in the last 30 days
When ASU System ITS breaks, it is typically resolved in 6h 16m — median across 1 resolved incidents over 30 days.
October 26, 2026
October 21, 2026
Temporary Service Interruptions Related to Worldwide PHP Security Issue
Last updatepostmortemOct 26 · 15:08 UTC
Incident Postmortem: Emergency PHP Security Upgrades & Proactive Site OutagesDate: October 26, 2026 Incident Window: October 21 – October 25, 2026 Prepared By: Chris Doyle, Director of Infrastructure and Networking Services
Executive Summary During the week of October 21, 2026, Infrastructure and Networking Services executed an emergency remediation across our web hosting environments in response to critical zero-day Remote Code Execution (RCE) vulnerabilities in the PHP core (CVE-2026-109618 and CVE-2026-109619, known as "PHP2Shell"). To protect institutional data and prevent active exploitation, several web applications experienced planned and preventative downtime while PHP runtimes were upgraded to patched versions. Legacy sites with incompatible codebases were intentionally taken offline as a containment measure until code remediation and testing could be completed.
Root Cause & Trigger An urgent security advisory (CERT-EU 2026-018) identified severe RCE flaws affecting PHP versions 5 through 8, primarily exploiting multipart form data and file upload handling. Because public-facing PHP applications were at immediate risk of compromise, waiting for a standard maintenance window was not viable.
Impact & Containment Actions While perimeter mitigations—including custom Palo Alto threat signatures and blocking external multipart uploads—were immediately put in place at the firewall level, patching the underlying PHP runtimes across our Linux and Windows (IIS/FastCGI) servers was required for full remediation.
- Upgrade-Related Downtime: Multiple websites experienced brief outages as server environments were upgraded to patched PHP 8.x releases and services were restarted.
- Proactive Takedowns: Select applications running on legacy PHP versions (such as PHP 7.4) or utilizing deprecated functions were intentionally taken offline. Taking these sites down prevented both potential security breaches and broken application states (white-screens/fatal errors) during the transition to PHP 8.x. Some sites are still down at the time of this postmortem as they will require php rewrites.
Resolution & Recovery Web environments were systematically backed up and upgraded to secure PHP 8.x branches (with side-by-side FastCGI configurations retained on Windows servers for controlled testing and rollback). Applications were brought back online as their compatibility and database connections were verified. Remaining offline sites are being refactored or isolated prior to restoration.
Reported by ASU System ITS on their status page.