Balsamiq incident

Service down

Critical Resolved View vendor source →

Balsamiq experienced a critical incident on April 4, 2025 affecting Balsamiq Cloud and Balsamiq Collaboration Server, lasting 4h 8m. The incident has been resolved; the full update timeline is below.

Started
Apr 04, 2025, 10:05 AM UTC
Resolved
Apr 04, 2025, 02:13 PM UTC
Duration
4h 8m
Detected by Pingoru
Apr 04, 2025, 10:05 AM UTC

Affected components

Balsamiq CloudBalsamiq Collaboration Server

Update timeline

  1. investigating Apr 04, 2025, 10:05 AM UTC

    We are currently investigating this issue.

  2. investigating Apr 04, 2025, 10:11 AM UTC

    We have identified the issue and are working on restoring service. We expect this will take a couple of hours. We are sorry for the inconvenience.

  3. investigating Apr 04, 2025, 10:48 AM UTC

    We are still working on restoring service. Rest assure that no project data was deleted.

  4. investigating Apr 04, 2025, 11:50 AM UTC

    Still working on restoring service. Next update in 30m

  5. investigating Apr 04, 2025, 12:18 PM UTC

    Our engineers are still working on restoring service. Next update in 30m.

  6. identified Apr 04, 2025, 12:50 PM UTC

    We have identified the root cause to be a low-level network connectivity issue. We are working hard on restoring service. Next update in 30 minutes. Thank you for your patience.

  7. identified Apr 04, 2025, 01:24 PM UTC

    We are continuing to work on a fix for this issue. Next update in 30m.

  8. identified Apr 04, 2025, 01:54 PM UTC

    We are starting to see the light at the end of the tunnel. Internal sub-systems are restored, but the Balsamiq Cloud app isn't up quite yet. Next update in 30m.

  9. resolved Apr 04, 2025, 02:13 PM UTC

    Service is restored! We will monitor closely. Sorry for the inconvenience and happy wireframing (again).