Beanstalk Outage History

Beanstalk is up right now

Beanstalk had 17 outages in the last 2 years totaling 21h 37m of downtime — averaging 0.7 incidents per month.

There were 17 Beanstalk outages since May 8, 2025 totaling 21h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.beanstalkapp.com

Major February 14, 2026

We’re having issues with our Git SSH infrastructure at the moment. If you are unable to use Git over SSH, please switch over to using HTTPS protocol temporarily.

Detected by Pingoru
Feb 14, 2026, 02:48 PM UTC
Resolved
Feb 14, 2026, 03:52 PM UTC
Duration
1h 4m
Affected: Beanstalk
Timeline · 2 updates
  1. investigating Feb 14, 2026, 02:48 PM UTC

    We’re having issues with our Git SSH infrastructure at the moment. If you are unable to use Git over SSH, please switch over to using HTTPS protocol temporarily.

  2. resolved Feb 14, 2026, 03:52 PM UTC

    Our Git service over SSH should be back to normal now. Thank you for your patience.

Read the full incident report →

Major October 26, 2025

Based on the data we’re seeing this outage is considered resolved at this time. Thank you for your…

Detected by Pingoru
Oct 26, 2025, 03:37 PM UTC
Resolved
Oct 26, 2025, 03:37 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 26, 2025, 03:37 PM UTC

    Based on the data we’re seeing this outage is considered resolved at this time. Thank you for your patience! We’ll be doing a thorough investigation of this downtime to figure out how we can prevent this from happening again.

Read the full incident report →

Major October 26, 2025

Our web app is currently down due to a firewall equipment issue. Our datacenter team is investigating.

Detected by Pingoru
Oct 26, 2025, 02:08 PM UTC
Resolved
Oct 26, 2025, 04:37 PM UTC
Duration
2h 29m
Affected: Beanstalk
Timeline · 3 updates
  1. investigating Oct 26, 2025, 02:08 PM UTC

    Our web app is currently down due to a firewall equipment issue. Our datacenter team is investigating.

  2. monitoring Oct 26, 2025, 04:27 PM UTC

    Our web app is now accessible but the networking issue is not fully resolved yet, some packet loss is still present.

  3. resolved Oct 26, 2025, 04:37 PM UTC

    Based on the data we’re seeing this outage is considered resolved at this time. Thank you for your patience! We’ll be doing a thorough investigation of this downtime to figure out how we can prevent this from happening again.

Read the full incident report →

Major September 23, 2025

We are experiencing intermittent network issues that affect all parts of our application. Our datacenter team is looking into it. Thank you for your patience!

Detected by Pingoru
Sep 23, 2025, 06:54 PM UTC
Resolved
Sep 24, 2025, 12:28 PM UTC
Duration
17h 34m
Affected: Beanstalk
Timeline · 2 updates
  1. investigating Sep 23, 2025, 06:54 PM UTC

    We are experiencing intermittent network issues that affect all parts of our application. Our datacenter team is looking into it. Thank you for your patience!

  2. resolved Sep 24, 2025, 12:28 PM UTC

    Our datacenter team has notified us that the networking issues has been resolved at this time.

Read the full incident report →

Major August 10, 2025

We are once again experiencing issues with our data center network. Beanstalk is unavailable at the moment.

Detected by Pingoru
Aug 10, 2025, 02:10 AM UTC
Resolved
Aug 10, 2025, 02:39 AM UTC
Duration
29m
Affected: Beanstalk
Timeline · 2 updates
  1. investigating Aug 10, 2025, 02:10 AM UTC

    We are once again experiencing issues with our data center network. Beanstalk is unavailable at the moment.

  2. resolved Aug 10, 2025, 02:39 AM UTC

    We believe the issue has been resolved for good this time around.

Read the full incident report →

Minor May 8, 2025

Our services are back up and running. It looks like the issue stemmed from our datacenter,…

Detected by Pingoru
May 08, 2025, 05:09 AM UTC
Resolved
May 08, 2025, 05:09 AM UTC
Duration
—
Timeline · 1 update
  1. resolved May 08, 2025, 05:09 AM UTC

    Our services are back up and running. It looks like the issue stemmed from our datacenter, potentially there was an issue with their network equipment. We’re waiting to hear back from them. Thank you for your patience!

Read the full incident report →