Flxpoint Outage History

Flxpoint is up right now

Flxpoint had 19 outages in the last 2 years totaling 156h 31m of downtime, averaging 0.8 incidents per month.

There were 19 Flxpoint outages since October 24, 2024 totaling 156h 31m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.flxpoint.com

Critical October 15, 2026

Webhooks not processing

Detected by Pingoru
Oct 15, 2026, 03:41 PM UTC
Resolved
Oct 15, 2026, 03:54 PM UTC
Duration
12m
Affected: Webhooks
Timeline · 3 updates
  1. identified Oct 15, 2026, 03:41 PM UTC

    Webhooks stopped processing at 2026-10-14 15:00 UTC Root cause has been identified and is being fixed.

  2. resolved Oct 15, 2026, 03:54 PM UTC

    All delayed webhooks have been processed and the incident is fully resolved.

  3. postmortem Oct 15, 2026, 03:56 PM UTC

    **What happened** From Oct 15, 00:10 UTC to Oct 15, 15:49 UTC, Order Imported and Fulfillment Request Processing webhooks were delayed. **Impact** These webhooks weren't sent during that window. Orders kept importing and processing normally, and no data was lost. Once the issue was fixed, all delayed webhooks were delivered, so you may have received a burst of older events. **Cause** Our cloud provider replaced the server that sends webhooks, and the new server didn't start correctly. Our monitoring didn't catch it. **Resolution** We restored the webhook service, and all delayed notifications were delivered by 15:49 UTC. **Next steps** We're adding alerts for delayed webhook delivery and fixing the deployment issue that kept the replacement server from starting. If your system was unavailable while we caught up and you're missing events, contact support and we'll resend them.

Read the full incident report →

Critical October 9, 2026

FTP Connectivity Issues

Detected by Pingoru
Oct 09, 2026, 12:45 PM UTC
Resolved
Oct 09, 2026, 01:14 PM UTC
Duration
28m
Affected: FTP Service
Timeline · 3 updates
  1. identified Oct 09, 2026, 01:19 PM UTC

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

  2. resolved Oct 09, 2026, 01:22 PM UTC

    This incident has been resolved.

  3. postmortem Oct 09, 2026, 04:10 PM UTC

    # RCA The root EBS volume on the FileMage gateway was provisioned at 8 GB and ran out of space. Once full, the server could no longer write session data and began returning HTTP 500 on the portal, and remote shell access to the host was also lost. The condition was not caught by monitoring. # Impact Third-party services and internal Flxpoint services were unable to read or write files from the FTP service during the outage window. All existing files at rest on the FTP server were not affected nor corrupted. # Future The root volume has been increased from 8 GB to 50 GB. Disk and inode usage monitors now alerts at 80% utilisation, well ahead of any failure.

Read the full incident report →

Critical September 21, 2026

AWS Outage Impacting Automation Jobs

Detected by Pingoru
Sep 21, 2026, 11:46 PM UTC
Resolved
Sep 22, 2026, 02:13 AM UTC
Duration
2h 26m
Affected: Automation
Timeline · 5 updates
  1. investigating Sep 21, 2026, 11:46 PM UTC

    We are currently experiencing an incident due to a major AWS outage. This outage is affecting our Automation Jobs, resulting in delays and failures in job execution.

  2. investigating Sep 22, 2026, 12:18 AM UTC

    We are actively monitoring the situation and working with our cloud provider for a resolution.

  3. monitoring Sep 22, 2026, 12:51 AM UTC

    We’re seeing signs of recovery — Automation Jobs have started executing again. However, we are continuing to closely monitor the progress to ensure full stability. We’ll share another update once all systems have completely recovered.

  4. monitoring Sep 22, 2026, 12:52 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Sep 22, 2026, 02:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 26, 2026

Scheduled jobs are taking longer than usual to start

Detected by Pingoru
Aug 26, 2026, 07:11 PM UTC
Resolved
Aug 26, 2026, 09:05 PM UTC
Duration
1h 54m
Affected: Automation
Timeline · 3 updates
  1. investigating Aug 26, 2026, 07:11 PM UTC

    We are currently looking into why some scheduled jobs are taking longer than expected to start

  2. monitoring Aug 26, 2026, 08:04 PM UTC

    Jobs are now scheduled and being picked up in a timely fashion. We will continue monitoring to ensure nominal performance over the coming hours.

  3. resolved Aug 26, 2026, 09:05 PM UTC

    Jobs are scheduling and beginning execution in a timely fashion.

Read the full incident report →

Major August 14, 2026

Web Application Access Down

Detected by Pingoru
Aug 14, 2026, 11:00 AM UTC
Resolved
Aug 14, 2026, 11:45 AM UTC
Duration
45m
Timeline · 1 update
  1. resolved Aug 14, 2026, 11:44 AM UTC

    Starting at approximately 6:00AM EST our web services encountered cache exhaustion which caused a large sub-set of incoming requests to fail with 500 errors. Root cause was identified by 6:30AM EST and actions began to be taken. By 6:45AM EST the web application was back up and serving requests as expected. Preventive measures are being implemented to prevent the same class of errors from occurring again in the future.

Read the full incident report →

Minor December 3, 2025

Automation Job Delays

Detected by Pingoru
Dec 03, 2025, 07:10 PM UTC
Resolved
Dec 03, 2025, 09:10 PM UTC
Duration
2h
Affected: Automation
Timeline · 4 updates
  1. investigating Dec 03, 2025, 07:10 PM UTC

    We're currently experiencing delays in executing automation jobs. Jobs are being picked up and executed successfully, however, throughput is significantly reduced. We believe this is coming from our service provider AWS. Investigation is ongoing.

  2. investigating Dec 03, 2025, 08:33 PM UTC

    We are still investigating delayed automation job start times.

  3. monitoring Dec 03, 2025, 08:47 PM UTC

    The issue with our internal service provider AWS has been resolved and we are currently working on processing the large backlog of jobs that have accumulated and not been run since the incident was first identified. We are aiming to have the backlog processed and to be running within standard startup times by 4:30 PM EST.

  4. resolved Dec 03, 2025, 09:10 PM UTC

    The backlog of delayed automation jobs has now been caught up and our job startup times are back within normal ranges.

Read the full incident report →

Minor November 10, 2025

Degraded Performance November 10, 2025

Detected by Pingoru
Nov 10, 2025, 04:20 PM UTC
Resolved
Nov 10, 2025, 07:37 PM UTC
Duration
3h 16m
Affected: AutomationAPI
Timeline · 4 updates
  1. investigating Nov 10, 2025, 04:32 PM UTC

    We are experiencing an outage causing degraded performance in API and automations. We are actively working to resolve the issue.

  2. identified Nov 10, 2025, 06:41 PM UTC

    Our investigation shows that only Automation is affected at this time. Jobs are executing, but with significant delays. All API services remain fully operational. We are continuing to monitor the situation closely and will provide further updates as we make progress.

  3. monitoring Nov 10, 2025, 07:18 PM UTC

    Automation has now fully recovered, and all jobs are executing normally. We will continue to monitor the system to ensure stability.

  4. resolved Nov 10, 2025, 07:37 PM UTC

    All our services are now running as expected, and the incident has been fully resolved. We will continue to monitor the system to ensure continued stability.

Read the full incident report →

Minor October 3, 2025

Degraded Performance October 3, 2025

Detected by Pingoru
Oct 03, 2025, 03:14 PM UTC
Resolved
Oct 03, 2025, 03:30 PM UTC
Duration
16m
Affected: AutomationAppAPIEventsWebhooks
Timeline · 2 updates
  1. investigating Oct 03, 2025, 03:14 PM UTC

    We are experiencing an outage causing degraded performance in our front-end app, API and automations. We are actively working to identify and resolve the issue.

  2. resolved Oct 03, 2025, 03:38 PM UTC

    All platform layers are now back to normal.

Read the full incident report →

Major October 1, 2025

Degraded Performance October 1, 2025

Detected by Pingoru
Oct 01, 2025, 02:53 PM UTC
Resolved
Oct 01, 2025, 03:30 PM UTC
Duration
37m
Affected: AutomationAppAPIEventsWebhooks
Timeline · 4 updates
  1. investigating Oct 01, 2025, 02:53 PM UTC

    We are experiencing an outage causing degraded performance in our front-end app, API and automations. We are actively working to identify and resolve the issue.

  2. investigating Oct 01, 2025, 02:53 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 01, 2025, 03:24 PM UTC

    All platform layers are now back to normal, except automation/jobs, which are still in the process of catching up. Our team is closely monitoring the system, and we’ll provide further updates as the remaining jobs stabilize.

  4. resolved Oct 01, 2025, 04:10 PM UTC

    A fix has been deployed and app access has been restored are now performing as expected. We are monitoring our systems and will provide another update.

Read the full incident report →

Major September 30, 2025

Degraded Performance September 30, 2025

Detected by Pingoru
Sep 30, 2025, 04:24 PM UTC
Resolved
Sep 30, 2025, 04:38 PM UTC
Duration
14m
Affected: AutomationAppAPIEventsWebhooks
Timeline · 2 updates
  1. investigating Sep 30, 2025, 04:24 PM UTC

    We are experiencing an outage causing degraded performance in our front-end app, API and automations. We are actively working to identify and resolve the issue.

  2. resolved Sep 30, 2025, 04:38 PM UTC

    A fix has been deployed and app access has been restored are now performing as expected. We are monitoring our systems and will provide another update.

Read the full incident report →

Major September 24, 2025

Degraded Performance September 24-25, 2025

Detected by Pingoru
Sep 24, 2025, 10:00 AM UTC
Resolved
Sep 24, 2025, 03:00 PM UTC
Duration
5h
Timeline · 1 update
  1. resolved Sep 25, 2025, 10:49 PM UTC

    On September 24th at 10:00 UTC, Flxpoint experienced degraded performance that resulted in increased latency in our app, automations, and API. The root cause was identified and a resolution was deployed today, September 25th at 15:00 UTC. Our team is monitoring the situation to ensure performance is stabilized and the incident is fully mitigated.

Read the full incident report →

Major August 8, 2025

August 9-10 Partial Outage

Detected by Pingoru
Aug 08, 2025, 06:00 PM UTC
Resolved
Aug 08, 2025, 06:00 PM UTC
Duration
–
Timeline · 1 update
  1. resolved Aug 11, 2025, 03:36 PM UTC

    Due to a communication issue with our database, we experienced a partial services outage, which was resolved Saturday, August 10 at 3pm UTC. We continue to monitor the database and app performance, but have not observed any errors in the past 24 hours.

Read the full incident report →

Minor July 27, 2025

Degraded Performance July 27-28, 2025

Detected by Pingoru
Jul 27, 2025, 04:00 PM UTC
Resolved
Jul 27, 2025, 04:00 PM UTC
Duration
–
Timeline · 1 update
  1. resolved Jul 28, 2025, 10:09 PM UTC

    Our cloud services provider experienced a networking issue on Sunday that caused degraded performance in our app, automation and API. Full performance has been restored as of 4 PM ET today, and we are monitoring the situation with our cloud provider to prevent further disruptions.

Read the full incident report →

Major March 13, 2025

March 13th 2025 Partial Outage

Detected by Pingoru
Mar 13, 2025, 01:31 PM UTC
Resolved
Mar 13, 2025, 04:50 PM UTC
Duration
3h 19m
Affected: App
Timeline · 3 updates
  1. investigating Mar 13, 2025, 01:31 PM UTC

    App access is currently unavailable. We are investigating the root cause and will share more updates as we have them.

  2. monitoring Mar 13, 2025, 01:38 PM UTC

    App access has been restored and the incident has been resolved.

  3. resolved Mar 13, 2025, 04:50 PM UTC

    We experienced a temporary outage today due to a high number of new signups, which briefly affected app access. Our team has restored access and has taken steps to ensure stability in the event we experience an increase in volume of new customers signing up.

Read the full incident report →

Major December 9, 2024

Email Deliverability for Mail Sent Directly from Flxpoint

Detected by Pingoru
Dec 09, 2024, 05:00 PM UTC
Resolved
Dec 12, 2024, 06:49 PM UTC
Duration
3d 1h
Affected: Automation
Timeline · 6 updates
  1. identified Dec 09, 2024, 07:28 PM UTC

    12/09 12:00 PM EST : An isolated issue with Amazon Web Services is impacting email deliverability for emails sent directly from Flxpoint. This is affecting all email services provided through Flxpoint. We are working with AWS to restore services.

  2. identified Dec 10, 2024, 03:55 PM UTC

    We're continuing to work with Amazon Web Services to restore email deliverability. We do not have a timeline from them to share at this point, but will continue to provide updates.

  3. identified Dec 10, 2024, 07:01 PM UTC

    We have deployed a final change requested by Amazon Web Services and are awaiting their confirmation the email deliverability is restored. We will provide another update shortly.

  4. identified Dec 11, 2024, 12:22 AM UTC

    We continue to wait for Amazon Web Services to restore email deliverability, but do not have an ETA from them to share. We will share further updates as they become available.

  5. monitoring Dec 11, 2024, 09:01 AM UTC

    Email deliverability has been restored and emailed fulfillment requests are processing normally now. Any impacted FRs will either show status Processing Error or be stuck in a status Processing. Here are instructions on the actions to take to verify your FRs have sent: FR Status = Processing Error In the Fulfilment Request view of the order manager, filter to show all processing errors Leverage a date filter to ensure you don't reprocess old, unrelated FRs Select the FRs > Actions > Reprocess FR Status = Processing (and status remains processing despite the Send FRs job running: Run Send FRs and and confirm the FRs sent; no other action should be required Please reach out to [email protected] if you need assistance.

  6. resolved Dec 12, 2024, 06:49 PM UTC

    This incident has been fully resolved.

Read the full incident report →

Major December 6, 2024

Email deliverability for mail sent directly from Flxpoint

Detected by Pingoru
Dec 06, 2024, 12:00 PM UTC
Resolved
Dec 08, 2024, 12:13 AM UTC
Duration
1d 12h
Affected: Automation
Timeline · 2 updates
  1. identified Dec 06, 2024, 09:14 PM UTC

    An isolated issue with Amazon Web Services is impacting email deliverability. This is affecting notifications and Send Fulfillment Request operations that are configured to send through email. We are working with AWS to restore services.

  2. resolved Dec 08, 2024, 12:13 AM UTC

    Email deliverability has been restored and emailed fulfillment requests are processing normally now. Any impacted FRs will either show status Processing Error or be stuck in a status Processing. Here are instructions on the actions to take to verify your FRs have sent: FR Status = Processing Error In the Fulfilment Request view of the order manager, filter to show all processing errors Leverage a date filter to ensure you don't reprocess old, unrelated FRs Select the FRs > Actions > Reprocess FR Status = Processing (and status remains processing despite the Send FRs job running: Run Send FRs and and confirm the FRs sent; no other action should be required Please reach out to [email protected] if you need assistance.

Read the full incident report →

Major November 17, 2024

Automation Jobs Not Triggering and App Access Impacted

Detected by Pingoru
Nov 17, 2024, 02:43 PM UTC
Resolved
Nov 18, 2024, 02:42 PM UTC
Duration
23h 58m
Affected: AutomationApp
Timeline · 7 updates
  1. investigating Nov 17, 2024, 02:43 PM UTC

    We are experiencing an outage with our cloud hosting provider, AWS, that is causing our automation processes to not trigger off as expected. We are actively working with them to resolve the issue and will update this incident as progress is made.

  2. identified Nov 17, 2024, 02:55 PM UTC

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

  3. identified Nov 18, 2024, 11:55 AM UTC

    Some users have reported the inability to log in. We continue to actively work with AWS to resolve this outage.

  4. monitoring Nov 18, 2024, 12:32 PM UTC

    A resolution has been implemented with AWS. Scheduled jobs are running and app access has been restored for most users. We will continue to update you on progress.

  5. monitoring Nov 18, 2024, 12:56 PM UTC

    App access should be restored for all users. We are now implementing the resolution to our job automation components and will continue to provide updates as we progress.

  6. monitoring Nov 18, 2024, 02:11 PM UTC

    We are continuing to resolve remaining job automation issues.

  7. resolved Nov 18, 2024, 02:42 PM UTC

    The outage with Amazon Web Services has been resolved. All job automation is functioning correctly and full app access has been restored.

Read the full incident report →

Notice October 24, 2024

FLX Jobs App Down

Detected by Pingoru
Oct 24, 2024, 02:49 PM UTC
Resolved
Oct 24, 2024, 02:49 PM UTC
Duration
–
Affected: Automation
Timeline · 1 update
  1. resolved Oct 24, 2024, 02:49 PM UTC

    At approximately 8:50 AM EST, our automation began failing due to an issue caused by the latest deployment. Please be assured that all failed jobs have been successfully rescheduled, and the issue has now been resolved.

Read the full incident report →