Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Cloudgov

    Last checked 10月28日 UTC 04:20

    Cloudgov status

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

    Experiencing an issue?

    Cloudgov logo

    Cloudgov宕机了吗？

    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
      10月28日 UTC 04:20

    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.

    近期没有中断报告

    过去24小时内，社区没有提交此服务的中断报告。

    在 Cloudgov 状态发生变化时接收通知

    通过电子邮件、推送和 Webhook 通知。

    开始监控

    Cloudgov 中断地图

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    查看完整地图

    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·Resolved0m2026年8月5日UTC 14:50YesUnknown
    Official status·Resolved19h 34m2026年6月11日UTC 17:52YesUnknown
    Official status·Resolved1h 19m2026年5月28日UTC 12:47YesUnknown
    Official status·Resolved17h 26m2026年4月8日UTC 17:34YesUnknown
    Official status·Resolved0m2026年3月17日UTC 13:30YesUnknown
    Official status·Resolved45h 7m2025年12月29日UTC 15:26YesMinor
    Official status·Resolved0m2025年12月15日UTC 20:30YesUnknown
    Official status·Resolved302h 45m2025年12月4日UTC 16:00YesUnknown

    关于 Uptimus 对 Cloudgov 的监控

    Uptimus 通过官方状态源监控 Cloudgov，并将事件、维护和组件健康状况统一为一致的服务状态。

    此页面目前包含 43 个受监控组件、51 个事件、57 个维护窗口和 9 天已知历史。

    Uptimus 是独立监控服务，与 Cloudgov 无关联。健康状态并不保证每位用户、设备或地区都未受影响。

    Uptimus 如何监控 Cloudgov

    当 Cloudgov 或受监控组件报告重大或关键中断时接收通知。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。 可用历史包含 51 个事件，为提醒提供当前状态之外的背景。 最近收录的事件是“Partial outage for the SES Service Broker”。

    接收有关性能下降、部分影响和非完全中断的小型事件通知。 Uptimus 当前跟踪 Cloudgov 的 43 个组件: Application logs - Intake and storage, Applications, Dashboard, GitHub。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。

    维护通知
    当 Cloudgov 发布计划、预定或正在进行的维护时接收通知。 Uptimus 已从 Cloudgov 的可用历史中收录 57 个维护窗口。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。
    恢复通知
    当 Cloudgov 或受影响组件恢复正常运行时收到通知。 页面包含 9 天已知历史，已解决事件仍可供查看。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。
    状态消息

    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 2027年2月2日 UTC 13:00 · 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 2026年12月1日 UTC 13:00 · 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 2026年11月17日 UTC 13:00 · 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 2026年10月28日 UTC 12:00 · Ongoing

    5. ✓

      Cloud.gov IDP Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年10月21日 UTC 12:30 · Resolved 2026年10月21日 UTC 13:31

    6. ✓

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

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年10月14日 UTC 12:00 · Resolved 2026年10月14日 UTC 18:00

    7. ✓

      Scheduled Improvements to Cloud.gov Logs Storage and Retrieval

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年10月13日 UTC 15:00 · Resolved 2026年10月13日 UTC 18:00

    8. ✓

      Cloud.gov IDP Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2025年10月29日 UTC 12:30 · Resolved 2025年10月29日 UTC 13:30

    Uptimus 保存 Cloudgov 发布的事件标题，并与标准化状态一起显示。 可用历史包含 51 个事件，为提醒提供当前状态之外的背景。 最近收录的事件是“Partial outage for the SES Service Broker”。
    状态详情
    事件和维护更新会被保留，以便跟踪调查、缓解和恢复过程。 Uptimus 保存的近期官方更新为：“# 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…”。
    组件状态筛选
    选择所有组件或仅选择使用的 Cloudgov 产品。官方通知会遵循该选择。 Uptimus 当前跟踪 Cloudgov 的 43 个组件: Application logs - Intake and storage, Applications, Dashboard, GitHub。 筛选只改变官方提醒的发送范围，不会从公开历史中移除事件。

    常见问题

    在 Cloudgov 状态发生变化时接收通知

    开始监控
    Similar services
    Comparison

    Cloudgov：Uptimus 与 Downdetector 对比

    Downdetector 公共页面主要基于用户报告。Uptimus 还会在来源提供时结合官方事件、维护窗口和组件状态。

    Cloudgov：Uptimus 与 Downdetector 对比
    比较标准UptimusDowndetector
    Cloudgov 的社区中断报告已包含已包含
    区分个别报告和大范围中断的自适应基线已包含已包含
    24 小时报表活动和区域中断视图已包含已包含
    在一个工作区管理网站、状态提供商、Steam 游戏及 Android 应用和游戏已包含独立产品
    从同一工作区发送邮件、推送和 Webhook 告警已包含独立产品
    Cloudgov 的官方事件更新和状态时间线已包含以用户报告为主
    分别展示组件健康与维护窗口已包含公共页面功能有限
    已包含以用户报告为主 · 公共页面功能有限独立产品

    The official status page for Cloudgov reports normal operation. 0 reports were recorded for Cloudgov in the last 24 hours. Last official check: 10月28日 UTC 04:20.

    更多监控服务

    发现其他流行服务及其当前状态

    浏览所有服务
    TDS TelecomBringgAppfiguresDwollaSumsubMailerliteAzureServicebell

    评价此服务

    您如何评价过去一个月的 Cloudgov？

    暂无评价

    (每月限制一条评价)

    社区讨论

    分享您对 Cloudgov 的看法

    A
    还没有评论

    成为第一个评论的人！