Live / Bynder / Incident
Bynder: Production Environment - All regions
Bynder · bynder.comMinor incidentResolved2026-10-20 21:12 UTC
Public — what happened
Summary
Bynder said it began investigating a problem with part of its production environment at 15:29 UTC on 20 October 2026, which it rated as minor. It later said it had found the cause, and that reading metadata from uploads on US-only portals was not working, so some uploads could get stuck. Bynder also reported that extracting clipping paths was unavailable and that downloads with embedded metadata might fail or be delayed, while everything else worked normally. A fix was put in place at 19:09 UTC and the incident was marked resolved at 21:12 UTC.
Affected
Uploads, Downloads, Global, US Only, EU Only
Timeline
- Started — 2026-10-20 15:29 UTC
- Investigating — 2026-10-20 15:29 UTC
- Identified — 2026-10-20 16:28 UTC (4 updates)
- Monitoring — 2026-10-20 19:09 UTC
- Resolved — 2026-10-20 21:12 UTC · 5h 43m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Bynder against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Bynder: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Bynder report →
More from Bynder
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.