Triton One Docs
WebsiteCustomer Portal
  • Introduction
  • RPC Pool
    • Introduction
    • GeoDNS
    • Abuse prevention
    • Rate Limits
    • Proxying
    • Support FAQs
    • Privacy & Security
  • Chains
    • Solana
      • Streaming
      • BigTable Archive
      • Improved Priority Fees API
        • For RPC Providers
      • Cascade
        • Transaction sending advice
        • Buying Transaction Bandwidth
        • Providing Transaction Bandwidth
      • Web3JS Socket/Connection Issues
      • Deprecated calls Solana 2.0
    • Pythnet
    • SUI
    • Others
  • Digital Assets API
    • Introduction
    • Fungible Assets
    • API Methods
      • Get Asset
      • Get Asset Proof
      • Get Assets By Authority
      • Get Assets By Owner
      • Get Assets By Group
      • Get Assets By Creator
      • Search Assets
      • Get Token Accounts
      • Get Signatures For Asset
      • Get NFT Editions
      • Get Asset Proofs
  • Project Yellowstone
    • Introduction
    • Dragon's Mouth gRPC Subscriptions
    • Old Faithful Historical Archive
      • Old Faithful Public Report
    • Steamboat Custom Indexes
    • Whirligig WebSockets
    • Fumarole Reliable Streams
    • Vixen Data Pipelines
      • Generate a Yellowstone Vixen Parser with Codama
  • Shield Transaction Policies
  • Account Management
    • Payments
    • Account management API
      • Introduction
      • Auth & Headers
      • Accounts
      • Address Watch Lists
      • Subscriptions
      • Subscription Types
      • Endpoints
      • Tokens
      • Rate Tiers
  • Trading APIs
    • Introduction
    • Jupiter swap
    • Pyth Hermes
    • Bundle simulation by Jito
  • Validators
    • Introduction
    • Vote account setup
    • Node identity protection
  • Pyth Publishers
    • NGINX proxy
    • Testnet, Devnet and Pythnet
Powered by GitBook
On this page

Was this helpful?

  1. RPC Pool

GeoDNS

PreviousIntroductionNextAbuse prevention

Last updated 1 year ago

Was this helpful?

For multi-node pools, such as our shared service, we leverage GeoDNS to route requests to a server that is near the user. This helps reduce latency greatly. You can observe the region you are routed to by visiting your endpoint on https://<endpoint>.rpcpool.com .

There are certain conditions under which we override GeoDNS and may serve you a node further away:

  1. If the closest region is overwhelmed with requests we shed load to other regions

  2. If the closest region is down, we move the load to other regions

We apply very short DNS TTLs (30 seconds) so you should relatively quickly be moved to another region and back again once load/up status changes.

If your users or you are using your RPC Pool endpoint via a proxy that can have an impact on the effectivness of GeoDNS and may cause inbalanced routing. .

If you find that you are not getting routed to a region close to you please verify:

  • If you're using a VPN that would alter the region that your DNS requests comes from

  • If you are using a DNS service that removes/masks EDNS

  • If you have a caching DNS server that doesn't respect DNS TTL

Please read more about Proxying here