Skip to content

Document 'Access to this endpoint is temporarily disabled' error #4332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lucasra1 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document 'Access to this endpoint is temporarily disabled' error #4332

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions content/docs/connect/connection-errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ This topic describes how to resolve connection errors you may encounter when usi
- [The request could not be authorized due to an internal error](#the-request-could-not-be-authorized-due-to-an-internal-error)
- [Terminating connection due to idle-in-transaction timeout](#terminating-connection-due-to-idle-in-transaction-timeout)
- [DNS resolution issues](#dns-resolution-issues)
- [Error: Access to this endpoint is temporarily disabled](#access-to-this-endpoint-is-temporarily-disabled)

<Admonition type="info">
Connection problems are sometimes related to a system issue. To check for system issues, please refer to the [Neon status page](https://neonstatus.com/).
Expand Down Expand Up @@ -345,4 +346,8 @@ Failure to resolve the Neon hostname can happen for different reasons:

Using a VPN routes DNS queries through a different resolver and often bypasses the issue entirely.

## Access to this endpoint is temporarily disabled

This error can for example happen if you want to connect to a anonymized branch, but the anonymization is not finished yet
Copy link

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence lacks a period at the end. All sentences should end with proper punctuation for consistency with the rest of the documentation.

Suggested change
This error can for example happen if you want to connect to a anonymized branch, but the anonymization is not finished yet
This error can, for example, happen if you want to connect to an anonymized branch, but the anonymization is not finished yet.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar error: "can for example happen" should be "can, for example, happen" with commas around "for example". Also, "a anonymized" should be "an anonymized" (incorrect indefinite article).

Suggested change
This error can for example happen if you want to connect to a anonymized branch, but the anonymization is not finished yet
This error can, for example, happen if you want to connect to an anonymized branch, but the anonymization is not finished yet

Copilot uses AI. Check for mistakes.

Comment on lines +351 to +352
Copy link

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The documentation for this error is quite brief and provides only one specific example. Consider expanding it to include: (1) a general explanation of when this error occurs, (2) additional scenarios that might trigger it, (3) suggested actions users can take to resolve or work around the issue, and (4) any relevant timeframes or expectations. This would provide more helpful guidance to users encountering this error.

Suggested change
This error can for example happen if you want to connect to a anonymized branch, but the anonymization is not finished yet
This error indicates that the Neon endpoint exists but is currently unavailable for new connections. The endpoint is usually disabled by the system for safety, maintenance, or data-processing reasons and is expected to become available again without any changes to your application code.
**Common reasons**
- You are connecting to an anonymized branch and the anonymization process has not finished yet. Until anonymization completes, the endpoint is blocked to prevent access to partially processed data.
- The project or endpoint is undergoing short-term maintenance or an automated operation (such as scaling or moving resources) that temporarily disables new connections.
- The project has been temporarily restricted due to billing, quota limits, or abuse-protection safeguards.
- The endpoint has been paused or restricted via project settings or by an organization administrator.
**What you can do**
- **Wait and retry:** For transient operations (such as anonymization or brief maintenance), the endpoint typically becomes available again after the operation completes. Try reconnecting after a short delay.
- **Check branch and endpoint status in the Neon console:** Confirm that the branch exists, anonymization (if enabled) has completed, and that the endpoint is in an active/available state.
- **Verify project and billing status:** Ensure your project is active, in good standing, and not subject to plan limits or account restrictions that could cause temporary suspension of endpoints.
- **Review any incident or maintenance notifications:** Check your email and the Neon status page or dashboard notifications for ongoing incidents or maintenance windows that might affect connectivity.
- **Contact support if the error persists:** If the endpoint remains disabled for an extended period and you see no relevant notices in the console or status page, reach out to Neon support with the project ID, endpoint ID, and approximate time when you observed the error.
**Expected timeframes**
- **Anonymized branches:** For small branches, anonymization usually completes within a few minutes. Larger datasets can take longer, depending on size and workload. If the endpoint is still disabled after a reasonable wait (for example, 15–30 minutes for large datasets), verify status in the console or contact support.
- **Planned maintenance and short-term operations:** These are typically brief. If the endpoint remains disabled well beyond the communicated maintenance window or more than 30 minutes without any status updates, contact support.

Copilot uses AI. Check for mistakes.
<NeedHelp/>
Loading