October 30th, 2025 Microsoft Azure Outage
Incident Details
INCIDENT DATE: 30 October 2025
INCIDENT TIME: 5:45am
INCIDENT DURATION: Approximately 4.5 hours
SEVERITY LEVEL: Partial outage
Incident Description
At approximately 5:45am, some Hitrak users experienced issues connecting to the Driver App and other client applications.
The issue was quickly traced to a widespread Microsoft Azure outage, which affected several services including Azure Front Door (AFD). This disruption temporarily prevented access to Hitrak client applications.
The issue was quickly traced to a widespread Microsoft Azure outage, which affected several services including Azure Front Door (AFD). This disruption temporarily prevented access to Hitrak client applications.
The impact was partial, as many users continued to access the Driver App and complete normal operations, and the Hitrak Admin Portal and API Gateway remained fully functional, ensuring core business operations could continue.
The Hitrak team distributed backup run manifests via email to affected customers. As the Admin Portal was still available, users were also able to manage runs and print up-to-date manifests directly, to support manual delivery operations.
Microsoft confirmed at 6:22am that the issue was related to the Azure Front Door service, and initiated a rollback to its last known good configuration.
Full service restoration to impacted Hitrak users was observed by approximately 10:15am. By 12:58pm, Microsoft reported service availability above 98%.
Systems and Data Affected
Affected
Access to Hitrak client applications (Driver App, Freightmaster, Fleet Tracker, Receiver App) was intermittently unavailable for some users.
Unaffected
Unaffected
The Admin Portal and API Gateway continued to operate normally, allowing essential business operations to continue.
Data Integrity
Data Integrity
No application data was lost or compromised.
Root Cause Analysis
Microsoft attributed the incident to an inadvertent configuration change affecting Azure Front Door (AFD).
As the root cause originated with Microsoft infrastructure, an internal Hitrak root cause analysis was not required.
As the root cause originated with Microsoft infrastructure, an internal Hitrak root cause analysis was not required.
Lessons Learnt
Hitrak’s existing disaster recovery process, which creates and stores a backup of key operational documents overnight in an independent cloud environment, enabled the team to supply necessary files to customers and maintain operational continuity.
Although backup files were distributed within 1.5 hours of the first report, Hitrak has identified opportunities to streamline this process. Internal refinements will ensure that in future, backup documents can be issued to affected customers within minutes of detection.
Although backup files were distributed within 1.5 hours of the first report, Hitrak has identified opportunities to streamline this process. Internal refinements will ensure that in future, backup documents can be issued to affected customers within minutes of detection.
Having Issues?
Email us at support@hitrak.com or submit a Helpdesk ticket