PreMiD incident

Activities not displaying in Discord

Critical Resolved View vendor source →

PreMiD experienced a critical incident on April 8, 2025 affecting Extension, lasting 17d 6h. The incident has been resolved; the full update timeline is below.

Started
Apr 08, 2025, 09:04 AM UTC
Resolved
Apr 25, 2025, 03:07 PM UTC
Duration
17d 6h
Detected by Pingoru
Apr 08, 2025, 09:04 AM UTC

Affected components

Extension

Update timeline

  1. identified Apr 08, 2025, 09:04 AM UTC

    We are aware of an issue where activities are not displaying in Discord. We’ve confirmed that activity data is still being sent correctly and received by Discord. However, it’s currently not being displayed as expected. This issue is on Discord’s end. We’ve already notified them, and they are looking into it. We kindly ask for your patience while Discord investigates and resolves the issue. Thank you for your understanding!

  2. monitoring Apr 08, 2025, 04:49 PM UTC

    Activity display appears to be recovering. We have started to see activities being displayed again, although still at a degraded rate. While Discord has not yet confirmed any fix on their end, it looks like something may have changed. We will continue monitoring the situation and keep you informed. Thank you for your continued patience and support!

  3. monitoring Apr 12, 2025, 09:15 AM UTC

    Activities appear to be fully operational again. We’re seeing activity display functioning as expected across the board. However, since we have not yet received any official confirmation from Discord, we will continue to keep this incident marked as active until we hear back. Thanks for sticking with us through this!

  4. monitoring Apr 19, 2025, 06:16 PM UTC

    Discord reports ongoing degraded performance Discord has informed us that they are still seeing degraded performance on their end. Activities should still show, but there may be a short delay before they appear. We’ll share another update as soon as we know more. Thanks again for your patience and understanding!

  5. resolved Apr 25, 2025, 03:07 PM UTC

    This incident has been resolved.