Skip to content

429: Contact support⚓︎

If you have worked through the guidance on the other 429 pages and are still seeing rate limit blocks — or if your situation requires a direct conversation — this page describes how to reach us.

This is the contact path specifically for 429 Too Many Requests rate limit issues on Maven Central. For other types of errors or general support, see Where to find help.

Before you contact us: egress IP is required⚓︎

We will ask for your egress IP first

The egress IP address (or IP range) that your traffic exits from is the first piece of information we need. Without it, there is very little we can do. We cannot look up rate limit activity by organization name, project name, or account. We can only look up what Maven Central sees at the network edge, which means we need the specific IP or range involved.

Please do not contact support without this information — your ticket will be blocked until we have it.

Your egress IP is the outbound IP address that Maven Central sees when your builds, tools, or systems make requests. This is typically:

  • The NAT gateway IP for your cloud environment (AWS NAT Gateway, GCP Cloud NAT, Azure NAT Gateway, etc.)
  • The corporate proxy or firewall IP if your organization routes outbound traffic through a proxy
  • The hosted CI provider's egress IP or IP range if you are using a service like GitHub Actions, GitLab CI, CircleCI, Jenkins, or similar
  • The VPN egress IP if your traffic exits through a corporate VPN

To find your egress IP:

  • Ask your cloud or network operations team for the NAT gateway or egress IP associated with the environment where builds run
  • Check your cloud provider's console for NAT gateway configurations
  • For hosted CI, check the provider's documentation for their published egress IP ranges
  • Run curl -s https://api.ipify.org from inside the affected environment (not your local machine) to see the outbound IP

If you have multiple environments or regions involved, provide all relevant IPs or ranges.

Exception: shared egress where the IP is not identifiable⚓︎

If you are on a shared platform — hosted CI, corporate VPN, cloud infrastructure — where the egress IP is not under your control and you genuinely cannot identify it, say so explicitly when you contact us. That context matters. We can still investigate, though our ability to act may be limited if the traffic is controlled by an infrastructure provider rather than your organization. In that case, getting your provider to contact us directly (using the infrastructure provider path) is often the faster route.

Commercial Sonatype customers⚓︎

Commercial Sonatype support account

If you have a paid Sonatype support account as part of a Sonatype product license, please use it. Commercial support tickets are routed and prioritized separately from the general Central Support queue. See How do I create a standard request for product/technical support for how to open a ticket.

What else to include⚓︎

Read the overview and follow the relevant path first

Before contacting us, make sure you have read the 429 Too Many Requests overview — so you know what has changed and, importantly, why — and worked through the path that applies to your situation: no repository manager, existing repository manager, infrastructure provider, tooling provider, or shared egress.

When you contact us, tell us which path applies to you, what you investigated, what you found, and what you changed. If you have not done this yet, we will ask you to work through it before we can investigate further.

Beyond the egress IP, the more context you provide, the faster we can investigate. Useful details include:

  • Which Maven Central endpoints are being accessed — repository download (repo1.maven.org, repo.maven.apache.org), search (search.maven.org), or publishing (central.sonatype.com)
  • What is generating the traffic — builds, scanners, container builds, CI jobs, data cluster provisioning, SCA tools, automated scripts, or other tooling
  • Whether you use a repository manager — and if so, whether the affected traffic is expected to flow through it
  • Your build toolchain and environment — Maven, Gradle, SBT, Bazel, etc.; cloud provider; CI platform; container orchestration
  • Any investigation you have already done — what you have checked, what you have found, any changes you have already made

Contact us⚓︎

Central Support