Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Cloudgov

    Last checked 28 Eki 09:35 UTC

    Cloudgov status

    Secure compliant cloud platform for rapid deployment of modern web applications.

    Experiencing an issue?

    Cloudgov logo

    Cloudgov çöktü mü?

    Maintenance

    Having issues with Cloudgov?

    Share your experience to help others stay informed.

    Current statusHealth graphOutage reportsOutage mapSocial signalsStatus historyComponentsIncident historyMaintenanceCommunityReviewsAboutFAQsMonitor serviceSimilar servicesComparison

    Latest activity

    Last 24 hours

    1. Official status checked

      Cloudgov has active maintenance

      Official provider status
      28 Eki 09:35 UTC

    Cloudgov outage reports

    0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.

    Yakın zamanda kesinti bildirimi yok

    Son 24 saat içinde topluluk tarafından bu hizmet için kesinti bildirimi gönderilmedi.

    Cloudgov durumu değiştiğinde bildirim alın

    E-posta, push ve webhook bildirimleri.

    İzlemeyi başlat

    Cloudgov kesinti haritası

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Haritanın tamamını görün

    Cloudgov kesinti haritası

    Loading report locations…

    Cloudgov status history

    Official status observations, not measured service uptime.

    Cloudgov components

    Component nameStatus
    Cloudgov Cloud.gov Logs — Application logs - Intake and storage statusUp
    Cloudgov Cloud.gov customer applications — Applications statusUp
    Cloudgov Cloud.gov customer access — Dashboard statusUp
    Cloudgov Services Cloud.gov Pages depends on — GitHub statusUp
    Cloudgov Cloud.gov Workshop — User interface statusUp
    Cloudgov Cloud.gov Pages — Web Application statusUp
    Cloudgov Cloud.gov Pages — Builds statusUp
    Cloudgov Services Cloud.gov Pages depends on — GitHub Webhooks statusUp
    Cloudgov Cloud.gov customer access — Logs front end statusUp
    Cloudgov Cloud.gov Workshop — Runner service statusUp

    Cloudgov incident history

    Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.

    View more history
    Incident nameDurationStartedUTCAcknowledgedSeverity
    Official status·Resolved0m5 Ağu 202614:50 UTCYesUnknown
    Official status·Resolved19h 34m11 Haz 202617:52 UTCYesUnknown
    Official status·Resolved1h 19m28 May 202612:47 UTCYesUnknown
    Official status·Resolved17h 26m8 Nis 202617:34 UTCYesUnknown
    Official status·Resolved0m17 Mar 202613:30 UTCYesUnknown
    Official status·Resolved45h 7m29 Ara 202515:26 UTCYesMinor
    Official status·Resolved0m15 Ara 202520:30 UTCYesUnknown
    Official status·Resolved302h 45m4 Ara 202516:00 UTCYesUnknown

    Uptimus'ta Cloudgov izleme hakkında

    Uptimus, Cloudgov hizmetini resmi durum kaynağından izler ve olayları, bakımları ve bileşenleri ortak bir duruma dönüştürür.

    Bu sayfa şu anda 43 bileşen, 51 olay, 57 bakım ve 9 günlük bilinen geçmiş içerir.

    Uptimus bağımsızdır ve Cloudgov ile bağlantılı değildir. Sağlıklı durum her kullanıcı, cihaz veya bölgenin etkilenmediğini garanti etmez.

    Uptimus Cloudgov hizmetini nasıl izler

    Cloudgov veya izlenen bir bileşen büyük ya da kritik kesinti bildirdiğinde bildirim alın. Uyarılar e-posta, push ve yapılandırılmış entegrasyonlar dahil etkin workspace kanallarına yönlendirilebilir. Mevcut geçmiş 51 dizinlenmiş olay içerir ve uyarılara güncel durumun ötesinde bağlam sağlar. Yakın zamanda dizinlenen bir olay “Partial outage for the SES Service Broker” idi.

    Düşük performans, kısmi etki ve tam kesinti olmayan küçük olaylar hakkında bildirim alın. Uptimus şu anda 43 Cloudgov bileşenini izliyor: Application logs - Intake and storage, Applications, Dashboard, GitHub. Uyarılar e-posta, push ve yapılandırılmış entegrasyonlar dahil etkin workspace kanallarına yönlendirilebilir.

    Bakım bildirimleri
    Cloudgov planlı, zamanlanmış veya etkin bakım yayınladığında bildirim alın. Uptimus mevcut Cloudgov geçmişinden 57 bakım aralığını dizinledi. Uyarılar e-posta, push ve yapılandırılmış entegrasyonlar dahil etkin workspace kanallarına yönlendirilebilir.

    Scheduled maintenance

    Planned work published by the official provider.

    1. ✓

      General retirement notice - CAPI V2 API

      Maintenance

      Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027. As we announced on January 7, 2025 ( https://docs.cloud.gov/news/2025/01/02/v2api-deprecation ), we are retiring version 2 of Cloud Foundry API (CAPI V2), and will soon use only version 3 of the API (CAPI V3). Over the last 20 months, our Cloud.gov community has done a terrific job in adopting CAPI V3, and CAPI V2 only accounts for 0.15% of all our CAPI traffic. On February 2, 2027, CAPI V2 will be permanently disabled on Cloud.gov. Tools that depend on V2, including CF CLI v6 and v7, will stop working and will not work again. Ahead of that date, Cloud.gov will run four scheduled brownouts: temporary, planned windows during which we disable V2 endpoints so you can discover if any of your tools depend on them – while there is still time to fix them. Service returns to normal at the end of each window. As a customer, you need to: Check that you are using V3 compatible tooling (see below) Test your deployment and other automated processes during the V2 brownouts to see if anything breaks -- indicating a possible V2 dependency. Brownout schedule Window #1 - Wed Oct 14, 2026 - 8:00 AM EDT thru Wed Oct 14, 2026, 2:00 PM EDT - length 6 hours Window #2 - Wed Oct 28, 2026 - 8:00 AM EDT thru Wed Oct 28, 2026, 2:00 PM EDT - length 6 hours Window #3 - Tue Nov 17, 2026 - 8:00 AM EST thru Wed Nov 18, 2026, 2:00 PM EST - length 30 hours Window #4 - Tue Dec 1, 2026 - 8:00 AM EST thru Thu Dec 3, 2026, 2:00 PM EST - length 54 hours Final retirement: Tuesday, February 2, 2027, 8:00 AM EST. This is not a maintenance window. V2 will not be re-enabled afterward. For more details and next steps, please see: https://docs.cloud.gov/news/2026/10/02/capi-v2-brownouts/ If you have any questions please contact support at [email protected]

      Started 2 Şub 2027 13:00 UTC · Ongoing

    2. ✓

      Cloud Foundry API (CAPI) V2 - Brownout Window #4

      Maintenance

      Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027. As we announced on January 7, 2025 ( https://docs.cloud.gov/news/2025/01/02/v2api-deprecation ), we are retiring version 2 of Cloud Foundry API (CAPI V2), and will soon use only version 3 of the API (CAPI V3). Over the last 20 months, our Cloud.gov community has done a terrific job in adopting CAPI V3, and CAPI V2 only accounts for 0.15% of all our CAPI traffic. On February 2, 2027, CAPI V2 will be permanently disabled on Cloud.gov. Tools that depend on V2, including CF CLI v6 and v7, will stop working and will not work again. Ahead of that date, Cloud.gov will run four scheduled brownouts: temporary, planned windows during which we disable V2 endpoints so you can discover if any of your tools depend on them – while there is still time to fix them. Service returns to normal at the end of each window. As a customer, you need to: Check that you are using V3 compatible tooling (see below) Test your deployment and other automated processes during the V2 brownouts to see if anything breaks -- indicating a possible V2 dependency. Brownout schedule Window #1 - Wed Oct 14, 2026 - 8:00 AM EDT thru Wed Oct 14, 2026, 2:00 PM EDT - length 6 hours Window #2 - Wed Oct 28, 2026 - 8:00 AM EDT thru Wed Oct 28, 2026, 2:00 PM EDT - length 6 hours Window #3 - Tue Nov 17, 2026 - 8:00 AM EST thru Wed Nov 18, 2026, 2:00 PM EST - length 30 hours Window #4 - Tue Dec 1, 2026 - 8:00 AM EST thru Thu Dec 3, 2026, 2:00 PM EST - length 54 hours Final retirement: Tuesday, February 2, 2027, 8:00 AM EST. This is not a maintenance window. V2 will not be re-enabled afterward. For more details and next steps, please see: https://docs.cloud.gov/news/2026/10/02/capi-v2-brownouts/ If you have any questions please contact support at [email protected]

      Started 1 Ara 2026 13:00 UTC · Ongoing

    3. ✓

      Cloud Foundry API (CAPI) V2 - Brownout Window #3

      Maintenance

      Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027. As we announced on January 7, 2025 ( https://docs.cloud.gov/news/2025/01/02/v2api-deprecation ), we are retiring version 2 of Cloud Foundry API (CAPI V2), and will soon use only version 3 of the API (CAPI V3). Over the last 20 months, our Cloud.gov community has done a terrific job in adopting CAPI V3, and CAPI V2 only accounts for 0.15% of all our CAPI traffic. On February 2, 2027, CAPI V2 will be permanently disabled on Cloud.gov. Tools that depend on V2, including CF CLI v6 and v7, will stop working and will not work again. Ahead of that date, Cloud.gov will run four scheduled brownouts: temporary, planned windows during which we disable V2 endpoints so you can discover if any of your tools depend on them – while there is still time to fix them. Service returns to normal at the end of each window. As a customer, you need to: Check that you are using V3 compatible tooling (see below) Test your deployment and other automated processes during the V2 brownouts to see if anything breaks -- indicating a possible V2 dependency. Brownout schedule Window #1 - Wed Oct 14, 2026 - 8:00 AM EDT thru Wed Oct 14, 2026, 2:00 PM EDT - length 6 hours Window #2 - Wed Oct 28, 2026 - 8:00 AM EDT thru Wed Oct 28, 2026, 2:00 PM EDT - length 6 hours Window #3 - Tue Nov 17, 2026 - 8:00 AM EST thru Wed Nov 18, 2026, 2:00 PM EST - length 30 hours Window #4 - Tue Dec 1, 2026 - 8:00 AM EST thru Thu Dec 3, 2026, 2:00 PM EST - length 54 hours Final retirement: Tuesday, February 2, 2027, 8:00 AM EST. This is not a maintenance window. V2 will not be re-enabled afterward. For more details and next steps, please see: https://docs.cloud.gov/news/2026/10/02/capi-v2-brownouts/ If you have any questions please contact support at [email protected]

      Started 17 Kas 2026 13:00 UTC · Ongoing

    4. ✓

      Cloud Foundry API (CAPI) V2 - Brownout Window #2

      Maintenance

      Cloud.gov is retiring the Cloud Foundry API (CAPI) V2 on Tuesday, February 2, 2027. As we announced on January 7, 2025 ( https://docs.cloud.gov/news/2025/01/02/v2api-deprecation ), we are retiring version 2 of Cloud Foundry API (CAPI V2), and will soon use only version 3 of the API (CAPI V3). Over the last 20 months, our Cloud.gov community has done a terrific job in adopting CAPI V3, and CAPI V2 only accounts for 0.15% of all our CAPI traffic. On February 2, 2027, CAPI V2 will be permanently disabled on Cloud.gov. Tools that depend on V2, including CF CLI v6 and v7, will stop working and will not work again. Ahead of that date, Cloud.gov will run four scheduled brownouts: temporary, planned windows during which we disable V2 endpoints so you can discover if any of your tools depend on them – while there is still time to fix them. Service returns to normal at the end of each window. As a customer, you need to: Check that you are using V3 compatible tooling (see below) Test your deployment and other automated processes during the V2 brownouts to see if anything breaks -- indicating a possible V2 dependency. Brownout schedule Window #1 - Wed Oct 14, 2026 - 8:00 AM EDT thru Wed Oct 14, 2026, 2:00 PM EDT - length 6 hours Window #2 - Wed Oct 28, 2026 - 8:00 AM EDT thru Wed Oct 28, 2026, 2:00 PM EDT - length 6 hours Window #3 - Tue Nov 17, 2026 - 8:00 AM EST thru Wed Nov 18, 2026, 2:00 PM EST - length 30 hours Window #4 - Tue Dec 1, 2026 - 8:00 AM EST thru Thu Dec 3, 2026, 2:00 PM EST - length 54 hours Final retirement: Tuesday, February 2, 2027, 8:00 AM EST. This is not a maintenance window. V2 will not be re-enabled afterward. For more details and next steps, please see: https://docs.cloud.gov/news/2026/10/02/capi-v2-brownouts/ If you have any questions please contact support at [email protected]

      Started 28 Eki 2026 12:00 UTC · Ongoing

    5. ✓

      Cloud.gov IDP Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 21 Eki 2026 12:30 UTC · Resolved 21 Eki 2026 13:31 UTC

    6. ✓

      Cloud Foundry API (CAPI) V2 - Brownout Window #1

      Resolved

      The scheduled maintenance has been completed.

      Started 14 Eki 2026 12:00 UTC · Resolved 14 Eki 2026 18:00 UTC

    7. ✓

      Scheduled Improvements to Cloud.gov Logs Storage and Retrieval

      Resolved

      The scheduled maintenance has been completed.

      Started 13 Eki 2026 15:00 UTC · Resolved 13 Eki 2026 18:00 UTC

    8. ✓

      Cloud.gov IDP Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 29 Eki 2025 12:30 UTC · Resolved 29 Eki 2025 13:30 UTC

    Kurtarma bildirimleri
    Cloudgov veya etkilenen bir bileşen tekrar sağlıklı çalışmaya döndüğünde haberdar olun. Sayfa 9 günlük bilinen geçmiş içerir; çözülen olaylar daha sonra incelenebilir. Uyarılar e-posta, push ve yapılandırılmış entegrasyonlar dahil etkin workspace kanallarına yönlendirilebilir.
    Durum mesajları
    Uptimus, Cloudgov tarafından yayınlanan olay başlığını normalleştirilmiş durumla birlikte saklar. Mevcut geçmiş 51 dizinlenmiş olay içerir ve uyarılara güncel durumun ötesinde bağlam sağlar. Yakın zamanda dizinlenen bir olay “Partial outage for the SES Service Broker” idi.
    Durum ayrıntıları
    Olay ve bakım güncellemeleri araştırma, azaltma ve kurtarma sürecini izlemek için korunur. Uptimus tarafından korunan yakın tarihli resmi güncelleme: “# SES service broker outage on August 5, 2026 ## Summary From approximately 9:13 AM ET to 9:45 AM ET on Wednesday August 5, 2026,[ ](http://cloud.gov)the [SES service broker](https://docs.cloud.gov/platform/services/aws-ses/) was unavailable. During this ti…”.
    Bileşen durumu filtreleme
    Tüm bileşenleri veya kullandığınız Cloudgov ürünlerini seçin. Resmi bildirimler bu seçime uyar. Uptimus şu anda 43 Cloudgov bileşenini izliyor: Application logs - Intake and storage, Applications, Dashboard, GitHub. Filtreleme teslim edilen resmi uyarıları değiştirir, olayları herkese açık geçmişten kaldırmaz.

    Sıkça Sorulan Sorular

    Cloudgov durumu değiştiğinde bildirim alın

    İzlemeyi başlat
    Similar services
    Comparison

    Cloudgov için Uptimus ve Downdetector

    Downdetector herkese açık sayfaları kullanıcı raporlarına odaklanır. Uptimus bu etkinliği sağlayıcının yayımladığı resmi olaylar, bakımlar ve bileşen durumlarıyla birleştirir.

    Cloudgov için Uptimus ve Downdetector
    Karşılaştırma ölçütleriUptimusDowndetector
    Cloudgov için topluluk kesinti raporlarıDahilDahil
    Tekil raporları geniş kesintilerden ayıran uyarlanabilir temelDahilDahil
    24 saatlik rapor etkinliği ve bölgesel kesinti görünümüDahilDahil
    Web siteleri, durum sağlayıcıları, Steam oyunları ve Android uygulama ve oyunları için tek alanDahilAyrı ürün
    Aynı çalışma alanından e-posta, push ve webhook uyarılarıDahilAyrı ürün
    Cloudgov için resmi olay güncellemeleri ve durum zaman çizelgesiDahilRapor odaklı
    Bileşen sağlığı ve bakım pencereleri ayrı tutulurDahilHerkese açık sayfalarda sınırlı
    DahilRapor odaklı · Herkese açık sayfalarda sınırlıAyrı ürün

    The official status page for Cloudgov reports normal operation. 0 reports were recorded for Cloudgov in the last 24 hours. Last official check: 28 Eki 09:35 UTC.

    İzlenecek daha fazla hizmet

    Diğer popüler hizmetleri ve mevcut durumlarını keşfedin

    Tüm hizmetlere göz atın
    TDS TelecomElite DangerousBringgAppfiguresDwollaSumsubMailerliteAzureVolusion

    Topluluk Tartışması

    Cloudgov hakkındaki düşüncelerinizi paylaşın

    A
    Henüz yorum yok

    İlk yorum yapan siz olun!

    Bu hizmeti değerlendirin

    Geçen ay Cloudgov'ı nasıl değerlendirirsiniz?

    Henüz değerlendirme yok

    (Ayda bir inceleme sınırı)