Is DexScreener down right now? Live status and what to do

Is DexScreener down right now?

The box below is our live answer. Green means our collector got a valid response from the DexScreener API within the last few seconds; red means it has failed five or more times in a row, which in practice means the API — and usually the website — is unreachable from our side. The bar is the last 24 hours, hour by hour: green for clean hours, amber for some errors, red where most calls failed.

One caveat: we measure the API, not your browser. If the box is green and dexscreener.com still does not load for you, the problem is almost always local — see the next two sections.

Common reasons DexScreener looks down

Most "dexscreener not working" moments are not outages. These are the causes we see most often, roughly in order of how common they are:

• CDN or Cloudflare challenge. DexScreener sits behind a CDN that sometimes serves a "checking your browser" page, a blank page, or an error code when traffic spikes. A hard reload after a few seconds usually clears it.
• Chain RPC lag. Prices and new pairs come from the blockchain. When a chain is congested — Solana during a launch frenzy, for example — charts freeze and new pairs appear late. That is "dexscreener not updating", not "dexscreener down", and it ends when the chain catches up.
• Browser extensions. Ad blockers, wallet extensions and privacy tools can block the scripts or WebSocket that feed the live charts. The page loads but stays empty.
• Rate limits. If you run a bot, a scraper or many tabs, DexScreener can start returning errors to your IP while everyone else is fine. Our own collector hits this when we poll too fast.
• Regional blocks or DNS. Some networks, countries and corporate firewalls block or misroute dexscreener.com. A VPN or a different DNS resolver changes the answer.
• A real outage. They happen, usually when traffic spikes. Most we have seen were brief, and the live box above turns red while they last.

What to check before you report it

Work through this list from the top; each step takes seconds and rules out one cause.

1. Look at the live box on this page. Green means the API answers — the problem is likely on your side.
2. Hard-reload the page (Ctrl+Shift+R or Cmd+Shift+R) and wait for any Cloudflare check to finish.
3. Open dexscreener.com in a private window with extensions disabled. If it works there, an extension is blocking it.
4. Try the token on another chain page or another token. If one chart is stuck but others move, it is chain RPC lag, not DexScreener.
5. Switch network: mobile data instead of Wi-Fi, or a VPN. If that fixes it, your network or region is the issue.
6. Check the DexScreener API directly if you are a developer: an HTTP 429 means you are rate-limited, a 5xx means the service is struggling.

If everything above fails and the live box is red, it is a genuine DexScreener outage. There is nothing to fix locally; wait it out and use the alternatives below.

What to use meanwhile

While DexScreener is down, the DXT Tools archive keeps working. Our database of paid activity — every Dex Paid profile, boost, ad and CTO we have recorded, with the market cap at the moment of payment — lives on our own server. The live feed, boosts, ads, CTO and the token check all read from that database, so history and "did this token pay?" answers stay available. New payments simply pause until the API returns; the feed catches up on its own afterwards.

For charts and prices, use another screener for the duration: GeckoTerminal covers most of the same chains and is what we use for ATH candles, and DexTools is the long-standing alternative on EVM chains. Both are listed with their strengths in the alternatives guide. None of them show who paid DexScreener — that is only here.

DexScreener alternatives, compared →

Where to get DexScreener support

DexScreener support runs through its official channels, not through us: the documentation at docs.dexscreener.com, the marketplace at marketplace.dexscreener.com for anyone who paid for a profile, boost or ad, and DexScreener's own social accounts for outage announcements. We know of no official status page. If a payment has not shown up, check the marketplace order first; profile updates usually land within minutes once the API is healthy.

DXT Tools cannot see your order or account. We can only tell you whether the API is responding and what it published.

How this status is measured

Our collector polls the public DexScreener API roughly 40 times a minute — one call every 1.5 seconds — rotating through the token-profile, boost, ad and community-takeover endpoints that feed the tracker (documented at 60 requests a minute in the API reference, checked 23 Aug 2026). Every call is counted as a success or an error, per minute, for the last 24 hours. A call counts as an error when the API returns a non-200 status, times out, or sends a body that is not valid JSON.

Healthy means fewer than 5 consecutive failures. One failed call is noise; five in a row (about eight seconds) almost always means the API is unreachable. On an HTTP 429 we back off for 30 seconds, and after 15 consecutive errors the collector pauses for a minute, so our own polling never makes an outage worse. The figures refresh every minute, straight from the collector's counters.

What this does not measure: the dexscreener.com website itself, the chart WebSocket, or any chain's data freshness. Green means "the API answers us"; it cannot promise the chart in your tab is moving.