Is Fulfil.IO down?

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

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

This incident has been resolved.

The issue has been identified and we are coordinating with FedEx

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.

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.

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.

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

We are continuing to investigate 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.

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.