Writable Outage History

Writable is up right now

Pingoru has recorded 10 incidents for Writable: 2 in the last 12 months and 0 in the last 90 days.

Source: status.writable.com

10incidents recorded
2last 12 months
0last 90 days
63 minutestypical duration

Incidents, newest first

Major January 10, 2026 System performance impacted 27m

Started Jan 10, 2026, 08:29 PM UTC· resolved Jan 10, 2026, 08:56 PM UTC

  1. identified Jan 10, 2026, 08:29 PM UTC

    We are currently investing a system performance issue. Resources are being brought online to address the situation.

  2. monitoring Jan 10, 2026, 08:38 PM UTC

    The system is recovering.

  3. resolved Jan 10, 2026, 08:56 PM UTC

    System is back to fully operational.

Read the full incident report →

Minor January 9, 2026 Intercom Service Outage 1h 39m Intercom APIs (Help features), Intercom Chats and Posts (Help features)

Started Jan 09, 2026, 08:10 PM UTC· resolved Jan 09, 2026, 09:49 PM UTC

  1. identified Jan 09, 2026, 08:10 PM UTC

    A third-party vendor, Intercom, is experiencing a major service outage. This is affecting ability to get Live Support within the Writable app.

  2. monitoring Jan 09, 2026, 08:54 PM UTC

    Intercom has implemented a fix and is monitoring for recovery.

  3. monitoring Jan 09, 2026, 09:06 PM UTC

    Writable Live Support is functional once again, but messaging may be slow as the Intercom service continues to recover. Continuing to monitor as the feature improves.

  4. resolved Jan 09, 2026, 09:49 PM UTC

    Intercom has resolved the incident.

Read the full incident report →

Critical November 18, 2024 Application Unresponsive –

Started Nov 18, 2024, 03:26 PM UTC· resolved Nov 18, 2024, 03:26 PM UTC

  1. resolved Nov 18, 2024, 03:26 PM UTC

    Beginning at 6:10a PST, the Writable application started to become unresponsive for some users, gradually impacting more users over time. Our engineers were notified of issue reports at 6:27a PST and began investigating. The cause was identified by 6:47a PST and steps were immediately taken to correct the underlying cause. All metrics were back to normal at 6:43a PST.

Read the full incident report →