Botkeeper Outage History

Botkeeper is up right now

Pingoru has recorded 50 incidents for Botkeeper: 0 in the last 12 months and 0 in the last 90 days.

Source: status.botkeeper.com

50incidents recorded
0last 12 months
0last 90 days
–typical duration

Incidents, newest first

Notice August 31, 2025 Elevated API Errors 1m

Started Aug 31, 2025, 06:36 PM UTC· resolved Aug 31, 2025, 06:37 PM UTC

  1. investigating Aug 31, 2025, 06:36 PM UTC

    We're experiencing an elevated level of API errors and are currently looking into the issue.

  2. resolved Aug 31, 2025, 06:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 27, 2025 Botkeeper Platform Login Issues 6h 42m Partner Platform

Started May 27, 2025, 02:14 PM UTC· resolved May 27, 2025, 08:56 PM UTC

  1. identified May 27, 2025, 02:14 PM UTC

    Users are reporting issues logging in to the Botkeeper platform. A critical vendor integration is experiencing technical issues, which is currently impacting users' ability to access our platform. We are monitoring this incident closely and expect to become fully operational as soon as the vendor reaches a resolution.

  2. monitoring May 27, 2025, 04:29 PM UTC

    The issue has been resolved with the vendor. We are continuing to monitor to ensure the system has fully recovered.

  3. resolved May 27, 2025, 08:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 6, 2025 SmartConnect Finicity Platform Issue 43m Smart Connect

Started Jan 06, 2025, 06:30 PM UTC· resolved Jan 06, 2025, 07:13 PM UTC

  1. investigating Jan 06, 2025, 06:30 PM UTC

    A potential platform issue impacting Finicity services is currently being investigated, and the Finicity team is actively working to resolve this issue. Botkeeper SmartConnect remains operational, but updated transactions and statements may be unavailable temporarily.

  2. identified Jan 06, 2025, 06:36 PM UTC

    Finicity has identified the root cause of the issue and is working to implement a fix.

  3. monitoring Jan 06, 2025, 07:00 PM UTC

    Finicity has implemented a fix and is validating the resolution.

  4. resolved Jan 06, 2025, 07:13 PM UTC

    This incident has been resolved.

Read the full incident report →