Discontinuation bricking

❗Article Status Notice: This Article is a stub

---

This article is underdeveloped, and needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. Learn more ▼

Issues may include:

• This article needs to be expanded to provide meaningful information
• This article requires additional verifiable evidence to demonstrate systemic impact
• More documentation is needed to establish how this reflects broader consumer protection concerns
• The connection between individual incidents and company-wide practices needs to be better established
• The article is simply too short, and lacks sufficient content

How you can help:

• Add documented examples with verifiable sources
• Provide evidence of similar incidents affecting other consumers
• Include relevant company policies or communications that demonstrate systemic practices
• Link to credible reporting that covers these issues
• Flesh out the article with relevant information

This notice will be removed once the article is sufficiently developed. Once you believe the article is ready to have its notice removed, visit the Discord (join here) and post to the #appeals channel, or mention its status on the article's talk page.

Discontinuation bricking occurs when a product is rendered no longer functional ("bricked") because the manufacturer has decided to discontinue it. Discontinuation bricking almost exclusively occurs in products that require a connection to a remote server hosted by the producer. The product may become bricked if the company decides to shut down services or if the company goes out of business entirely, while not allowing the consumer to substitute those services with alternative and/or self-hosted solutions. End-of-life for a product does not require the product to be bricked.

End-of-Life compared to bricking

	EOL	Soft brick	Discontinuation bricking
Device boots	yes	yes	sometimes
Basic functionality	yes	sometimes	no
Software updates	sometimes	no	no

Impact to consumer rights

Discontinuation bricking, similarly to planned obsolescence, harms the consumer by making a product they paid for to stop functioning, resulting to loss of ownership of said product, as functionality is stripped from it.

Dependence on third-party bypasses

After a product has been bricked, a consumer may wish to repair their product and return it back to a functioning state. De-bricking a product is not impossible but can be difficult depending on the severity of the problem. Consumers will inevitably look to third-parties for methods to bypass the bricking which may open the user to security and safety risks. Bypasses may end up being expensive, with more complicated server-dependent products needing potentially complicated server infrastructure.

Resale falsification

Products are often resold on the internet, and may be put on sale before a discontinuation bricking occurs with valid information but become invalidated afterwards causing false advertising. This has many implications:

1. Sellers may be completely unaware of the discontinuation bricking and will continue selling their product, hurting seller reputation once the product becomes bricked and no longer functions afterwards.
2. Buyers may be completely unaware of the discontinuation bricking and will buy the product, only to have it not function and harming the buyer.
3. Customers may learn about the discontinuation and decide to sell the product without providing adequate details, even without any malicious intent.

Environmental impact

Discontinuation bricking will inevitably generate waste given that the product is no longer functional, and consumers will be forced to discard the product.

Warning signs of discontinuation bricking

Discontinuation bricking is usually a consequence of a remote service shutting down that the product depends on for complete functionality. The risk of discontinuation bricking occurring can be assessed beforehand by observing warning signs, such as:

• Product requires an internet connection to a remote server: If a product requires connection to a remote server for functionality, there is a risk that the company may shut down the server and brick some function, if not all functions of the product. These connections may be necessary because:

• Product requires remote authorization: Product only works if you can receive authorization from an authorization server. If the authorization server shuts down, login will become impossible. An unusual example being the Spotify Car Thing which stopped functioning after Spotify unauthorized the Car Thing from interacting with the Spotify App API.

• Product has features dependent on remote sources: The product may brick if it is unable to access remote information because of server outages.

• Product depends on a phone application to work: Updates to the app may remove support for the discontinued product. An example being the Spotify Car Thing which stopped functioning after Spotify unauthorized the Car Thing from interacting with the Spotify App API.

• Product requires physical input on a regular basis: As an example, HP Inc. printer ink has a DRM that forces consumers to exclusively use HP ink, and does not allow third-party cartridges. If HP goes out of business or decides to stop producing their ink cartridges, any printer depending upon it will become bricked, effectively discontinuing the printer even if not explicitly stated.

Further reading

• Spotify Car Thing
• Sonos
• Orphaned technology on wikipedia.org
• Logitech Harmony Link hub
• Nest Revolv Hub
• Amazon Astro
• Neos SmartCam

See also

• Planned obsolescence
• Software degradation and lock-out
• EOL - end-of-life product