Skip to main content

Is Discogs Down?

No — Discogs is up

Reachable from all 8 checked regions

Average response time: 360ms

Last checked · checks run every 6 hours

Official status page: https://status.discogs.com

Components the vendor reports as affected: CDN Degraded Performance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Discogs fail from enough regions to rule out probe noise.

Discogs uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
384ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 64 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

64-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 36 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 40 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 31 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 31 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 24 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
322ms
DNS 88ms TCP 2ms TLS 10ms TTFB 321ms
lhr
310ms
DNS 82ms TCP 2ms TLS 7ms TTFB 309ms
nrt
532ms
DNS 366ms TCP 1ms TLS 7ms TTFB 532ms
ord
177ms
DNS 44ms TCP 2ms TLS 9ms TTFB 177ms
sin
573ms
DNS 308ms TCP 1ms TLS 10ms TTFB 573ms
sjc
228ms
DNS 120ms TCP 2ms TLS 8ms TTFB 228ms
syd
363ms
DNS 88ms TCP 1ms TLS 6ms TTFB 362ms
yyz
379ms
DNS 239ms TCP 1ms TLS 7ms TTFB 379ms

What Discogs does

Discogs is a crowd-built database of music releases and a marketplace where collectors buy and sell physical records. Its API root currently reports over 19.3 million releases, 10.2 million artists and 2.4 million labels. Sellers run stores against the same catalogue, and record shops and price-tracking tools call the public API, so the database and the marketplace are one dependency.

What an outage looks like

Release, artist and label pages fail to load or return errors, search stops returning results, and Marketplace checkout stalls part-way. Discogs tracks Collection, Wantlist and Shop My Wants as their own tools, so a collector can browse normally while their own lists refuse to open. Sellers see inventory management fail separately from checkout, and the iOS and Android apps are listed apart from the website.

What to do about it

Read status.discogs.com, which separates Website and Login, Marketplace, Discography pages, collector tools and the underlying infrastructure, CDN and search. If checkout failed, check whether the order appeared in your purchase history before paying again, because a stalled checkout and a failed one look identical from the browser. Sellers should confirm inventory changes landed once the Marketplace line returns to normal.

Is it down for everyone, or just you?

If this page says Discogs is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Discogs outage FAQ

Is Discogs down for everyone or just me?
Check status.discogs.com, which breaks the site into Website and Login, Marketplace, Discography, collector tools and infrastructure. Login can fail while release pages serve normally, which looks like an account problem and is not. If every component reads operational, the more likely causes are your network, a browser extension blocking the CDN, or rate limiting if you are calling the API.
Does a Discogs outage affect the Marketplace and my orders?
Marketplace is tracked separately from the database pages, with checkout and inventory management listed apart from each other. An order that was accepted before the fault is recorded on Discogs and does not depend on the site staying up. The risk during an incident is duplicate action: paying twice for a checkout that stalled rather than failed, so check your purchase history first.
Is the Discogs API down too?
The public API and the website share infrastructure, and Discogs lists Infrastructure, CDN and Search as their own components, so an API fault often shows on one of those lines rather than on Website. If your integration fails while the site loads normally, compare against the API root at api.discogs.com, which returns a plain JSON greeting and the current database counts when the service is healthy.
Do the Discogs mobile apps work when the site is down?
Sometimes. The iOS and Android apps are listed as their own components on the status page, separate from the website, so one can be affected while the other is not. Both read from the same catalogue and marketplace, though, so a fault in Infrastructure or Search will usually show up everywhere at once. Check the component lines rather than the top banner.

How we measure this

  • We request Discogs's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Discogs publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Discogs goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required