Keypup Outage History

Keypup is up right now

Pingoru has recorded 6 incidents for Keypup: 3 in the last 12 months and 0 in the last 90 days.

Source: status.keypup.io

6incidents recorded
3last 12 months
0last 90 days
14 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Keypup in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 98 (0%)

Incidents, newest first

Notice February 20, 2026 Delayed Updates 1d 8h Data & Reporting

Started Feb 20, 2026, 01:01 PM UTC· resolved Feb 21, 2026, 09:57 PM UTC

  1. monitoring Feb 20, 2026, 01:01 PM UTC

    Google Cloud Platform is currently having issues with services related to background jobs, on which Keypup relies. This results in an elevated error rate in the data processing jobs, with a high number of jobs failing or being retried. We are monitoring the situation and will reprocess application updates since Thursday once the incident is over on the GCP side.

  2. monitoring Feb 20, 2026, 03:31 PM UTC

    Data updates have been paused while we are processing a large backlog of jobs. Job processing is slowed down due to continued issues on Google Cloud Platform.

  3. monitoring Feb 20, 2026, 06:13 PM UTC

    We have re-enabled data updates from third-party applications and are continuing to clear the backlog of jobs. On the reporting side, the loading of insights may feel slower due to the following: - The auto-refresh mechanism of dashboard insights is currently disabled. Insights will only be refreshed upon reloading the page (or visiting another dashboard, then coming back) - The ahead-of-time caching of dashboard insights is currently disabled. Insights are live-loaded if data has changed since the last load.

  4. monitoring Feb 21, 2026, 05:43 AM UTC

    We continue the process the pending backlog and will provide another update in the next few hours.

  5. monitoring Feb 21, 2026, 04:13 PM UTC

    The processing of the remaining backlog is almost over. Once processed, the team will trigger a job to reprocess the application updates for the last few days to ensure no updates were missed.

  6. monitoring Feb 21, 2026, 05:54 PM UTC

    The processing backlog has been cleared, and our team is now reprocessing the last few days of updates to ensure no data updates were missed.

  7. resolved Feb 21, 2026, 09:57 PM UTC

    The application updates have been reprocessed, and the platform has resumed normal operations.

Read the full incident report →

Minor December 8, 2025 Data update delays 3h 25m Platform (HQ), Data & Reporting

Started Dec 08, 2025, 05:44 PM UTC· resolved Dec 08, 2025, 09:10 PM UTC

  1. identified Dec 08, 2025, 05:44 PM UTC

    The team identified a rogue process on one of our databases tampering with index performance and causing delays in our processing pipeline. The team is currently taking actions to fix this and restore normal service. This action will involve a component restart, which means some platform components will be briefly unavailable.

  2. monitoring Dec 08, 2025, 06:22 PM UTC

    The team has performed maintenance activities on the database to restore performance. The system is currently catching up on updates from the last two hours.

  3. resolved Dec 08, 2025, 09:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025 Cloudflare Incident 4h 45m Platform (HQ), Data & Reporting

Started Nov 18, 2025, 02:04 PM UTC· resolved Nov 18, 2025, 06:50 PM UTC

  1. identified Nov 18, 2025, 02:04 PM UTC

    Intermittent traffic issues are preventing users from accessing the platform. This is due to a global outage on the Clouflare side. Cloudflare incident status page: https://www.cloudflarestatus.com/

  2. monitoring Nov 18, 2025, 02:51 PM UTC

    Cloudflare has implemented a fix and is currently monitoring traffic through their network.

  3. resolved Nov 18, 2025, 06:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 5, 2025 Jira API returns empty issue list - Outdated Jira reports 1d Data & Reporting

Started Sep 05, 2025, 10:30 AM UTC· resolved Sep 06, 2025, 11:16 AM UTC

  1. identified Sep 05, 2025, 10:30 AM UTC

    The Jira API is currently in the middle of an incident, returning an empty list of issues on the /search API endpoint. Other API endpoints are fine and returning data. This problem occurs for most customers but not all. We believe this issue started occurring on September 4th around 4 pm UTC, as Atlassian deployed a fix for another incident occuring the same day. Jira-related reports are still available on Keypup. However, we are currently not receiving updates for Jira issues. Jira-related reports will show information as of September 4th. We have reached out to the Atlassian team, provided a full incident report, and are waiting for next steps.

  2. monitoring Sep 05, 2025, 05:29 PM UTC

    The issue retrieval flow has resumed normal operations. We are currently monitoring the logs to ensure proper activity. A resync of Jira projects will take place during the weekend to ensure the data are up to date.

  3. resolved Sep 06, 2025, 11:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 11, 2025 Delayed processing of third-party updates 17h 44m Platform (HQ), Data & Reporting

Started Mar 11, 2025, 04:40 PM UTC· resolved Mar 12, 2025, 10:24 AM UTC

  1. investigating Mar 11, 2025, 04:40 PM UTC

    We're currently investigating an elevated load on our databases related to third-party data processing.

  2. identified Mar 11, 2025, 04:59 PM UTC

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

  3. monitoring Mar 11, 2025, 07:52 PM UTC

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

  4. resolved Mar 12, 2025, 10:24 AM UTC

    This incident has been resolved.

Read the full incident report →