Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Buddy outage history

    7 recorded Buddy incidents since October 2023, with official updates, affected components, duration and resolution information.

    Back to current status

    [US Data Center] We are investigating reports of API degraded performance

    Started January 20, 2026 at 2:56 PM UTC · 23m

    IssuesMinor incident
    1. January 20, 2026 at 2:56 PM UTCinvestigating

      [US Data Center] We are investigating reports of Pipelines degraded performance

    2. January 20, 2026 at 3:20 PM UTCresolved

      This incident has been resolved.

    [US Data Center] Incident with Pipelines

    Started September 25, 2025 at 5:10 AM UTC · 26m

    OutageMajor incident
    1. September 25, 2025 at 5:10 AM UTCinvestigating

      We are currently experiencing a service outage affecting the Buddy.works platform. Our application is temporarily unavailable due to network connectivity problems in our primary datacenter.

    2. September 25, 2025 at 5:36 AM UTCresolved

      We are pleased to confirm that the platform has been fully restored and is now operating normally. All services are back online and functioning as expected.

    [US Data Center] Incident with Pipelines

    Started May 5, 2025 at 8:51 AM UTC · 2h 54m

    OutageMajor incident
    1. May 5, 2025 at 8:51 AM UTCresolved

      We are currently experiencing a service outage in our US region due to network connectivity issues. Our technical team has identified the root cause and is actively working to restore full functionality. We apologize for any inconvenience this may cause and appreciate your patience while we resolve this matter. We will provide updates as soon as service is restored.

    2. May 5, 2025 at 11:45 AM UTCresolved

      Buddy is back online. We apologize for the inconvenience.

    [US Data Center] We are investigating reports of Pipelines degraded performance

    Started June 4, 2024 at 5:28 AM UTC · 30m

    IssuesMinor incident
    1. June 4, 2024 at 5:28 AM UTCinvestigating

      We are currently investigating this issue.

    2. June 4, 2024 at 5:58 AM UTCresolved

      This incident has been resolved.

    [US Data Center] We are investigating reports of Pipelines degraded performance

    Started November 28, 2023 at 5:20 PM UTC · 3h 39m

    IssuesMinor incident
    1. November 28, 2023 at 5:20 PM UTCinvestigating

      Some customers experience network problems in pipelines. We are currently investigating this issue.

    2. November 28, 2023 at 6:14 PM UTCinvestigating

      The problem is solely related to WPEngine servers. WPEngine is blocking SFTP and SSH operations from our servers. We are currently communicating with them about this issue.

    3. November 28, 2023 at 9:00 PM UTCresolved

      Our IPs were unblocked by WPEngine. We are in contact with the WPEngine team to prevent this kind of issues in feature

    [US Data Center] We are investigating reports of Git degraded performance

    Started November 14, 2023 at 8:34 PM UTC · 11m

    IssuesMinor incident
    1. November 14, 2023 at 8:34 PM UTCinvestigating

      We are currently investigating this issue.

    2. November 14, 2023 at 8:45 PM UTCresolved

      The issue has been resolved. More details: Our alerting systems detected a problem with In-Memory Data Grid on one of git servers. During the incident, some customers experienced delays/timeouts in the application. The root cause a was network issues. We have taken internal actions to prevent a recurrence in the future.

    [US Data Center] We are investigating reports of Website degraded performance

    Started October 11, 2023 at 8:33 PM UTC · 21m

    IssuesMinor incident
    1. October 11, 2023 at 8:33 PM UTCinvestigating

      We are currently investigating this issue.

    2. October 11, 2023 at 8:54 PM UTCresolved

      The issue has been resolved. More details: Our alerting systems detected an increase in the time of API responses. During the incident, some customers experienced delays/timeouts in the application. The root cause was network issues on one of our internal API servers. We have replaced it with a new one. We have taken internal actions to prevent a recurrence in the future.