Sunsama Outage History

Sunsama is up right now

Sunsama had 3 outages in the last 2 years totaling 5h 3m of downtime — averaging 0.1 incidents per month.

There were 3 Sunsama outages since September 13, 2024 totaling 5h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://sunsamastatus.com

Minor August 17, 2026

Calendar can appear empty

Detected by Pingoru
Aug 17, 2026, 10:57 AM UTC
Resolved
Aug 17, 2026, 12:46 PM UTC
Duration
1h 48m
Affected: WebDesktopMobile
Timeline · 4 updates
  1. investigating Aug 17, 2026, 10:57 AM UTC

    We are currently investigating this issue.

  2. identified Aug 17, 2026, 11:46 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 17, 2026, 12:24 PM UTC

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

  4. resolved Aug 17, 2026, 12:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 24, 2026

Timeboxing broken in Desktop app

Detected by Pingoru
Mar 24, 2026, 02:30 PM UTC
Resolved
Mar 24, 2026, 04:03 PM UTC
Duration
1h 33m
Affected: WebDesktopMobile
Timeline · 2 updates
  1. investigating Mar 24, 2026, 02:30 PM UTC

    We're seeing a problem with the desktop app version 3.3.5 where time boxing isn't working.

  2. resolved Mar 24, 2026, 04:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 13, 2024

Gmail & Google Calendar Outage

Detected by Pingoru
Sep 13, 2024, 04:44 PM UTC
Resolved
Sep 13, 2024, 06:26 PM UTC
Duration
1h 42m
Affected: Google CalendarGoogle Gmail
Timeline · 3 updates
  1. investigating Sep 13, 2024, 04:44 PM UTC

    The Gmail and Google Calendar APIs have started responding with errors. We are investigating the issue and will report back when we know more.

  2. monitoring Sep 13, 2024, 04:56 PM UTC

    The issue has been fixed however the root cause is undetermined. We will continue monitoring things in case it returns.

  3. resolved Sep 13, 2024, 06:26 PM UTC

    This incident has been resolved.

Read the full incident report →