Fulfil.IO Outage History

Started Sep 11, 2026, 03:59 PM UTC· resolved Sep 11, 2026, 07:37 PM UTC

1. investigating Sep 11, 2026, 03:59 PM UTC

   We are currently seeing errors being reported for certain workspaces affecting connectivity. We are currently investigating the issue and will follow up with further updates shortly.

2. investigating Sep 11, 2026, 04:00 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 11, 2026, 04:23 PM UTC

   We are seeing workspace performance is recovering. The specific workspaces reporting 404 errors should now be operational as expected. We are continuing to monitor these workspaces remain stable.

4. resolved Sep 11, 2026, 07:37 PM UTC

   The incident has been resolved. We've continued to monitor through this period from the last update and see no further impact. A subset of workspaces experienced 404 errors when accessing the ERP and calling the API. The underlying issue was identified and our team is currently conducting an internal review to determine the full root cause.

Read the full incident report →

Started Jul 23, 2026, 03:54 PM UTC· resolved Jul 23, 2026, 08:41 PM UTC

1. investigating Jul 23, 2026, 03:54 PM UTC

   EasyPost is experiencing network connectivity issues and is investigating. Any carrier action such as rating or label generation may fail. If shipments need to urgently be fulfilled, we recommend switching to a different carrier while Easypost continues to investigate. More updates can be found here: https://www.easypoststatus.com/

2. resolved Jul 23, 2026, 08:41 PM UTC

   Easypost is reporting their services have started to recover and previous failing actions should start working again. For additional details into the connectivity errors, the EasyPost status page has more detailed information https://www.easypoststatus.com/

Read the full incident report →

Started Jun 11, 2026, 09:23 AM UTC· resolved Jun 11, 2026, 11:02 AM UTC

1. investigating Jun 11, 2026, 09:23 AM UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. monitoring Jun 11, 2026, 09:29 AM UTC

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

3. resolved Jun 11, 2026, 11:02 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 28, 2026, 04:28 PM UTC· resolved May 28, 2026, 05:09 PM UTC

1. identified May 28, 2026, 04:28 PM UTC

   The issue has been identified and we are coordinating with FedEx

2. identified May 28, 2026, 04:32 PM UTC

   We are currently experiencing rate limiting from FedEx at the application level, which is impacting all customers using our FedEx v2 integration. This is affecting label generation, rate quotes, and tracking calls routed through FedEx v2. *What is working* All other carrier integrations (UPS, USPS, DHL, and all non-FedEx carriers) are operating normally. FedEx v1 integration is unaffected. *What is not working* API calls to FedEx v2 are being throttled by FedEx, resulting in failed or delayed responses for affected operations. *Root cause* FedEx is enforcing a rate limit at the application level on our integration. This is a limit imposed by FedEx, not a Fulfil-side capacity issue. *What we are doing* We are in active contact with FedEx and have been escalated to their Account Executives to request a rate limit increase. We do not yet have a confirmed timeline or the specific requirements FedEx will ask for to raise the limit. *What you can do in the interim* * If you have a FedEx v1 connection configured, you can route shipments through it as a temporary workaround. * For time-sensitive shipments, consider routing through an alternate carrier integrations. *How you can help* Contact your FedEx account representative directly. Customer escalations to FedEx carry significant weight, often more than ours. If you have a dedicated FedEx AE or account manager, please reach out and reference this issue. Specifically, ask them to: * Flag the rate limit applied to Fulfil's FedEx Web Services / FedEx API v2 integration affecting your account. * Escalate to FedEx's API/Developer Support team on your behalf. * Request that FedEx prioritize the rate limit increase request currently in progress with Fulfil.

3. identified May 28, 2026, 04:54 PM UTC

   We are currently on a live call with FedEx working through the rate limit issue. We will post a update as soon as the call concludes. FedEx v2 remains impacted; all other carriers and FedEx v1 remain operational.

4. resolved May 28, 2026, 05:09 PM UTC

   FedEx has increased the rate limit on our v2 integration effective now. FedEx v2 API calls are returning successfully and label generation, rate quotes, and tracking are operating normally.

Read the full incident report →

Started May 08, 2026, 11:00 AM UTC· resolved May 08, 2026, 11:00 AM UTC

1. resolved May 08, 2026, 02:51 PM UTC

   Earlier today, some print templates failed to convert to PDF. Retries usually worked. The print template system needs every asset (stylesheets, logos, barcodes) to load before it can produce a PDF. If one asset failed, the whole PDF failed. Two things were causing assets to fail: 1. our barcode service was returning errors on some request shapes after a library upgrade. 2. and some customer logos (and other assets) hosted on AWS were intermittently unavailable. We've fixed the barcode service. It now handles the request shapes the template renderer sends and retries once on a transient error. The AWS issue resolved on its own. Longer term, we want the renderer to keep going when an asset fails (e.g. fall back to a placeholder). We can't change the current renderer's behavior without risking layout shifts in your existing templates, so we're building a new version alongside it. The renderer will be versioned, and you'll be able to move templates over when you're ready. We're also adding monitoring on the barcode service and on template-render success rates so we catch this faster next time. Sorry for the disruption. If a print is still failing for you from this window, please retry. Contact support if it still doesn't work.

Read the full incident report →

Started Feb 12, 2026, 02:11 PM UTC· resolved Feb 12, 2026, 03:51 PM UTC

1. investigating Feb 12, 2026, 02:11 PM UTC

   We are currently investigating reports of 404 errors occurring on some instances. Our team has been notified and is actively working to identify the root cause. We will provide updates as more information becomes available.

2. investigating Feb 12, 2026, 02:18 PM UTC

   We are continuing to investigate this issue.

3. identified Feb 12, 2026, 02:44 PM UTC

   We have identified an issue affecting some workspaces, causing 404 errors. The issue has been traced to a specific database infrastructure component. Our engineering team is actively working on a resolution to restore service. We will continue to provide updates as we have more information.

4. monitoring Feb 12, 2026, 03:27 PM UTC

   The issue with the specific database infrastructure component has been resolved. Affected workspaces should be working as expected and no longer returning the 404 error. Our team is currently monitoring for any further errors.

5. resolved Feb 12, 2026, 03:51 PM UTC

   The incident has been resolved. After monitoring, our team has confirmed all components are operational and workspaces working as expected.

Read the full incident report →

Started Nov 18, 2025, 12:02 PM UTC· resolved Nov 18, 2025, 03:38 PM UTC

1. identified Nov 18, 2025, 12:02 PM UTC

   Prominent cloud service cloudflare is down. https://www.cloudflarestatus.com/ This seems to have brought down a bunch of cloud services that merchants use including Shippo and 3PLs that use Cloudflare like Deposco. Our favorite AIs are also down which could have written a better message.

2. identified Nov 18, 2025, 12:06 PM UTC

   Updating incident to Major since shopify also seems to be affected. Stripe is only reporting "elevated error messages" but is actually down as well.

3. identified Nov 18, 2025, 12:37 PM UTC

   We’re seeing degraded performance for this component caused by the Cloudflare outage. We’re monitoring and will update as conditions improve.

4. identified Nov 18, 2025, 01:36 PM UTC

   We’re seeing degraded performance for this component caused by the Cloudflare outage. We’re monitoring and will update as conditions improve.

5. monitoring Nov 18, 2025, 02:54 PM UTC

   Cloudflare has reported a fix has been implemented for the previous network issues https://www.cloudflarestatus.com/ external integrations should begin recovering back to normal shortly. We will continue to monitor for any additional related errors.

6. resolved Nov 18, 2025, 03:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:27 PM UTC· resolved Jun 12, 2025, 10:02 PM UTC

1. identified Jun 12, 2025, 06:27 PM UTC

   There appears to be an issue with Google Cloud Platform. We are working with them and determining impact. Also seems to have affected Shopify

2. identified Jun 12, 2025, 06:28 PM UTC

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

3. identified Jun 12, 2025, 06:32 PM UTC

   GCP still has not updated their status page or provided an explanation on what is causing the outage. Widespread issues are reported by Shopify as well: https://www.shopifystatus.com/incidents

4. monitoring Jun 12, 2025, 06:56 PM UTC

   We are seeing the printing service recover. PDF generation and attachments seem to be working. We are closely monitoring the status.

5. resolved Jun 12, 2025, 10:02 PM UTC

   Google cloud has reported that most services have recovered and are back to normal. For additional information regarding the service disruption, please follow along GCP's status page https://status.cloud.google.com/

Read the full incident report →

Started Feb 24, 2025, 02:49 PM UTC· resolved Feb 24, 2025, 03:57 PM UTC

1. investigating Feb 24, 2025, 02:49 PM UTC

   We are currently investigating reported errors affecting the Fulfil Channels app. Active integrations connected only through the Channels app may experience delays in synchronizing information to the channel. We will provide updates as more information becomes available.

2. resolved Feb 24, 2025, 03:57 PM UTC

   Our team has resolved the root cause of the error affecting the Channels app. Integrations connected should see data synced as expected going forward.

Read the full incident report →