Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Cloudgov

    Last checked 28. Okt., 05:08 UTC

    Cloudgov status

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

    Experiencing an issue?

    Cloudgov logo

    Ist Cloudgov down?

    Status unavailable

    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. Status verification pending

      The latest official observation is not fresh enough to confirm current service health.

      Official provider status
      28. Okt., 05:08 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.

    Keine aktuellen Störungsmeldungen

    In den letzten 24 Stunden wurden für diesen Dienst keine Störungsmeldungen aus der Community eingereicht.

    Benachrichtigung erhalten, wenn sich der Status von Cloudgov ändert

    Benachrichtigungen per E-Mail, Push und Webhook.

    Überwachung starten

    Ausfallkarte für Cloudgov

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Vollständige Karte anzeigen

    Ausfallkarte für Cloudgov

    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. Aug. 202614:50 UTCYesUnknown
    Official status·Resolved19h 34m11. Juni 202617:52 UTCYesUnknown
    Official status·Resolved1h 19m28. Mai 202612:47 UTCYesUnknown
    Official status·Resolved17h 26m8. Apr. 202617:34 UTCYesUnknown
    Official status·Resolved0m17. März 202613:30 UTCYesUnknown
    Official status·Resolved45h 7m29. Dez. 202515:26 UTCYesMinor
    Official status·Resolved0m15. Dez. 202520:30 UTCYesUnknown
    Official status·Resolved302h 45m4. Dez. 202516:00 UTCYesUnknown

    Über die Überwachung von Cloudgov auf Uptimus

    Uptimus überwacht Cloudgov über die offizielle Statusquelle und normalisiert Vorfälle, Wartungen und Komponenten in einen einheitlichen Status.

    Diese Seite enthält derzeit 43 überwachte Komponenten, 51 Vorfälle, 57 Wartungen und 9 Tage bekannten Verlauf.

    Uptimus ist ein unabhängiger Dienst und nicht mit Cloudgov verbunden. Ein gesunder Status garantiert nicht, dass alle Nutzer, Geräte oder Regionen unbeeinträchtigt sind.

    Wie Uptimus Cloudgov überwacht

    Erhalte eine Meldung, wenn Cloudgov oder eine überwachte Komponente einen schweren Ausfall oder eine kritische Störung meldet. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen. Der verfügbare Verlauf enthält 51 erfasste Vorfälle und gibt Meldungen Kontext über den aktuellen Status hinaus. Ein kürzlich erfasster Vorfall war „Partial outage for the SES Service Broker“.

    Erhalte Meldungen zu Leistungseinbußen, teilweisen Auswirkungen und kleineren Vorfällen ohne vollständigen Ausfall. Uptimus überwacht derzeit 43 Cloudgov-Komponenten: Application logs - Intake and storage, Applications, Dashboard, GitHub. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen.

    Wartungsbenachrichtigungen

    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. Feb. 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. Dez. 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. Nov. 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. Okt. 2026, 12:00 UTC · Ongoing

    5. ✓

      Cloud.gov IDP Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 21. Okt. 2026, 12:30 UTC · Resolved 21. Okt. 2026, 13:31 UTC

    6. ✓

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

      Resolved

      The scheduled maintenance has been completed.

      Started 14. Okt. 2026, 12:00 UTC · Resolved 14. Okt. 2026, 18:00 UTC

    7. ✓

      Scheduled Improvements to Cloud.gov Logs Storage and Retrieval

      Resolved

      The scheduled maintenance has been completed.

      Started 13. Okt. 2026, 15:00 UTC · Resolved 13. Okt. 2026, 18:00 UTC

    8. ✓

      Cloud.gov IDP Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 29. Okt. 2025, 12:30 UTC · Resolved 29. Okt. 2025, 13:30 UTC

    Erhalte eine Meldung, wenn Cloudgov geplante, terminierte oder aktive Wartungen veröffentlicht. Uptimus hat 57 Wartungsfenster aus dem verfügbaren Cloudgov-Verlauf erfasst. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen.
    Wiederherstellungsbenachrichtigungen
    Erfahre, wenn Cloudgov oder eine betroffene Komponente nach einer Störung wieder gesund ist. Die Seite enthält 9 Tage bekannten Verlauf; behobene Ereignisse bleiben zur Prüfung verfügbar. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen.
    Statusmeldungen
    Uptimus speichert die von Cloudgov veröffentlichte Überschrift und zeigt sie mit dem normalisierten Status an. Der verfügbare Verlauf enthält 51 erfasste Vorfälle und gibt Meldungen Kontext über den aktuellen Status hinaus. Ein kürzlich erfasster Vorfall war „Partial outage for the SES Service Broker“.
    Statusdetails
    Aktualisierungen zu Vorfällen und Wartungen bleiben erhalten, damit Untersuchung, Behebung und Wiederherstellung nachvollziehbar sind. Eine von Uptimus gespeicherte offizielle Aktualisierung lautet: „# 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…“.
    Komponentenfilter
    Wähle alle Komponenten oder nur die genutzten Cloudgov-Produkte. Offizielle Meldungen berücksichtigen diese Auswahl. Uptimus überwacht derzeit 43 Cloudgov-Komponenten: Application logs - Intake and storage, Applications, Dashboard, GitHub. Der Filter ändert zugestellte offizielle Meldungen, entfernt aber keine Ereignisse aus dem öffentlichen Verlauf.

    Häufig gestellte Fragen

    Benachrichtigung erhalten, wenn sich der Status von Cloudgov ändert

    Überwachung starten
    Similar services
    Comparison

    Uptimus vs Downdetector für Cloudgov

    Öffentliche Downdetector-Seiten basieren vor allem auf Nutzermeldungen. Uptimus verbindet diese mit offiziellen Vorfällen, Wartungen und Komponentenstatus, sofern der Anbieter sie veröffentlicht.

    Uptimus vs Downdetector für Cloudgov
    VergleichskriterienUptimusDowndetector
    Community-Störungsmeldungen zu CloudgovEnthaltenEnthalten
    Adaptive Basislinie zur Trennung einzelner Meldungen von größeren StörungenEnthaltenEnthalten
    24-Stunden-Meldeaktivität und regionale StörungskarteEnthaltenEnthalten
    Ein Arbeitsbereich für Websites, Statusanbieter, Steam-Spiele und Android-Apps und -SpieleEnthaltenSeparates Produkt
    E-Mail-, Push- und Webhook-Alarme aus demselben ArbeitsbereichEnthaltenSeparates Produkt
    Offizielle Vorfallmeldungen und Statusverlauf für CloudgovEnthaltenMeldungsbasiert
    Komponentenstatus und Wartungsfenster getrennt dargestelltEnthaltenAuf öffentlichen Seiten begrenzt
    EnthaltenMeldungsbasiert · Auf öffentlichen Seiten begrenztSeparates Produkt

    The current official status of Cloudgov cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Cloudgov in the last 24 hours. Last official check: 28. Okt., 05:08 UTC.

    Weitere zu überwachende Dienste

    Entdecken Sie andere beliebte Dienste und ihren aktuellen Status

    Alle Dienste durchsuchen
    TDS TelecomTHE FINALSBringgAppfiguresDwollaSumsubMailerliteAzureVolusion

    Bewerten Sie diesen Dienst

    Wie würden Sie Cloudgov im letzten Monat bewerten?

    Noch keine Bewertungen

    (Limit: Eine Bewertung pro Monat)

    Community-Diskussion

    Teilen Sie Ihre Gedanken über Cloudgov

    A
    Noch keine Kommentare

    Seien Sie der Erste, der kommentiert!