Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Cloudgov

    Last checked 28. okt., 04.20 UTC

    Cloudgov status

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

    Experiencing an issue?

    Cloudgov logo

    Er Cloudgov nede?

    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. okt., 04.20 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.

    Ingen nylige nedbrudsrapporter

    Fællesskabet har ikke indsendt nedbrudsrapporter for denne tjeneste inden for de seneste 24 timer.

    Få besked, når status for Cloudgov ændres

    Notifikationer via e-mail, push og webhook.

    Start overvågning

    Driftskort for Cloudgov

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Se fuldt kort

    Driftskort for 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. jun. 202617.52 UTCYesUnknown
    Official status·Resolved1h 19m28. maj 202612.47 UTCYesUnknown
    Official status·Resolved17h 26m8. apr. 202617.34 UTCYesUnknown
    Official status·Resolved0m17. mar. 202613.30 UTCYesUnknown
    Official status·Resolved45h 7m29. dec. 202515.26 UTCYesMinor
    Official status·Resolved0m15. dec. 202520.30 UTCYesUnknown
    Official status·Resolved302h 45m4. dec. 202516.00 UTCYesUnknown

    Om overvågning af Cloudgov på Uptimus

    Uptimus overvåger Cloudgov via den officielle statuskilde og normaliserer hændelser, vedligeholdelse og komponenter til én ensartet status.

    Siden indeholder nu 43 komponenter, 51 hændelser, 57 vedligeholdelser og 9 dages kendt historik.

    Uptimus er en uafhængig tjeneste og er ikke tilknyttet Cloudgov. En sund status garanterer ikke, at alle brugere, enheder eller områder er upåvirkede.

    Sådan overvåger Uptimus Cloudgov

    Få besked, når Cloudgov eller en overvåget komponent melder et større eller kritisk nedbrud. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer. Den tilgængelige historik indeholder 51 hændelser og giver mere kontekst end den aktuelle status. En nylig registreret hændelse var “Partial outage for the SES Service Broker”.

    Få besked om nedsat ydelse, delvis påvirkning og mindre hændelser uden et fuldt nedbrud. Uptimus følger nu 43 Cloudgov-komponenter: Application logs - Intake and storage, Applications, Dashboard, GitHub. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.

    Vedligeholdelsesnotifikationer

    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. dec. 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

    Få besked, når Cloudgov offentliggør planlagt, tidsbestemt eller aktiv vedligeholdelse. Uptimus har registreret 57 vedligeholdelsesvinduer fra den tilgængelige Cloudgov-historik. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.
    Gendannelsesnotifikationer
    Få besked, når Cloudgov eller en påvirket komponent igen fungerer normalt. Siden indeholder 9 dages kendt historik; løste hændelser bevares til senere gennemgang. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.
    Statusmeddelelser
    Uptimus gemmer hændelsesoverskriften fra Cloudgov sammen med den normaliserede status. Den tilgængelige historik indeholder 51 hændelser og giver mere kontekst end den aktuelle status. En nylig registreret hændelse var “Partial outage for the SES Service Broker”.
    Statusdetaljer
    Opdateringer om hændelser og vedligeholdelse gemmes, så undersøgelse, afhjælpning og gendannelse kan følges. En nylig officiel opdatering gemt af Uptimus lyder: “# 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…”.
    Komponentfiltrering
    Vælg alle komponenter eller kun de Cloudgov-produkter, du bruger. Officielle alarmer følger valget. Uptimus følger nu 43 Cloudgov-komponenter: Application logs - Intake and storage, Applications, Dashboard, GitHub. Filtrering ændrer leverede officielle alarmer, men fjerner ikke hændelser fra den offentlige historik.

    Ofte Stillede Spørgsmål

    Få besked, når status for Cloudgov ændres

    Start overvågning
    Similar services
    Comparison

    Uptimus vs Downdetector for Cloudgov

    Downdetectors offentlige sider er primært baseret på brugerrapporter. Uptimus kombinerer dem med officielle hændelser, vedligeholdelse og komponentstatus, når udbyderen offentliggør dataene.

    Uptimus vs Downdetector for Cloudgov
    JämförelsekriterierUptimusDowndetector
    Rapporter fra fællesskabet om CloudgovInkluderetInkluderet
    Adaptiv basislinje, der skelner enkelte rapporter fra større nedbrudInkluderetInkluderet
    Rapportaktivitet over 24 timer og regionalt nedbrudskortInkluderetInkluderet
    Ét arbejdsområde til websites, statusudbydere, Steam-spil og Android-apps og -spilInkluderetSeparat produkt
    E-mail-, push- og webhookalarmer fra samme arbejdsområdeInkluderetSeparat produkt
    Officielle hændelsesopdateringer og statushistorik for CloudgovInkluderetRapportbaseret
    Komponentstatus og vedligeholdelse vises separatInkluderetBegrænset på offentlige sider
    InkluderetRapportbaseret · Begrænset på offentlige siderSeparat produkt

    The official status page for Cloudgov reports normal operation. 0 reports were recorded for Cloudgov in the last 24 hours. Last official check: 28. okt., 04.20 UTC.

    Flere tjenester at overvåge

    Opdag andre populære tjenester og deres nuværende status

    Gennemse alle tjenester
    TDS TelecomBringgAppfiguresDwollaSumsubMailerliteAzureServicebell

    Vurder denne tjeneste

    Hvordan vil du vurdere Cloudgov over den sidste måned?

    Ingen anmeldelser endnu

    (Én anmeldelse pr. måned begrænsning)

    Fællesskabsdiskussion

    Del dine tanker om Cloudgov

    A
    Ingen kommentarer endnu

    Vær den første til at kommentere!