For the past week or so, me and the rest of my team have been having issues fetching provider version from terraform
goldsky-infra-prod Initializing the backend...
goldsky-infra-prod
Successfully configured the backend "remote"! Terraform will automatically
use this backend unless the backend configuration changes.
goldsky-infra-prod Initializing provider plugins...
goldsky-infra-prod - Finding dopplerhq/doppler versions matching "1.1.6"...
goldsky-infra-prod - Finding hashicorp/helm versions matching "2.10.1"...
goldsky-infra-prod - Finding hashicorp/http versions matching "2.1.0"...
goldsky-infra-prod - Finding hashicorp/kubernetes versions matching "2.23.0"...
goldsky-infra-prod - Finding hashicorp/random versions matching "3.1.3"...
goldsky-infra-prod - Finding hashicorp/tls versions matching "3.1.0"...
goldsky-infra-prod - Finding hashicorp/aws versions matching "5.15.0"...
goldsky-infra-prod - Using hashicorp/tls v3.1.0 from the shared cache directory
goldsky-infra-prod - Using hashicorp/aws v5.15.0 from the shared cache directory
goldsky-infra-prod - Using dopplerhq/doppler v1.1.6 from the shared cache directory
goldsky-infra-prod - Using hashicorp/helm v2.10.1 from the shared cache directory
goldsky-infra-prod - Using hashicorp/kubernetes v2.23.0 from the shared cache directory
goldsky-infra-prod - Using hashicorp/random v3.1.3 from the shared cache directory
goldsky-infra-prod ╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider
│ hashicorp/http: could not query provider registry for
│ registry.terraform.io/hashicorp/http: the request failed after 2 attempts,
│ please try again later: Get
│ "https://registry.terraform.io/v1/providers/hashicorp/http/versions": read
│ tcp
│ [2601:47:477e:2ad0:a56b:9be8:aa40:edf0]:63227->[2600:9000:2209:9000:16:1aa3:1440:93a1]:443:
│ read: connection reset by peer
╵
This happens very frequently. Has anyone else had issues? Is hashicorp having network issues?