You can remix anyone on Suno, but you can't see the map of who remixed whom — the platform erases it. We once glimpsed a corner of it through a gap. That gap has since been welded shut.
When one Suno track descends from another, that lineage is written into its metadata: extension chains, "edited from", "covered from". It should be the most interesting social graph in AI music. But on nearly every public endpoint, Suno replaces those pointers with a string of all-zero UUIDs (00000000-…-000000000000) — you learn a source exists, but never which clip it was.
A few places forgot to redact. We used those gaps to record every edge that fell through, and assembled a cross-author remix graph. This report is not about how large that graph will grow. It is about the fact that it will not grow at all.
104
Lineage edges we recorded before the gaps closed, spanning 142 distinct clips. That count is now effectively capped — it holds steady as Suno patches, it does not grow.
The edges come in kinds. The vast majority are extension chains — the internal relationships as a single song is lengthened segment by segment. The true remix gestures — edited from and covered from — are rarer, 12 in all, but they are the social act of one person building on another's work.
Lineage edges by type
- extension chain90 · 87%
- edited from6 · 6%
- covered from6 · 6%
- edit history2 · 2%
Three leaking taps, all now closed
This graph did not accrete gradually. It is the sum of one backfill and a few leaks that are now sealed. Here is where each edge came from, and the current state of that tap:
Edge provenance · and its status
- trending feednow a frozen 2024 snapshot102 edges
- watched playlistsserializer redacts2 edges
Put the three channels together and the conclusion is hard: no live pipeline can add a single edge to this graph anymore. It is not a young dataset that will fill in — it is a sealed archive, a one-time slice of history. That is exactly what makes it rare: as far as we know no one else holds the same graph, and Suno has made sure it cannot be collected again.
We see the remixer, not the source
Even inside this sealed archive, the telling asymmetry holds. Among the leaked edges, the child — the clip that did the remixing — almost always resolves to a public creator. The source it remixed — the parent — almost never does. Across all 104 edges, the number of sources we can publicly name is:
0
Sources we can name (out of 104 edges). By contrast, 82 edges have a nameable public remixer, drawn from 38 clips that surfaced on the leaking endpoints.
But even an anonymous source leaves a shape. Take the source clip below: its identity is redacted, yet our records prove that 2 different public creators each built work from it. That is the silhouette of a cross-author remix hub — we can see the spokes even when the center is dark.
A cross-author remix hub
The remixes we caught
Here are the nameable remix tracks we recorded — each declaring a (redacted) source of its own. With the gaps closed, this list is now fixed:
- covered from
The Questions
@alejopastran - covered from · edited from
The Void (piano version)
@frowns - edited from
AWAKE'S Soundclash Master Remix
@imess - covered from · edited from
Soundclash Dembow Remix (feat. Flosstradamus)
@jpichardo - edited from
Only One God
@mazta - covered from · edited from
Re Start~🎶(House) 2024 9/17
@restina - covered from
Sun Rise (Cover)
@teaboy555 - covered from · edited from
Flosstradamus - Soundclash Master ( Cover Suno Remix Contest)
@vvmusicbirdspath
These edges aggregate into a cross-author remix network. It will not grow further, but it remains browsable — read it as a frozen archive: the remix network.