Stonly incident

General database performance degradation

Major Resolved View vendor source →

Stonly experienced a major incident on November 4, 2025 affecting Stonly Editor and Stonly customers KB's - location N and 1 more component, lasting 2h 50m. The incident has been resolved; the full update timeline is below.

Started
Nov 04, 2025, 01:32 PM UTC
Resolved
Nov 04, 2025, 04:22 PM UTC
Duration
2h 50m
Detected by Pingoru
Nov 04, 2025, 01:32 PM UTC

Affected components

Stonly EditorStonly customers KB's - location NStonly customers KB's - location CStonly AI BotStonly Contact FormsKnowledgebase searchStonly Guides

Update timeline

  1. investigating Nov 04, 2025, 01:32 PM UTC

    We are under a huge load, and some of our databases have degraded performance. We are applying modifications to the database systems. We will be back with further information in 15 minutes.

  2. investigating Nov 04, 2025, 01:43 PM UTC

    We are observing recovery symptoms, and will keep updating in the next 15 minutes

  3. monitoring Nov 04, 2025, 01:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Nov 04, 2025, 04:22 PM UTC

    The incident was fully resolved.