The short version
DistroKid has confirmed it is removing songs from streaming services in response to Universal Music Group’s copyright lawsuit — and the removals are hitting artists who did nothing wrong. A licensed Stevie Wonder cover, an original nerdcore track, and an entire album that sat untouched for years have all vanished with no warning. If you distribute through DistroKid, this is the one story in October 2026 you can’t afford to skim.
What DistroKid actually admitted
On September 15, 2026, Universal Music Group sued DistroKid in the US District Court for the District of Delaware, accusing the distributor of flooding streaming platforms with infringing material. That’s the lawsuit. The new development — the part that affects your catalog directly — came on October 10, when The Verge reported that DistroKid is acting on UMG’s claims by pulling recordings.
DistroKid’s VP of Artist Services, Amanda Ferri, confirmed it on the record:
“A very small number of recordings distributed through DistroKid have been removed in response to claims made by UMG.”
Read that sentence twice. “A very small number” is doing a lot of work there — no actual figure, no criteria for which recordings, and no description of the review process. What we know for certain is that removals are happening, they’re tied to UMG’s claims, and DistroKid says it disputes the underlying lawsuit while complying with the claims anyway.
The next court date to watch: DistroKid’s response in the case is due December 4, according to Digital Music News’ coverage this week. The case itself will grind on for months. The takedowns, though, are happening right now.
The false positives, name by name
Here’s where the story stops being about lawyers and starts being about musicians. The artists who’ve come forward so far don’t fit the profile of whoever UMG says it’s after.
McGwire: six songs gone, including a licensed cover
Musician McGwire told The Verge that six of his tracks were removed from streaming services. DistroKid didn’t contact him before or after — he had to chase them down himself to find out why, and before he could reach a human he sat through what he called a “lengthy circular conversation” with a support bot.
Now look at what was actually removed. One track was a cover of Stevie Wonder’s “Isn’t She Lovely” — which McGwire says he properly licensed. Another used a beat he bought on a marketplace, a beat other artists had licensed too. And then there’s the one that tells you everything about how this process works: one of his songs was flagged for an uncleared sample from a track that was released two years after his own song. Read that again. He was accused of sampling a song that didn’t exist yet when his came out.
Insane Ian: an original song, no explanation
Nerdcore rapper Insane Ian posted that he “had an original song taken down with no warning, and they wouldn’t tell me why either.” An original song. No cover, no sample dispute, no AI involved — just gone, with no reason given.
King Chase: an entire album, erased after years
Rapper King Chase told The Verge that an entire album for an artist he’d been working with was removed with no communication or explanation. “The album had been up for 3-4 years without incident,” he said, adding there had been “no copyright strikes or anything either.” Three to four years of clean history, and then one day it’s just not on Spotify anymore.
None of these three were contacted before their music disappeared. None were contacted after, either — each had to go find DistroKid and ask what happened to their own work.
Why “it’s only AI slop” doesn’t explain this
UMG’s complaint is aimed at what it calls an “AI-slop pipeline” — AI-generated tracks masquerading as human-made, unauthorized remixes, and altered copies of its recordings. And to be fair about the legal framing, the complaint explicitly excludes clearly-disclosed AI music. It’s targeting deception, not disclosure.
But stack that framing against the three cases above and it falls apart:
- A licensed Stevie Wonder cover is the opposite of an AI-slop upload. It’s a human performance of a famous song, with a license.
- An original nerdcore song with no samples is the opposite of an infringing remix.
- An album live for 3-4 years with zero strikes doesn’t match a flood of fresh infringing uploads.
So the honest read is this: whatever review process DistroKid is running under litigation pressure, it’s misfiring. The mechanism — automated flags, rushed reviews, shoot-first compliance — is catching human-made, licensed, long-standing work. When a distributor starts deleting first and asking questions never, the lawsuit’s careful legal distinctions stop mattering to the artist staring at a grayed-out Spotify profile.
That’s the part that changed how I think about my own catalog, and I’ll get to that in a minute.
What artists are saying right now
The frustration is spilling out across Reddit and social media, and it’s not just the three named cases. Digital Music News quoted one Redditor whose album was supposed to drop Friday the 16th: “My album is supposed to come out Friday the 16th, and DistroKid rejected the whole thing because one track matched another artist’s song.” The poster’s explanation: both artists had used the same beat, except he had actually paid for the lease and the other artist hadn’t.
Another commenter described UMG putting a claim on one of his songs over an alleged sample — from a track released two years after his own — followed by DistroKid deleting his whole album with no notification and handing him a copyright strike. He says both songs used the same commercially available sample pack, sent DistroKid all his proof, and is still waiting for a response.
The through-line in every one of these stories is the same: no warning, no explanation, no clear path back. As Music Ally put it this week, distribution is supposed to be the simplest, most reliable part of the process — “music goes in; money comes out.” Right now, for some DistroKid artists, music goes in and silence comes out.
Where I stand in all of this
Let me be straight with you about my own position, because I write about this stuff and I also live it. I distribute my own music through DistroKid. My setup is human-written lyrics with AI vocals, and I disclose the AI involvement everywhere — which puts me squarely in the lane UMG’s complaint explicitly excludes. On the merits, I should be fine.
McGwire’s licensed cover should have been fine too. That’s the sentence that keeps replaying in my head.
My catalog is small — my DistroKid dashboard shows $274.46 in streaming earnings plus $140 in referrals, $414.46 total withdrawn. I’m not pretending I’m operating at a scale where a takedown would make headlines. But the principle doesn’t care about scale: if a properly licensed cover can vanish without warning, then “I did everything right” is not the shield I thought it was. The risk isn’t about whether your music is legitimate. It’s about whether a stressed, lawsuit-driven review process can tell the difference — and right now, the evidence says it can’t always.
So I’m watching my dashboard like a hawk, and I’ve put together the checklist below from everything reported this week. If you distribute through DistroKid, I’d do the same starting today.
If your music disappears, do this — in this order
1. Don’t touch anything yet. The worst first move is re-uploading in a panic. Screenshot your DistroKid dashboard, the grayed-out release on Spotify and Apple Music, and note the dates. You want a paper trail of what was there and when it vanished.
2. Confirm it’s a removal, not a glitch. Stores have hiccups. Check your artist profiles on Spotify and Apple Music directly, and check DistroKid’s dashboard for any notice or status change on the release.
3. Contact DistroKid support in writing. Open a ticket and keep everything in the thread. Fair warning from the reported cases: expect friction getting to a human. McGwire’s bot loop is apparently the normal experience now, not the exception.
4. Gather your proof before they ask. Licenses for covers, beat lease agreements, sample pack receipts, original upload confirmations, ISRC codes, release dates. The McGwire cases show that “I licensed it” only helps if you can produce the paperwork fast.
5. Don’t re-upload the same recording under the same ISRC until the removal status is cleared. This one’s important. A duplicate ISRC floating around while the original is flagged can tangle your metadata and make reinstatement harder. Sort out the status of the existing release first.
6. Read RouteNote’s walkthrough. RouteNote — a competing distributor, which makes this refreshingly candid — published a guide called “DistroKid Removed My Music: Why It Happens and What to Do Next” that walks through identifying why a removal happened, how to challenge it, and how to protect the rest of your catalog. It’s the most practical single resource I’ve seen on this so far.
7. Know about counter-notices. AllHipHop’s coverage noted that artists who believe in good faith that a removal was a mistake can send DistroKid a counter-notice. “Good faith” is the operative phrase — don’t file one over a track you’re unsure about.
Should you switch distributors?
Honest answer: not in a panic, and not mid-crisis. If your catalog is currently intact on DistroKid, your royalties, playlists, and release history are tied to that pipeline, and a hasty migration can cost you months of momentum. I compared the major distributors in detail in my DistroKid vs CD Baby vs TuneCore vs Ditto vs RouteNote breakdown — if you’re weighing a move, start there, not with a cancellation click.
That said, this is also the right moment to make sure your next upload doesn’t give anyone a reason to flag it. My guide to DistroKid upload mistakes covers the metadata and rights errors that draw scrutiny — worth a re-read before you submit anything this month.
And if you’re still deciding on DistroKid itself: new artists can get a discount through my referral link (affiliate disclosure: I may earn a commission if you sign up). I’d just recommend it differently today than I would have a month ago — go in with your eyes open, keep local backups of every master and ISRC, and read the comparison piece first.
For context on how we got here, by the way, this isn’t DistroKid’s first rough month. I covered the delayed YouTube royalties saga — and the artists talking lawsuits over it last week. Different issue, same theme: communication.
The legal side, explained by an actual music attorney
If you want the lawsuit itself broken down by someone who does music law for a living, this video from Top Music Attorney is the clearest explainer I’ve found:
The key date from the legal calendar: DistroKid’s response to UMG’s complaint is due December 4. The case will likely stretch well into 2026 — but as this month proves, you don’t need to wait for a verdict for the fallout to reach your catalog.
Frequently asked questions
Did DistroKid admit to removing songs because of the UMG lawsuit?
Yes. VP of Artist Services Amanda Ferri told The Verge that “a very small number of recordings distributed through DistroKid have been removed in response to claims made by UMG.” DistroKid says it disputes UMG’s lawsuit while complying with the claims.
I don’t use AI in my music. Can my songs still be removed?
Evidently, yes. The named cases so far include a licensed cover, an original song with no samples, and an album that had been live for years with no strikes. None involved AI-generated music masquerading as human-made — which is what UMG’s complaint actually targets.
What’s the first thing I should do if my music disappears from Spotify?
Screenshot everything before you touch anything — your DistroKid dashboard, the missing release on each store, and the dates. Then confirm it’s a real removal rather than a store glitch, and open a written support ticket with DistroKid. Don’t re-upload the same recording under the same ISRC until the removal status is resolved.
Can a wrongly removed release be reinstated?
Sometimes. You’ll need your proof ready — licenses, beat leases, sample pack receipts, release dates — and you may need patience getting past support bots to a human. Artists who believe in good faith the removal was a mistake can also file a counter-notice. RouteNote’s removal guide walks through the challenge process step by step.
Should I leave DistroKid right now?
Not in a panic. If your catalog is intact, your royalties and playlists are tied to that pipeline, and migration takes months. Document everything, keep local backups of all masters and ISRCs, and compare alternatives calmly — my distributor comparison is a good starting point.
When is the next development in the UMG lawsuit?
DistroKid’s formal response to the complaint is due December 4, 2026. The case was filed September 15 in the US District Court for the District of Delaware and is expected to run well into next year.
Sources: Music Business Worldwide on DistroKid’s confirmation, Exposed Vocals on the takedowns and the December 4 deadline, Digital Music News on the Reddit reports, RouteNote’s removal guide. Artist accounts are the artists’ own claims as reported; none are court findings.
New to DistroKid? You can get a discount through my referral link. (Affiliate disclosure: I may earn a commission if you sign up.)