{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihucsc7apkzldqbmr6wn3jqn3qg7owasbimengqnomyc7bodnfu2m",
    "uri": "at://did:plc:pkbuqwmk3z3fddp2keropzjk/app.bsky.feed.post/3mlez54inxvj2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiblq3wqbt5gewbqpvfd2dcif7lthr4xh6bn4ijrioze7qdcyvadm4"
    },
    "mimeType": "image/png",
    "size": 3910
  },
  "path": "/incidents/4hpm4454hxtx",
  "publishedAt": "2026-05-08T22:38:17.000Z",
  "site": "https://discordstatus.com",
  "textContent": "May  8, 15:38 PDT\n**Resolved** - All critical functionalities have recovered for all users.\n\nMay  8, 14:47 PDT\n**Update** - Users are able to connect to the platform, and we are working on recovering some features\n\nMay  8, 14:08 PDT\n**Update** - We are continuing to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state\n\nMay  8, 13:19 PDT\n**Identified** - We are beginning to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state\n\nMay  8, 13:16 PDT\n**Monitoring** - We are seeing significant recovery at this time. We are continue to restore ancillary services and we are metering in traffic as users reconnect.\n\nMay  8, 12:56 PDT\n**Update** - We are continuing to work to remediate the issues impacting availability for some Discord users. This is causing impact across our service, including logging in and sending messages.\n\nMay  8, 12:24 PDT\n**Identified** - We have identified the issue. Many users are unable to start their sessions at this time\n\nMay  8, 12:08 PDT\n**Investigating** - We're investgating errors in our API systems.",
  "title": "Increased API Errors",
  "updatedAt": "2026-05-08T22:38:17.000Z"
}