SleekFlow incident

⚠️ Disruption - Message Delivery Status and access to SleekFlow

Minor Resolved View vendor source →

SleekFlow experienced a minor incident on January 14, 2026, lasting 4h 4m. The incident has been resolved; the full update timeline is below.

Started
Jan 14, 2026, 02:55 AM UTC
Resolved
Jan 14, 2026, 06:59 AM UTC
Duration
4h 4m
Detected by Pingoru
Jan 14, 2026, 02:55 AM UTC

Update timeline

  1. investigating Jan 14, 2026, 02:55 AM UTC

    SleekFlow is currently experiencing an issue affecting message delivery and access since 14 Jan 2026 at 10:35 AM HKT**:** * **Message Syncing:** Outgoing messages may stay in a "loading" state, but are actually being sent to the end user. * **Incoming Messages:** New incoming messages are currently not being received in the platform. * **Interface:** Users may not be able to access the inbox. Our engineering team is actively investigating this matter. We will provide a further update as soon as additional information becomes available. We sincerely apologize for any inconvenience and appreciate your patience..

  2. identified Jan 14, 2026, 03:10 AM UTC

    Updated on 14 Jan 2026 **at 11:02 AM HKT** The team has applied mitigations, and the disruption is recovering. We will continue to monitor the status and provide updates as more information becomes available..

  3. resolved Jan 14, 2026, 06:59 AM UTC

    Updated on 14 Jan 2026 at 01:49 PM HKT**.** We can confirm the disruptions have been fully resolved. Thank you for your patience..