The use case: how Disqus deploys Sentry
Disqus engineers use Sentry as an early warning system for errors after frequent code releases and to prioritize which errors to fix by frequency. Support uses error hashes to route issues to engineering, and the team also uses it for diagnostic logging, auditing and security tracking.
More reported results
Figures published in Sentry’s case study. They are not independently measured by usedby.
While it’s average is only 1-2 events per second in Sentry, at times there are spikes of up to 500 errors a second.
Today, Disqus is the #1 online discussion and commenting service, serving 1.1 billion unique monthly visitors at 2.5 million sites.
In the customer’s words
As we ship code, which we do at least daily, I’m constantly staring at Sentry.Other companies using Sentry
Customers across industries, with public evidence.
Animation Digital NetworkConfirmed
AnthropicConfirmed
ArcadeConfirmed
AtlassianConfirmed
BasetenConfirmed
BitnamiConfirmedGo straight to the source
Based on Sentry’s published case study. We check the public evidence; the results are reported by the vendor.
sentry.io- Last checked
- Nov 13, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 20 Sentry instancesChecked
Printed word for word on the page, near the name of Disqus.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Disqus.
- Disqus uses SentryChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
The entire Disqus engineering team (16 people and counting) use Sentry in one way or another, deploying 20 Sentry instances across a wide range of services.