Mirror Sites
This section collects mirror endpoints for commonly used developer services, registries, and package ecosystems.
Mirror services provide stable alternative entrypoints for environments where direct upstream access is slow, unstable, restricted, or operationally inconvenient. The available pages document supported domains, upstream targets, common usage patterns, and service-specific notes.
Scope
Mirror documentation will be expanded over time. Current and future pages may cover:
- Package registry mirrors
- Container and OCI registry proxies
- Developer service mirrors
- Regional or provider-specific proxy endpoints
- Access checks and operational guidance
Each service page should be treated as the source of truth for its own endpoint list, support level, and usage examples.
Access control example
Some mirror endpoints may enforce network-level access control. The following check is a general example for validating whether your current environment can access a protected mirror endpoint:
For other services, replace the domain with the mirror endpoint you want to test. Protected endpoints commonly expose the same test path:
Typical responses:
Access AllowedAccess Denied
Not every mirror is required to use this exact access model. Check the service-specific page before relying on access control behavior in automation.
Current mirror pages
| Mirror | Description |
|---|---|
| Google Translate | Google Translate web and API mirror endpoints |
| GoProxy | Go module proxy mirror |
| NPM | npm registry mirror |
| Container Registry Proxy | Docker and OCI registry mirror endpoints |
| Aliyun Container Registry Proxy | Shanghai-region Aliyun Container Registry proxy |
Domain conventions
Most mirror endpoints are organized under the following domain pattern:
| Domain pattern |
|---|
*.m.kubectl.net |
Some services may also provide non-m domains or provider-specific entrypoints. Use the exact hostname listed on the relevant service page.
Support
For questions or support, contact: dev@intellij.io