Is Cloud.gov Builds down?
Current Cloud.gov Builds status is UP

We checked the official Cloud.gov Builds Status Page 4 min. 40 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Cloud.gov Builds Outages and Issues

Follow the recent outages and downtime for Cloud.gov Builds in the table below.

Start Time

Type

Length

Message

Details

February 27, 2024 18:01 UTC

WARN

ongoing

Out of memory issues in running and staging apps

See more
Start Time

February 27, 2024 18:01 UTC

Type WARN
Affected Components

cloud.gov Pages - Builds

Message

Out of memory issues in running and staging apps

Details

Update - Since the changes that were deployed last week to increase the number of VMs available to host customer applications and to double the amount of memory available for staging operations, customers have reported a reduction in the frequency of "out of memory" issues, but are still experiencing them.The cloud.gov team has continued to investigate the cause of these issues. After consulting with the CloudFoundry community, we believe that these issues may be caused by faulty memory allocation in the Linux kernel which is built-in to the stemcells for CloudFoundry VMs. This GitHub issue is being used to track investigation and resolution of the stemcell memory issues: https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/318One of the recommendations from the community to resolve the "out of memory" issues was to roll back to stemcell version 1.340, however every stemcell release includes fixes for a number of CVEs (https://github.com/cloudfoundry/bosh-linux-stemcell-builder/releases), so rolling back would expose the platform and our customers to CVEs that are patched in the current stemcell version. At this time, cloud.gov does not plan to roll back our stemcell version given the potential security risk.Another recommendation from the community was to increase the amount of memory available for staging, which we did last week when we increased the value from 1024 MB to 2048 MB, but customers continue to experience issues.At this point, the plan for mitigation is to pursue ad hoc memory increases for applications that are still experiencing issues until a fix for the kernel/stemcell issue is released from upstream and can be deployed to our platform.If your applications are still experiencing issues, please contact us at support@cloud.gov so we can work to resolve them for you.Thank you for being a cloud.gov customer! Feb 20, 2024 - 12:04 EST

February 20, 2024 19:27 UTC

WARN

7 days

cloud.gov Pages builds caching error for Jekyll sites

See more
Start Time

February 20, 2024 19:27 UTC

Type WARN
Affected Components

cloud.gov Pages - Builds

Message

cloud.gov Pages builds caching error for Jekyll sites

Details

Monitoring - cloud.gov Pages customers using Jekyll may be experiencing failing builds due to a caching error on our application. We have identified the fix and are resetting the cache for affected sites. Please contact us if you are experiencing an unexpected Jekyll build error Feb 20, 2024 - 14:25 EST

April 20, 2023 20:41 UTC

WARN

about 1 hour

Intermittent Webhook Failures

See more
Start Time

April 20, 2023 20:41 UTC

Type WARN
Affected Components

cloud.gov Pages - Builds

Message

Intermittent Webhook Failures

Details

Investigating - Some sites on the platform are experiencing problems with builds due to missing webhook details. We are investigating the problem and adding additional admin features to identify and remediate it with the affected sites. Contact Pages support if you are experiencing these problems. Apr 20, 2023 - 16:39 EDT

January 30, 2023 14:31 UTC

DOWN

about 2 hours

Pages: failing builds

See more
Start Time

January 30, 2023 14:31 UTC

Type DOWN
Affected Components

cloud.gov Pages - Builds

Message

Pages: failing builds

Details

Investigating - All builds are currently failing. The error message will show "There was a problem fetching the commit hash for this build". GitHub is showing some failures at the moment but they appear to be unrelated. We are continuing to investigate this issue. Jan 30, 2023 - 09:30 EST

No outages or status changes in the last 24 hours

Cloud.gov Builds status, last 24 hours:

5:00 AM
11:00 AM
5:00 PM
11:00 PM
5:00 AM
5:00 AM
5:00 PM
5:00 AM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

  • Maintenance: 0 minutes

Cloud.gov Builds Outage and Status History

We've been monitoring Cloud.gov Builds outages since March 14, 2021.
Here's the history of service outages we've observed from the Cloud.gov Builds Status Page:

May 2024

April 2024

March 2024

  • Up

  • Warn

  • Down

  • Maintenance

Instant enriched data from
3,590 status pages

About Our Cloud.gov Builds Status Page Integration

Cloud.gov Builds is a Finance solution that StatusGator has been monitoring since March 2021. Over the past about 3 years, we have collected data on on more than 158 outages that affected Cloud.gov Builds users. When Cloud.gov Builds publishes downtime on their status page, they do so across 31 components and 5 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.

Many StatusGator users monitor Cloud.gov Builds to get notified when it's down, is under maintenance, or has an outage. You can get alerts by signing up for a free StatusGator account.

If Cloud.gov Builds is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Cloud.gov Builds is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Cloud.gov Builds posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Cloud.gov Builds enters a pre-planned maintenance window, keeping you up to date.

Since Cloud.gov Builds publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.

When Cloud.gov Builds posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Cloud.gov Builds has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Cloud.gov Builds has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Cloud.gov Builds Down?

Are you experiencing issues with Cloud.gov Builds? Sign up to receive notifications when Cloud.gov Builds publishes outages.

Cloud.gov Builds Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,590 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Cloud.gov Builds?

Sign up for StatusGator and see all historical information about Cloud.gov Builds outages and performance issues. Get free, instant notifications when Cloud.gov Builds goes down.