FMX Outage History

FMX is up right now

Pingoru has recorded 50 incidents for FMX: 8 in the last 12 months and 6 in the last 90 days.

Source: status.gofmx.com

50incidents recorded
8last 12 months
6last 90 days
7 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking FMX in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202626 of 744 (1%)
September 2026425 of 720 (3%)
October 202600 of 525 (0%)

Incidents, newest first

Minor September 16, 2026 Mobile users unable to login 38m Mobile

Started Sep 16, 2026, 02:18 PM UTC· resolved Sep 16, 2026, 02:56 PM UTC

  1. investigating Sep 16, 2026, 02:18 PM UTC

    Investigating reports of users not being able to login to the mobile application

  2. monitoring Sep 16, 2026, 02:37 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 16, 2026, 02:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 14, 2026 Increased latency across platform 1d Web App, API, Reporting Dashboards

Started Sep 14, 2026, 01:17 PM UTC· resolved Sep 15, 2026, 01:18 PM UTC

  1. investigating Sep 14, 2026, 01:17 PM UTC

    We are currently investigating this issue.

  2. identified Sep 14, 2026, 01:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Sep 14, 2026, 01:59 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Sep 14, 2026, 02:06 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Sep 14, 2026, 02:50 PM UTC

    We're adding additional hardware to increase capacity

  6. monitoring Sep 14, 2026, 03:15 PM UTC

    A fix has been implemented and we are monitoring the results.

  7. resolved Sep 15, 2026, 01:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 4, 2026 Elevated error rates affecting up to half of our customers 28m Web App, API, Email, Reporting Dashboards and 2 more

Started Sep 04, 2026, 05:50 PM UTC· resolved Sep 04, 2026, 06:18 PM UTC

  1. identified Sep 04, 2026, 05:50 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Sep 04, 2026, 05:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 04, 2026, 06:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 4, 2026 Elevated error rates –

Started Sep 04, 2026, 08:30 AM UTC· resolved Sep 04, 2026, 08:30 AM UTC

  1. resolved Sep 04, 2026, 01:04 PM UTC

    There have been reports of an elevated number of errors across the application.

Read the full incident report →

Major August 5, 2026 Elevated 500 errors being reported 1h 9m Web App, API, Email, Reporting Dashboards and 2 more

Started Aug 05, 2026, 05:15 PM UTC· resolved Aug 05, 2026, 06:24 PM UTC

  1. investigating Aug 05, 2026, 05:15 PM UTC

    We are currently investigating this issue.

  2. identified Aug 05, 2026, 05:35 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 05, 2026, 05:54 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 05, 2026, 06:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 2, 2026 System Unavailable 4h 26m Web App, API, Email, Reporting Dashboards and 2 more

Started Aug 02, 2026, 04:15 PM UTC· resolved Aug 02, 2026, 08:41 PM UTC

  1. investigating Aug 02, 2026, 04:40 PM UTC

    We are currently investigating the issue.

  2. identified Aug 02, 2026, 05:16 PM UTC

    The issue has been identified and we are working to remediate the issue.

  3. identified Aug 02, 2026, 07:45 PM UTC

    We're currently rolling out a fix across the affected environments.

  4. monitoring Aug 02, 2026, 08:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 02, 2026, 08:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 30, 2025 Login and performance issues 38m Web App

Started Oct 30, 2025, 05:59 PM UTC· resolved Oct 30, 2025, 06:37 PM UTC

  1. investigating Oct 30, 2025, 05:59 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 30, 2025, 06:00 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Oct 30, 2025, 06:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 30, 2025, 06:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 29, 2025 Cloud service provider disruption 21h 4m Web App, API, Email, Reporting Dashboards and 2 more

Started Oct 29, 2025, 04:24 PM UTC· resolved Oct 30, 2025, 01:28 PM UTC

  1. investigating Oct 29, 2025, 04:24 PM UTC

    We're currently investigation an incident with one of our cloud providers.

  2. monitoring Oct 29, 2025, 04:48 PM UTC

    We have implemented a workaround to the cloud provider incident and are monitoring the situation.

  3. resolved Oct 30, 2025, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 2, 2025 Disruption of Service 52m Web App, API, Email, Reporting Dashboards and 2 more

Started Oct 02, 2025, 02:27 PM UTC· resolved Oct 02, 2025, 03:19 PM UTC

  1. investigating Oct 02, 2025, 02:35 PM UTC

    We are currently investigating this issue.

  2. identified Oct 02, 2025, 02:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 02, 2025, 03:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 02, 2025, 03:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 29, 2025 General slowness with the API 2h 1m API

Started Sep 29, 2025, 12:59 PM UTC· resolved Sep 29, 2025, 03:01 PM UTC

  1. investigating Sep 29, 2025, 12:59 PM UTC

    We are currently investigating the issue.

  2. identified Sep 29, 2025, 01:03 PM UTC

    The issue has been identified and a solution is being implemented.

  3. identified Sep 29, 2025, 02:19 PM UTC

    We are starting the deployment of our fix to the performance issue

  4. monitoring Sep 29, 2025, 02:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Sep 29, 2025, 03:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 14, 2025 Temporary Downtime During Update 41m Web App, API, Mobile

Started Apr 14, 2025, 03:57 PM UTC· resolved Apr 14, 2025, 04:38 PM UTC

  1. identified Apr 14, 2025, 03:57 PM UTC

    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.

  2. identified Apr 14, 2025, 04:00 PM UTC

    The main application should be available now and we are still working through the other services

  3. monitoring Apr 14, 2025, 04:11 PM UTC

    A fix has been implemented and we are now monitoring.

  4. resolved Apr 14, 2025, 04:38 PM UTC

    This incident has been resolved. Again. We sincerely apologize for this interruption and any inconvenience this may have caused.

Read the full incident report →

Notice March 10, 2025 Temporary Calendar Inaccessibility Due to Hotfix –

Started Mar 10, 2025, 02:30 PM UTC· resolved Mar 10, 2025, 02:30 PM UTC

  1. resolved Mar 10, 2025, 03:02 PM UTC

    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.

Read the full incident report →

Major November 19, 2024 Logging in to Mapping results in a 502 error 18m Mapping, Mobile

Started Nov 19, 2024, 07:06 PM UTC· resolved Nov 19, 2024, 07:25 PM UTC

  1. investigating Nov 19, 2024, 07:06 PM UTC

    We're currently investigating reports of customers that are receiving a 502 error while logging into Mapping and Mobile.

  2. investigating Nov 19, 2024, 07:09 PM UTC

    We are continuing to investigate this issue.

  3. identified Nov 19, 2024, 07:13 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Nov 19, 2024, 07:18 PM UTC

    We have implemented a fix and are continuing to monitor.

  5. resolved Nov 19, 2024, 07:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 23, 2024 Database failover 23h 14m Web App, API, Reporting Dashboards

Started Oct 23, 2024, 01:57 PM UTC· resolved Oct 24, 2024, 01:11 PM UTC

  1. investigating Oct 23, 2024, 01:57 PM UTC

    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

  2. resolved Oct 24, 2024, 01:11 PM UTC

    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.

Read the full incident report →