Disband Status

Live checks across the services that power Disband.

All systems operational

Everything is responding normally.

Platform

Voice gateway

Operational

90-day uptime100%
Response
136ms

Authentication

Operational

90-day uptime100%
Response
16ms

Storage

Operational

90-day uptime100%
Response
117ms

Bot gateway

Operational

90-day uptime100%
Response
122ms

Disband

Website

Operational

90-day uptime100%
Response
51ms

API

Operational

90-day uptime100%
Response
168ms

Web app

Operational

90-day uptime100%
Response
48ms

Docs

Operational

90-day uptime100%
Response
23ms

Static assets

Operational

90-day uptime100%
Response
28ms

Media CDN

Operational

90-day uptime100%
Response
15ms

Status data

Operational

90-day uptime100%
Response
265ms

Active incidents

No active incidents. If something looks wrong, check back shortly.

Announcements

No announcements right now.

Past incidents

Subscribe via RSS
ResolvedIncident3 Nov 2026, 01:00 UTC

Disband wasn't loading

Back to normal after about 6 minutes.

Resolved 3 Nov 2026, 01:06 UTC

ResolvedIncident1 Nov 2026, 21:15 UTC

Disband wasn't loading

Back to normal after about 1401 minutes.

Resolved 2 Nov 2026, 20:36 UTC

ResolvedScheduled maintenance26 Oct 2026, 20:18 UTC

Bots are being reworked

All fixed

Resolved 1 Nov 2026, 19:50 UTC

ResolvedIncident25 Oct 2026, 00:40 UTC

Profile pictures aren't changeable

We have repaired the issue.

Resolved 25 Oct 2026, 19:51 UTC

ResolvedIncident23 Oct 2026, 22:04 UTC

Disband unavailable across all services

Resolved. Disband has been running normally for over two hours since the fix went out, with database load back to its usual level. Summary: an update released at 12:29 pm ET made the web app check for new messages far too often. As more people came online the database was overwhelmed and stopped responding from 4:50 pm to 6:00 pm ET (about 70 minutes). We restarted the database to restore service, then shipped a fix that returns message checking to once a second and stops it speeding up when a connection drops. Sorry for the disruption. We've added a note to that code so this can't quietly happen again.

Resolved 24 Oct 2026, 01:52 UTC

ResolvedIncident20 Oct 2026, 00:01 UTC

Status data is down

Recovered after 23 minutes.

Resolved 20 Oct 2026, 00:25 UTC

ResolvedIncident20 Oct 2026, 00:01 UTC

Status data is down

Recovered after 24 minutes.

Resolved 20 Oct 2026, 00:26 UTC

ResolvedIncident20 Oct 2026, 00:01 UTC

Authentication is down

Recovered after 23 minutes.

Resolved 20 Oct 2026, 00:25 UTC

Checks run automatically every minute. Seeing a problem that isn't listed? Report a bug.