Your Distributor Can Pull Your Music On A Claim. Not A Ruling.

On Saturday the 10th of October, independent artists started noticing their songs had gone from Spotify and Apple Music. No email. No warning. In several cases, no reason given. They were DistroKid artists, and the takedown notices named Universal.

What's confirmed

On 15 September, Universal Music Group sued DistroKid in federal court in Delaware. UMG says DistroKid is flooding streaming services with AI-generated “slop” — their word — and distributing recordings it has acknowledged it doesn't hold the rights to. The complaint asks the court to order infringing tracks removed and repeat infringers' accounts terminated.

On 12 October, DistroKid confirmed the removals. Amanda Ferri, their VP of Artist Services, told The Verge: “A very small number of recordings distributed through DistroKid have been removed in response to claims made by UMG.” And: “We strongly dispute the allegations underlying UMG's lawsuit, and regret the disruption to affected artists.”

Then on Friday 16 October, Universal and Sony filed again, demanding DistroKid hand over its internal data on how many AI-generated tracks it uploads, and the details of its AI detection tools. The filing calls DistroKid a “primary conduit” for Suno-generated music.

The mechanism is a clause, not a scandal

DistroKid's distribution agreement reserves the right to remove a recording from streaming services — quote — “if we receive any legal claims regarding the particular Recording”.

Any legal claims. Received. Not proven. Not ruled on. A claim arrives, and the clause is live.

That is not unusual, and I'm not telling you DistroKid is unusual for having it. Most distribution agreements have something that shape. The point is that you agreed to it, and you probably haven't read it.

Where it lands on you

The musician McGwire says six of his songs came down, that DistroKid didn't contact him before or after, and that when he chased it he first got a bot. One removal cited an uncleared sample — and Hypebot reports the song he supposedly sampled came out two years after his track did. The rapper Insane Ian says an original song was removed with no warning and no reason given. Those are their accounts, not findings.

The documented route back is a DMCA counter-notice. DistroKid's own guidance says that after a valid one, it has to wait ten business days before reinstating. And the streaming services may choose not to reinstate at all, under their own policies.

Ten business days is two weeks. If that lands on your release week, your release week is gone.

What this does not mean

• It does not mean DistroKid did anything wrong. They dispute UMG's allegations, they called it a very small number, and no court has decided anything yet.
• It does not mean the removed tracks were AI. Some of those artists say theirs weren't. Music Business Worldwide was careful to say it had not verified the rights status of those recordings, or whether they were even tied to UMG's claims. I can't verify it either.
• It does not mean switching distributor fixes this. That clause is common. Moving to a distributor whose agreement you also haven't read is not a plan.

What nobody outside DistroKid and Universal can tell you is how many tracks came down, or how many were correctly identified. That is part of why the filing on the 16th exists.

Three things. The first takes ten minutes.

1. 1Open your distribution agreement and search it for the word “remove”. Find the clause that says when they can take your music down, and whether they have to tell you first. Read that one paragraph. Whatever it says, you'll know — which is more than most people reading this.
2. 2Build the evidence file before you need it, not after. For every release: the sample clearances, the beat licence and who else it was sold to, the cover licence, the split sheet, and the date you published. If you ever file a counter-notice you'll be assembling all of that under time pressure, with a ten-business-day clock on top.
3. 3Stop letting one dashboard be the only place your catalogue exists. If your distributor's account is the only record of what you released and when, then when something goes wrong you find out in their order, at their speed.

That third one is what droplr is. One record per release — the links, the splits, the rights — somewhere that isn't your distributor's dashboard.

It will not stop a takedown. Nothing I build can. What it does is mean that when one happens, you already know what you published, where it went, and when. I build it on my own, one person in Brisbane.