Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Cloudgov

    Last checked 10月28日 4:20 UTC

    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日 4: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.

    最近の障害報告はありません

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

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

    5. ✓

      Cloud.gov IDP Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    6. ✓

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

      Resolved

      The scheduled maintenance has been completed.

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

    7. ✓

      Scheduled Improvements to Cloud.gov Logs Storage and Retrieval

      Resolved

      The scheduled maintenance has been completed.

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

    8. ✓

      Cloud.gov IDP Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    ステータスメッセージ
    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時間の報告推移と地域別障害マップ利用可能利用可能
    Webサイト、公式ステータス、Steam、Androidアプリとゲームを1つのワークスペースで管理利用可能別製品
    同じワークスペースからメール、プッシュ、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日 4:20 UTC.

    コミュニティディスカッション

    Cloudgovについてのあなたの考えを共有してください

    A
    まだコメントはありません

    最初のコメントを残しましょう！

    監視するサービス

    他の人気サービスとその現在のステータスを発見する

    すべてのサービスを閲覧
    TDS TelecomBringgAppfiguresDwollaSumsubMailerliteAzureServicebell

    このサービスを評価する

    過去1ヶ月間のCloudgovをどのように評価しますか？

    まだレビューはありません

    (月に1回のレビュー制限)