53 Fmx incidents · juli 2018 — official updates, affected components, duration and resolution details.
Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.
Et fix er blevet gennemført, og vi overvåger resultaterne.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Der har været rapporter om et forhøjet antal fejl på tværs af programmet.
Automatisk oversat fra den officielle hændelsesopdatering.
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.
Vi undersøger i øjeblikket problemet.
Spørgsmålet er blevet identificeret, og vi arbejder på at afhjælpe problemet.
Vi ruller et fix ud over de berørte miljøer.
Et fix er blevet gennemført, og vi overvåger resultaterne.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
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.
Earlier today, 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, resulting in approximately 5-10 minutes of unexpected downtime. We sincerely apologize for this interruption and any inconvenience it may have caused. We plan to implement measures to prevent this from happening in future deployments and are reviewing our processes to ensure greater reliability moving forward.
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.
On 10/22/2024 at approximately 10:30 PM EDT FMX experienced a server failure that required manual intervention to restore it. On 10/23/2024 at 4:10 AM EDT we had successfully restored the affected databases and are continuing to investigate the extent of data that was not restored between 10 and 11 pm EDT
Through our investigation we have identified a subset of customers that were potentially affected by this issue. If you are one of the customers that we have identified, our Customer Success team will be reaching out to you via phone or email. What we know at this time is that we experienced multiple hardware failures that required us to roll back a subset of our databases to an earlier restore point. Any data that was added, edited, or deleted between 10:00pm EDT, and 11:00pm EDT on 10/22/2024 for these identified customers has been corrupted and our Customer Success team will be reaching out to you to answer any further questions. We are still in the process of investigating alternative remediation steps and will be conducting an internal postmortem to better understand and prioritize future infrastructure changes and processes to remove the possibility of this ever happening again. We know that any amount of data corruption can be a problem, and we apologize for any inconvenience this issue has caused.
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.
Our Cloud Service Provider is experiencing an outage. We will update this message as we have more details. We apologize for the inconvenience.
We are continuing to monitor and follow our cloud providers status pages and will provide more updates as they become available.
According to our cloud provider they've `determined the underlying cause and are currently applying mitigation through multiple workstreams. ` We're continuing to monitor the situation and will provide updates as they become available.
We are seeing sites come back online. We're continuing to monitor the incident to ensure our cloud service provider's mitigation is successful.
Our cloud provider has deployed a fix that appears to have resolved the current incident. We'll continue to monitor the situation and provide updates as they happen.
This incident has been resolved by our cloud service provider. We will continue to keep an eye out for any further issues. Again, our sincere apologies for any service disruption.
We want to thank you for using FMX to manage your operations. We understand that FMX is often a critical component of running your organization and therefore we take any service disruptions seriously. This postmortem report will help you to better understand what caused the interruption in service as well as how we plan to avoid issues like these in the future. **The root cause of the outage** On the evening of July 18th, we discovered that the FMX platform was unavailable. After investigating we determined that the cause of this was due to an entire region outage at the Microsoft Azure datacenters across the entire US-Central region. You can read more about it [here](https://azure.status.microsoft/en-us/status/history/) from the Azure team. Tracking ID: `1K80-N_8` **Solution** To solve the problem, we simply monitored the situation and waited for the Azure remediations to be implemented. **Future mitigations** On July 30th, we conducted our own internal postmortem discussing future mitigation tactics that we can employ to reduce our reliance on an individual region or cloud provider, improve communication, and improve our monitoring capabilities. This discussion aligned very closely with the [Azure Well-Architected Framework](https://learn.microsoft.com/en-us/azure/well-architected/). Regards, FMX Team
We are currently investigating degraded site performance and errors when generating PDFs. We will update our status page with additional details as they become available. We apologize for any inconvenience.
A fix has been implemented to resolve PDF generation errors. We are continuing to monitor site performance.
This incident has been resolved.
We have identified an issue with our reporting dashboards. We are investigating solutions for a fix. We anticipate that reporting dashboards should be up in a few hours. We'll update this message as we progress on this issue. We apologize for the inconvenience.
We have identified a fix for this issue. We are working on testing the fix now. We'll update this message once our fix passes testing and is out for release. We still anticipate that reporting dashboards should be up in a couple of hours.
A fix has been implemented, and we're monitoring the results.
This incident has been resolved.
We are currently investigating an issue related to our servers. We will report back when we have more information. We apologize for the inconvenience.
We are continuing to investigate an issue related to our servers. We will report back when we have more information. We apologize for the inconvenience.
The application is back online. However, we may see degraded performance until our system can recover from the issue. We will report back when our application performance is back to normal. We apologize for the inconvenience.
This incident has been resolved. Application performance should be back to normal.
We have identified an issue that is impacting users ability to resolve work requests. We have identified a fix and are working to implement it. We will respond back on our status page with a timeline shortly. We apologize for any inconvenience this issue has caused.
We are rolling out a fix now. We expect full service to be returned in 20 minutes or less. We apologize for any inconvenience this issue has caused.
This issue is now resolved. We apologize for any inconvenience this issue has caused.
We are aware of an issue impacting the universal sign-on function on our marketing website https://www.gofmx.com Users who attempt to sign on through our marketing website will receive a page not found error. Please note that you can still sign on to your FMX site via a direct link, .gofmx.com (example.gofmx.com). If you don't know your direct link, you can find one by clicking any link back to FMX through any email notification. From there, you will be prompted to log in. You can also contact the FMX Support Team at [email protected] for assistance. Once you've identified your direct link to your FMX site, we recommend bookmarking it and using it as your primary login method in the future, as it is the most direct path to your site. We apologize for any inconvenience this issue has caused and will update this message when the universal sign-on service is restored.
This issue has been resolved. Users that experienced the issue before may need to "hard refresh" the login page by holding the shift key and clicking the browser's refresh button if they're still experiencing the issue. We apologize for any inconvenience this issue has caused. We recommend bookmarking a direct link to your FMX site and using it as your primary login method in the future, as it is the most direct path to your site. Your direct link is .gofmx.com (example.gofmx.com). If you don't know your hostname, you can find a direct link by clicking any link back to FMX through any email notification. From there, you will be prompted to log in. You can also contact the FMX Support Team at [email protected] for assistance.