When a Looker (Google Cloud core) instance creation fails, you can use this troubleshooting guide to resolve issues stemming from instance creation or network validation. The troubleshooting process is broken down into two decision trees based on symptoms:

- [Symptom: Instance creation failure](https://docs.cloud.google.com/looker/docs/best-practices/flows/looker-core-instance-creation-troubleshooting.md.txt#instance_creation_failure)
- [Symptom: Network validation failures](https://docs.cloud.google.com/looker/docs/best-practices/flows/looker-core-instance-creation-troubleshooting.md.txt#network_validation_failures)

## Symptom: Instance creation failure

If you're encountering a failure while trying to create a Looker (Google Cloud core) instance, use the following decision tree to begin troubleshooting. This tree helps route you to setup guides for first-time deployments, to Sales for discontinued editions or quota increases, to network configuration steps for a Shared VPC, or to specific bug mitigations for intermittent Filestore errors.
<iframe src="https:///frame/looker/docs/best-practices/flows/looker-core-instance-creation-troubleshooting_710e293b2ae7b9f5c16934d5545bdd4f64d6a54171e924de52f3aaae0887febd.frame" class="framebox inherit-locale " allow="clipboard-write https://" allowfullscreen is-upgraded></iframe>

**Troubleshooting steps:**

1. **First-time creation?** If yes, review the [setup guide](https://docs.cloud.google.com/looker/docs/looker-core-instance-create.md.txt#create_instance) to ensure that all steps were followed.
2. **Quota Issue?** If you suspect a quota issue, contact your Sales or Account Executive. If you have recently deleted a Looker (Google Cloud core) instance, or if a previous provisioning attempt failed, your project's quota may still be in use. It can take up to 24 hours for the quota to reset. If immediate provisioning is required, contact [Customer Care](https://docs.cloud.google.com/looker/docs/looker-core-support.md.txt) to request a manual, temporary quota bump to bypass the reset window.
3. **Trial/Monthly Standard?** If you're using an expired or discontinued edition, refer to current [Looker pricing](https://cloud.google.com/looker/pricing).
4. **None of the above?** Proceed to the [Network Validation Failures](https://docs.cloud.google.com/looker/docs/best-practices/flows/looker-core-instance-creation-troubleshooting.md.txt#network_validation_failures) tree.

## Symptom: Network validation failures

If you're encountering network validation failures, such as `RANGES_NOT_RESERVED` or `RANGES_EXHAUSTED`, use the following decision tree to troubleshoot. This tree helps identify specific range reservation errors and verify if a Shared VPC is in use. You may be guided to reserve IP ranges, expand existing allocations, or perform manual Looker service account setup steps for Shared VPC environments.
<iframe src="https:///frame/looker/docs/best-practices/flows/looker-core-instance-creation-troubleshooting_adbe4dead7adc318222fb22738271c13ea73ce7400802d4686604772a95caebb.frame" class="framebox inherit-locale " allow="clipboard-write https://" allowfullscreen is-upgraded></iframe>

**Troubleshooting steps:**

1. **RANGES_NOT_RESERVED?** Reserve the necessary IP ranges for your instance.
2. **RANGES_EXHAUSTED?** Expand the existing IP range allocation.
3. **Shared VPC?** If you're using a [Shared VPC](https://docs.cloud.google.com/looker/docs/looker-core-create-private-ip.md.txt#shared-vpc), ensure that the Looker service account is enabled and has the `compute.globalAddresses.get` permission.
4. **None of the above?** Contact [Support](https://docs.cloud.google.com/looker/docs/looker-core-support.md.txt) if you need further assistance.