Blueink incident
Elevated errors / service unavailable
Blueink experienced a minor incident on June 11, 2026, lasting 24m. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Jun 11, 2026, 08:22 PM UTC
The service is fully restored. A summary will follow. We apologize for the disruption.
- resolved Jun 11, 2026, 09:48 PM UTC
This incident was resolved as of 1:45 pm PT. ### Postmortem ### Summary On 2026-06-11, the Blueink Application was unavailable for approximately 23 minutes (from ~1:22pm to ~1:45pm PT). The root cause was that database schema update during a routine deploy locked a key table in our database. #### Impact During the window, requests to the application were blocked and most users were unable to access the service. No data was lost or corrupted. #### Resolution We safely stopped the operation — it rolled back cleanly with no data loss — which released the lock and immediately restored service. The schema change was deferred and has no impact on correct operation of the system. #### Remediation We've put safeguards in place to catch and prevent this class of issue going forward. All Blueink systems have been confirmed as operating correctly as of the resolution time of this incident.