Resolved after 2 hours 21 minutes, affecting Streaming and On-the-fly Packager and 1 more, on October 26, 2026.
Our engineers have confirmed that On-the-Fly Packaging (OTFP) has been fully restored. Customers may have experienced 503 errors from 16:36 to 18:57 UTC on October 26, 2026. This incident is resolved. Affected customers may have experienced impact to varying degrees and for a shorter duration than stated above Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team. Status Post, Created Date/Time: 2026-10-26 18:28:01 UTC
Affected components
Update timeline
- investigating Oct 26, 2026, 06:24 PM UTC
We are investigating an issue causing 503 errors for customers using On-the-Fly Packaging (OTFP). Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the next hour.
- investigating Oct 26, 2026, 06:51 PM UTC
Our engineers believe they have identified the contributing factor causing the issue impacting On-the-Fly Packaging (OTFP). Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.
- monitoring Oct 26, 2026, 07:05 PM UTC
The fix has been successfully deployed, and we have observed a recovery of On-the-Fly Packaging (OTFP). Error rates and latency have returned to nominal levels. Our team will continue to monitor the platform to ensure stability before we resolve this incident.
- resolved Oct 26, 2026, 07:14 PM UTC
Our engineers have confirmed that On-the-Fly Packaging (OTFP) has been fully restored. Customers may have experienced 503 errors from 16:36 to 18:57 UTC on October 26, 2026. This incident is resolved. Affected customers may have experienced impact to varying degrees and for a shorter duration than stated above Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team. Status Post, Created Date/Time: 2026-10-26 18:28:01 UTC
Your product runs on more than Fastly
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services