The feed Suno forgot

We spent three months monitoring what we thought was Suno's Explore front page. It was a September-2024 snapshot the platform had stopped updating almost two years earlier — served untouched, straight from origin, right up until Suno removed the public route to it on 2026-07-24. The object itself survived; we still read it directly today. We have the receipts, from the freeze through the door closing.

We built a monitor and pointed it at Suno's trending feed. Three months later we understood why it never moved: not because it had frozen, but because no one was maintaining it. We had been photographing a fossil.

Here is how it started. Suno published an endpoint — /api/trending — that returned a chart called "Explore — Top 10 Songs" (playlist ID 1190bf92…). Anyone could read it without logging in, so we did the obvious thing and treated it as the platform's public face. From Apr 13, 2026 we photographed it once a day through Aug 22, 2026: 129 distinct days of captures.

It never changed. The same track held #1 for 129 days straight — Tsunami-Raptor (LIVE) by @steicamel. We first assumed we had a story about a frozen chart. A forensic teardown on 5 July 2026 overturned that reading: this is not a live feed that stopped moving. It is an object the platform forgot.

129 days

Days we watched the same 2024 track sit unmoved at the top of this endpoint — the entire length of our capture window. The real freeze ran far longer: every track on the list was created in September 2024, and the snapshot was served untouched for roughly 22 months. Suno removed the public route to it on 2026-07-24; the object survived, and we still read it daily.

The receipts

Open all 49 tracks on the list and their creation timestamps fall inside a single 72-hour window: 15–17 September 2024. It reads like someone hand-picked a "top ten" over that weekend and nobody touched it again. That is not how a live chart behaves; it is a pinned snapshot.

And, as of our 5 July 2026 teardown, it was still served fresh. Two fetches 108 seconds apart returned byte-identical content, with Cf-Cache-Status: DYNAMIC and no cache directives — meaning that 2024 data was not stuck in a CDN layer; the origin was regenerating it as a live response every time. The endpoint was alive; the data was dead. The #1 track gained just 56 plays across the three months we watched — real listeners were not looking at this list. Less than three weeks later, on 2026-07-24, Suno removed the endpoint's public route — the full account, including the door it left open, is in the coda below.

The line below is daily turnover of the list's top ten: what share is new versus the day before. A living chart jitters; this one hugs the baseline as a flat line. Of the 128 adjacent days we compared, 127 showed zero turnover, and the top three has been identical for 8 days. We used to read this flatline as a freeze. It is really the flat trace of an abandoned feed.

Top-10 turnover · daily

Each point is the share of that day's top ten that is new. The red segment marks the most recent unbroken zero-turnover run — once read as a freeze, now confirmed as evidence of an abandoned endpoint. Drawn from our daily snapshots of this 2024 snapshot.

Distinct tracks that have ever appeared in the top ten across our full 129-day window — all of them created over a single weekend in September 2024. Each has averaged 117.3 days on chart.

Current top ten · days on chart

1
Tsunami-Raptor (LIVE)@steicamel129 days
2
The Boss@aimagician129 days
3
Did you forget? (ft. TongMick)@procrastopia129 days
4
Fading Lights@fabiofalcone129 days
5
Flosstradamus - Soundclash Master ( Cover Suno Remix Contest)@vvmusicbirdspath129 days
6
Static@namestaken129 days
7
Never too old to Party - ft. @renhal@spupuz129 days
8
Pain In The Butt [SSC5, USA]@aimagician129 days
9
Echoes of Yesterday (Cover)@tagliuz129 days
10
Boss Battle (Flosstradamus Remix)@kingbanana8 days

Suno moved on — and never told the API

So where is the real Explore? It moved. Per Suno's own release notes, the platform ran an "Explore Refresh" on 14 May 2026 and rebuilt discovery around a set of human-curated playlists — Staff Picks (content through 2026-06-20) and Best of v5.5 (through 2026-06-22) among them. We checked those shelves the same day: they share zero tracks with the fossil chart.

The irony runs deeper. Even inside the new curated shelf, the playlist literally named "Trending" (ID 07653cdf…) is itself a stale snapshot from around May 2025. In other words, nothing Suno exposes to the public under the word "trending" is actually live. The one we had been monitoring was simply the oldest of them.

What it means

We surface this without editorializing. But the implication reads plainly: Suno's public discovery data for third parties is unmaintained. Anyone trying to understand what is popular on Suno right now from the outside — researchers, creators, other tools — is handed a 2024 fossil instead of the real discovery surface.

This is not only our claim. Music Ally reported in March 2026 that Suno exposes no real trending data to third parties — a project called SunoCharts had to fall back on placeholder dummy data — and per Music Business Worldwide (July 2026), Suno's forthcoming official API is generation-only, with no discovery or charts. The difference is that we hold dated proof: 84 daily snapshots plus a byte-level forensic teardown that pins down exactly when this data stopped updating.

The practical advice for creators shifts with it: stop hoping to break into a "trending" chart the platform has all but forgotten. Invest where you hold the levers — your portfolio page, human-curated playlists, remixes and collaborations. That is where discovery actually happens now.

Update, 2026-07-27 — the route is gone, the object isn't

Everything above described a feed that had stopped updating but was still there. That is still the state of things, though the door changed. Sometime between our capture on Aug 22, 2026 and the next scheduled run, Suno removed the public route into it — not a redesign, a plain 404 at /api/trending. But the object behind that route, the playlist itself, was never deleted: it is still public, still readable by its own address, and its play counts are still moving. We now read it that way, daily, and hold the complete record of the route's last months and the exact window it disappeared: read the full account, including the mistake we made telling this part of the story the first time. The preserved leaderboard at /trending and this report both stay online as a historical exhibit — but unlike a sealed archive, the readings keep coming.

Methodology

From Apr 13, 2026 we snapshotted this chart once a day through Suno's public, W3C-oEmbed-discovered endpoint (read-only, anonymous, no HTML scraping, no login) — through Aug 22, 2026, our last capture through the /api/trending alias route before Suno removed it. When a day had multiple captures we kept the latest; every metric is day-granular, covering 129 distinct days. The 49-clip creation window, the byte-for-byte stability and the DYNAMIC origin serving come from a 2026-07-05 anonymous forensic capture of the same public endpoint, back when that route still answered. Captures since 2026-07-27 read the same object directly by its playlist UUID.

Prior work and correction: a sibling probe project once logged a 67-day zero-rotation streak in this chart's top three as a freeze. That same project's 2026-07-05 teardown corrected the reading — those 67 days were measuring the 2024 snapshot itself. Our independent 84-day window agrees with the correction: what looked like a freeze is an abandoned endpoint.