Aug <var data-var='date'> 5</var>, <var data-var='time'>14:24</var> EDT Resolved - This incident has been resolved. Aug <var data-var='date'> 5</var>, <var data-var='time'>13:54</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'> 5</var>, <var data-var='time'>13:35</var> EDT Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'> 5</var>, <var data-var='time'>13:15</var> EDT Investigating - We are currently investigating this issue.

Elevated 500 errors being reported

Aug <var data-var='date'> 3</var>, <var data-var='time'>22:30</var> EDT Completed - The scheduled maintenance has been completed. Aug <var data-var='date'> 3</var>, <var data-var='time'>22:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'> 3</var>, <var data-var='time'>11:05</var> EDT Scheduled - We will be performing scheduled maintenance on our databases. During this window, some services may be temporarily unavailable or degraded. We expect the work to take approximately 15-30 minutes.

Database Maintenance

Aug <var data-var='date'> 2</var>, <var data-var='time'>16:41</var> EDT Resolved - This incident has been resolved. Aug <var data-var='date'> 2</var>, <var data-var='time'>16:33</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'> 2</var>, <var data-var='time'>15:45</var> EDT Update - We're currently rolling out a fix across the affected environments. Aug <var data-var='date'> 2</var>, <var data-var='time'>13:16</var> EDT Identified - The issue has been identified and we are working to remediate the issue. Aug <var data-var='date'> 2</var>, <var data-var='time'>12:15</var> EDT Investigating - We are currently investigating the issue.

System Unavailable

Jun <var data-var='date'>28</var>, <var data-var='time'>21:23</var> EDT Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>28</var>, <var data-var='time'>21:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>24</var>, <var data-var='time'>13:23</var> EDT Scheduled - We will be performing scheduled maintenance on Sunday evening. While maintenance windows are typically brief, this planned maintenance requires a larger than normal period that may last up to 30 minutes. The FMX application and API may be unavailable during this time.

Scheduled System Maintenance

Oct <var data-var='date'>30</var>, <var data-var='time'>14:37</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>30</var>, <var data-var='time'>14:30</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'>30</var>, <var data-var='time'>14:00</var> EDT Update - We are continuing to investigate this issue. Oct <var data-var='date'>30</var>, <var data-var='time'>13:59</var> EDT Investigating - We are currently investigating this issue.

Login and performance issues

Oct <var data-var='date'>30</var>, <var data-var='time'>09:28</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>29</var>, <var data-var='time'>12:48</var> EDT Monitoring - We have implemented a workaround to the cloud provider incident and are monitoring the situation. Oct <var data-var='date'>29</var>, <var data-var='time'>12:24</var> EDT Investigating - We're currently investigation an incident with one of our cloud providers.

Cloud service provider disruption

Oct <var data-var='date'>19</var>, <var data-var='time'>00:00</var> EDT Completed - The scheduled maintenance has been completed. Oct <var data-var='date'>18</var>, <var data-var='time'>22:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct <var data-var='date'>14</var>, <var data-var='time'>08:50</var> EDT Scheduled - We will be undergoing scheduled maintenance during this time.

Scheduled Database Maintenance COMPLETED 13 Oct 2025 (00:00 EDT)

Oct <var data-var='date'> 2</var>, <var data-var='time'>11:19</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'> 2</var>, <var data-var='time'>11:02</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'> 2</var>, <var data-var='time'>10:38</var> EDT Identified - The issue has been identified and a fix is being implemented. Oct <var data-var='date'> 2</var>, <var data-var='time'>10:27</var> EDT Investigating - We are currently investigating this issue.

Disruption of Service

Sep <var data-var='date'>29</var>, <var data-var='time'>11:01</var> EDT Resolved - This incident has been resolved. Sep <var data-var='date'>29</var>, <var data-var='time'>10:46</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>29</var>, <var data-var='time'>10:19</var> EDT Update - We are starting the deployment of our fix to the performance issue Sep <var data-var='date'>29</var>, <var data-var='time'>09:03</var> EDT Identified - The issue has been identified and a solution is being implemented. Sep <var data-var='date'>29</var>, <var data-var='time'>08:59</var> EDT Investigating - We are currently investigating the issue.

General slowness with the API

Apr <var data-var='date'>14</var>, <var data-var='time'>12:38</var> EDT Resolved - This incident has been resolved. Again. We sincerely apologize for this interruption and any inconvenience this may have caused. Apr <var data-var='date'>14</var>, <var data-var='time'>12:11</var> EDT Monitoring - A fix has been implemented and we are now monitoring. Apr <var data-var='date'>14</var>, <var data-var='time'>12:00</var> EDT Update - The main application should be available now and we are still working through the other services Apr <var data-var='date'>14</var>, <var data-var='time'>11:57</var> EDT Identified - 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.

Temporary Downtime During Update

Mar <var data-var='date'>10</var>, <var data-var='time'>10:30</var> EDT Resolved - 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.

Temporary Calendar Inaccessibility Due to Hotfix

Mar <var data-var='date'> 3</var>, <var data-var='time'>12:30</var> EST Resolved - 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.

Nov <var data-var='date'>19</var>, <var data-var='time'>14:25</var> EST Resolved - This incident has been resolved. Nov <var data-var='date'>19</var>, <var data-var='time'>14:18</var> EST Monitoring - We have implemented a fix and are continuing to monitor. Nov <var data-var='date'>19</var>, <var data-var='time'>14:13</var> EST Identified - The issue has been identified and a fix is being implemented. Nov <var data-var='date'>19</var>, <var data-var='time'>14:09</var> EST Update - We are continuing to investigate this issue. Nov <var data-var='date'>19</var>, <var data-var='time'>14:06</var> EST Investigating - We're currently investigating reports of customers that are receiving a 502 error while logging into Mapping and Mobile.

Logging in to Mapping results in a 502 error

Oct <var data-var='date'>24</var>, <var data-var='time'>09:11</var> EDT Resolved - 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. Oct <var data-var='date'>23</var>, <var data-var='time'>09:57</var> EDT Investigating - 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

Database failover

Sep <var data-var='date'>12</var>, <var data-var='time'>10:33</var> EDT Resolved - The incident has been marked as resolved by Microsoft. Sep <var data-var='date'>12</var>, <var data-var='time'>09:11</var> EDT Investigating - 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.

Site unavailable for AT&T customers

Jul <var data-var='date'>19</var>, <var data-var='time'>01:02</var> EDT Resolved - 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. Jul <var data-var='date'>18</var>, <var data-var='time'>22:47</var> EDT Monitoring - 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. Jul <var data-var='date'>18</var>, <var data-var='time'>21:43</var> EDT Update - We are seeing sites come back online. We're continuing to monitor the incident to ensure our cloud service provider's mitigation is successful. Jul <var data-var='date'>18</var>, <var data-var='time'>21:38</var> EDT Update - 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. Jul <var data-var='date'>18</var>, <var data-var='time'>20:56</var> EDT Update - We are continuing to monitor and follow our cloud providers status pages and will provide more updates as they become available. Jul <var data-var='date'>18</var>, <var data-var='time'>18:52</var> EDT Investigating - Our Cloud Service Provider is experiencing an outage. We will update this message as we have more details. We apologize for the inconvenience.

Cloud Service Provider outage

Oct <var data-var='date'> 2</var>, <var data-var='time'>11:05</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'> 2</var>, <var data-var='time'>09:09</var> EDT Monitoring - A fix has been implemented to resolve PDF generation errors. We are continuing to monitor site performance. Oct <var data-var='date'> 2</var>, <var data-var='time'>08:38</var> EDT Investigating - 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.

Degraded performance

Apr <var data-var='date'>24</var>, <var data-var='time'>13:36</var> EDT Resolved - This incident has been resolved. Apr <var data-var='date'>24</var>, <var data-var='time'>12:01</var> EDT Monitoring - A fix has been implemented, and we're monitoring the results. Apr <var data-var='date'>24</var>, <var data-var='time'>09:56</var> EDT Identified - 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. Apr <var data-var='date'>24</var>, <var data-var='time'>08:16</var> EDT Investigating - 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.

Reporting dashboards outage

Mar <var data-var='date'>10</var>, <var data-var='time'>12:44</var> EST Resolved - This incident has been resolved. Application performance should be back to normal. Mar <var data-var='date'>10</var>, <var data-var='time'>12:32</var> EST Identified - 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. Mar <var data-var='date'>10</var>, <var data-var='time'>12:19</var> EST Update - 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. Mar <var data-var='date'>10</var>, <var data-var='time'>12:03</var> EST Investigating - We are currently investigating an issue related to our servers. We will report back when we have more information. We apologize for the inconvenience.

Outage

Feb <var data-var='date'>20</var>, <var data-var='time'>08:30</var> EST Resolved - This issue is now resolved. We apologize for any inconvenience this issue has caused. Feb <var data-var='date'>20</var>, <var data-var='time'>08:07</var> EST Update - 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. Feb <var data-var='date'>20</var>, <var data-var='time'>07:40</var> EST Identified - 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.

Degraded performance resolving work requests

Jan <var data-var='date'>30</var>, <var data-var='time'>09:08</var> EST Resolved - 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 <your hostname>.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 support@gofmx.com for assistance. Jan <var data-var='date'>30</var>, <var data-var='time'>08:09</var> EST Investigating - 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, <your hostname>.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 support@gofmx.com 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.

Unable to sign on through universal sign on on gofmx.com

Dec <var data-var='date'> 8</var>, <var data-var='time'>15:15</var> EST Resolved - This incident has been resolved. This outage was the result of a bug that our Cloud Service Provider, Microsoft Azure, has in the service offering that FMX consumes. Microsoft Azure has assured us that they are currently testing a fix for this issue. We apologize for the inconvenience! Dec <var data-var='date'> 8</var>, <var data-var='time'>15:03</var> EST Investigating - We're currently investigating a site outage that began at 2:40 pm EST. Our typical responses to this known issue with our Cloud Service Provider do not seem to have had an impact. We'll report back as we have more information. We apologize for the inconvenience!

Temporary Outage

Dec <var data-var='date'> 2</var>, <var data-var='time'>13:51</var> EST Resolved - This incident has been resolved. This outage was the result of a bug that our Cloud Service Provider, Microsoft Azure, has in the service offering that FMX consumes. Microsoft Azure has assured us that they are currently testing a fix for this issue. We apologize for the inconvenience! Dec <var data-var='date'> 2</var>, <var data-var='time'>13:30</var> EST Investigating - We're currently investigating a site outage that began at 1:12 pm EST. Our typical responses to this known issue with our Cloud Service Provider do not seem to have had an impact. We'll report back as we have more information. We apologize for the inconvenience!

Temporary outage

Nov <var data-var='date'>22</var>, <var data-var='time'>20:00</var> EST Resolved - The FMX application experienced a 40-minute outage starting at 7:55 pm and ending at 8:33 pm EST. This outage was the result of a bug that our Cloud Service Provider, Microsoft Azure, has in the service offering that FMX consumes. Microsoft Azure has assured us that they are currently testing a fix for this issue. We apologize for the inconvenience!

40-minute outage

Nov <var data-var='date'>16</var>, <var data-var='time'>18:38</var> EST Resolved - This incident has been resolved. We'll continue to monitor the application for any issues. We apologize for the inconvenience! Nov <var data-var='date'>16</var>, <var data-var='time'>18:13</var> EST Investigating - We're currently investigating a site outage that began at 5:44 pm EST. Our typical responses to this known issue with our Cloud Service Provider do not seem to have had an impact. We'll report back as we have more information. We apologize for the inconvenience!

Is FMX System down?

FMX System status is UP

Lastest published events

Elevated 500 errors being reported

Database Maintenance

System Unavailable

FMX System Services, Components and Regions

Recent FMX System events

Elevated 500 errors being reported

Database Maintenance

System Unavailable

Scheduled System Maintenance

Login and performance issues

Cloud service provider disruption