FMX had 10 outages in the last 2 years totaling 33h 8m of downtime — averaging 0.4 incidents per month.
There were 10 FMX outages since July 18, 2024 totaling 33h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're currently investigation an incident with one of our cloud providers.
We have implemented a workaround to the cloud provider incident and are monitoring the situation.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating the issue.
The issue has been identified and a solution is being implemented.
We are starting the deployment of our fix to the performance issue
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We deployed a critical hotfix to address an issue in our system. While this deployment was designed to occur without downtime, an internal misconfiguration inadvertently triggered maintenance mode. We have identified the issue and are actively working on remediation steps. We sincerely apologize for this interruption and any inconvenience it may have caused.
The main application should be available now and we are still working through the other services
A fix has been implemented and we are now monitoring.
This incident has been resolved. Again. We sincerely apologize for this interruption and any inconvenience this may have caused.
Earlier today, we deployed a hotfix to address a previously identified calendar-related issue. Inadvertently, additional changes were included in the deployment, which resulted in the calendar returning errors and being temporarily inaccessible for approximately 3-4 minutes. The issue was quickly identified and resolved, and full functionality has been restored. We apologize for any inconvenience this may have caused and are reviewing our deployment processes to prevent similar occurrences in the future.
We're currently investigating reports of customers that are receiving a 502 error while logging into Mapping and Mobile.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
We have implemented a fix and are continuing to monitor.
This incident has been resolved.
We have received reports that some users can't access their site. Microsoft has reported that there is an issue between their cloud and AT&T customers. They're currently looking into the issue. You can follow their status page https://azure.status.microsoft/en-us/status for more details. If available, you can try switching over to a mobile hot spot.
The incident has been marked as resolved by Microsoft.