Stay organized with collections
Save and categorize content based on your preferences.
When you propose a Virtual Private Cloud (VPC) spoke
connection to a hub, the spoke is not fully operational until the hub
administrator accepts the spoke. Similarly, when you propose updates to the
properties of an existing spoke, the updates aren't effective until the hub
administrator accepts the updates. This page describes
how you can check the status of a spoke after you have proposed a new spoke or
updates to an existing spoke.
Before you begin
Before you get started, review the following sections.
Create or select a project
To make it easier to configure Network Connectivity Center, start by identifying a valid
project.
Sign in to your Google Cloud account. If you're new to
Google Cloud,
create an account to evaluate how our products perform in
real-world scenarios. New customers also get $300 in free credits to
run, test, and deploy workloads.
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
To perform this task, you must have been granted the following permissions
or the following IAM roles.
Permissions
networkconnectivity.spokes.get
Roles (one of the following)
roles/networkconnectivity.hubAdmin
roles/networkconnectivity.spokeAdmin
roles/networkconnectivity.hubViewer
Spoke states
The following table describes the different states that a spoke might be in
after it is proposed to the hub administrator.
Spoke state
State reason
Description
ACTIVE
The reasons field is empty.
For new spoke proposals, this means that the hub administrator has
accepted the spoke and the spoke is fully operational.
For updates to existing spokes, this means that the hub administrator
has accepted the updates and the updates have been applied.
ACTIVE
UPDATE_PENDING_REVIEW
This means that the spoke is operational, but a proposed update
to the spoke's properties hasn't yet been accepted or rejected. If a
spoke update is rejected by the hub administrator, but the
rejection fails, the spoke might still show an
UPDATE_PENDING_REVIEW state.
ACTIVE
UPDATE_FAILED
This means that the spoke is operational, and a proposed update
to the spoke's properties was accepted, but the update failed.
ACTIVE
UPDATE_REJECTED
This means that the spoke is operational, but a proposed update
to the spoke's properties was rejected.
INACTIVE
PENDING_REVIEW
This means that the spoke is not operational, and that the hub
administrator hasn't yet accepted or rejected the spoke.
INACTIVE
REJECTED
This means that the spoke is not operational because the hub
administrator has rejected the spoke.
OBSOLETE
The reasons field is empty.
This means that the hub has been deleted. Once in this state, the
state never changes, and the spoke can only be deleted.
Get the status of a spoke proposal
To get the status of a spoke that you have proposed in a different project from
the hub, including updates to existing spokes, follow these steps.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Check the status of a VPC spoke\n\nWhen you [propose a Virtual Private Cloud (VPC) spoke](/network-connectivity/docs/network-connectivity-center/how-to/vpc-propose-a-spoke)\nconnection to a hub, the spoke is not fully operational until the hub\nadministrator accepts the spoke. Similarly, when you propose updates to the\nproperties of an existing spoke, the updates aren't effective until the hub\nadministrator accepts the updates. This page describes\nhow you can check the status of a spoke after you have proposed a new spoke or\nupdates to an existing spoke.\n\nBefore you begin\n----------------\n\nBefore you get started, review the following sections.\n\n### Create or select a project\n\nTo make it easier to configure Network Connectivity Center, start by identifying a valid\nproject.\n\n- Sign in to your Google Cloud account. If you're new to Google Cloud, [create an account](https://console.cloud.google.com/freetrial) to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n-\n [Install](/sdk/docs/install) the Google Cloud CLI.\n\n- If you're using an external identity provider (IdP), you must first\n [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n\n-\n To [initialize](/sdk/docs/initializing) the gcloud CLI, run the following command:\n\n ```bash\n gcloud init\n ```\n\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n-\n [Install](/sdk/docs/install) the Google Cloud CLI.\n\n- If you're using an external identity provider (IdP), you must first\n [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n\n-\n To [initialize](/sdk/docs/initializing) the gcloud CLI, run the following command:\n\n ```bash\n gcloud init\n ```\n\n1. If you are using the Google Cloud CLI, set your project\n ID by using the\n [`gcloud config set` command](/sdk/gcloud/reference/config/set).\n\n ```\n gcloud config set project PROJECT_ID\n ```\n\n Replace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with your unique project ID.\n\n The gcloud CLI instructions on this page assume that you have set your project ID.\n2. To confirm that you set the project ID correctly, use the\n [`gcloud config list` command](/sdk/gcloud/reference/config/list).\n\n ```\n gcloud config list --format='text(core.project)'\n ```\n\n### Enable the Network Connectivity API\n\nBefore you can perform *any* tasks using Network Connectivity Center, you must enable the\nNetwork Connectivity API. \n\n### Console\n\nTo enable the Network Connectivity API, do the following:\n\n1. In the Google Cloud console, go to the **Network Connectivity Center** page.\n\n [Go to Network Connectivity Center](https://console.cloud.google.com/hybrid/hubs/list)\n2. Click **Enable**.\n\nAlternatively, you can enable the API by\nusing the\n[Google Cloud console API Library](https://console.cloud.google.com/apis/library?project=_),\nas described in [Enabling APIs](/apis/docs/getting-started#enabling_apis).\n\n#### Permissions required for this task\n\nTo perform this task, you must have been granted the following permissions\n*or* the following IAM roles.\n\n**Permissions**\n\n- `networkconnectivity.spokes.get`\n\n**Roles** (one of the following)\n\n- `roles/networkconnectivity.hubAdmin`\n- `roles/networkconnectivity.spokeAdmin`\n- `roles/networkconnectivity.hubViewer`\n\nSpoke states\n------------\n\nThe following table describes the different states that a spoke might be in\nafter it is proposed to the hub administrator.\n\nGet the status of a spoke proposal\n----------------------------------\n\nTo get the status of a spoke that you have proposed in a different project from\nthe hub, including updates to existing spokes, follow these steps. \n\n### gcloud\n\nRun the\n[`gcloud network-connectivity spokes describe` command](/sdk/gcloud/reference/network-connectivity/spokes/describe). \n\n```\ngcloud network-connectivity spokes describe SPOKE_NAME \\\n --global\n```\n\nReplace \u003cvar translate=\"no\"\u003eSPOKE_NAME\u003c/var\u003e with the name of the spoke for which\nyou want to check the status, such as `my-spoke`.\n\n### API\n\nTo describe a spoke, use the\n[`networkconnectivity.spokes.get` method](/network-connectivity/docs/reference/networkconnectivity/rest/v1/projects.locations.spokes/get). \n\n```\n GET https://networkconnectivity.googleapis.com/v1/projects/PROJECT_ID/locations/global/spokes/SPOKE_NAME\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the project ID of the project that contains the spoke\n- \u003cvar translate=\"no\"\u003eSPOKE_NAME\u003c/var\u003e: the name of the spoke for which you want to get status\n\nWhat's next\n-----------\n\n- To create hubs and spokes, see [Work with hubs and spokes](/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes).\n- To view a list of partners whose solutions are integrated with Network Connectivity Center, see [Network Connectivity Center partners](/network-connectivity/docs/network-connectivity-center/partners).\n- To find solutions for common issues, see [Troubleshooting](/network-connectivity/docs/network-connectivity-center/support/troubleshooting).\n- To get details about API and `gcloud` commands, see [APIs and reference](/network-connectivity/docs/network-connectivity-center/apis)."]]
