Home Help Center Knowledge Base Submit Ticket Check Status System Status
Back to System Status

Quran player: turning on English translation could result in silent playback

  • Incident
  • minor
  • Resolved

When the English translation option was turned on for a verse-by-verse reciter, playback could occasionally start in a silent state: the player showed itself as playing, but no audio was heard, and pressing Play again did not recover. Arabic-only listening and all other player features were unaffected, and no data was involved. The cause was a rare condition in the browser's audio engine that left it unable to produce sound while still reporting normal playback. The player now detects this condition within about a second, restarts its audio engine automatically, and resumes from the same position, so listening continues without interruption.

Affected Services

  • Quran Player
  • Posted: Jul 16, 2026, 14:58 UTC
  • Resolved: Jul 16, 2026, 15:12 UTC
  • Duration: 14m

Timeline

  1. resolved

    15:12 UTC

    This incident has been resolved. If the silent condition occurs, the player now recovers on its own within about a second and listening continues from the same position.

  2. monitoring

    15:09 UTC

    A fix has been implemented and we are monitoring the results. The player now detects the silent condition automatically, restarts its audio engine, and resumes from the same position. If the player still appears stuck, reloading the page will pick up the fix.

  3. identified

    15:06 UTC

    The issue has been identified. In a rare condition, the browser's audio engine could enter a state where it reported normal playback while producing no sound. A fix is being implemented.

  4. investigating

    14:58 UTC

    We are currently investigating a report that turning on English translation in the Quran player could leave it silent: the player appeared to be playing, but no audio was heard, and pressing Play again did not recover. Device diagnostics have been captured and are being reviewed.

Permalink: /incident/78

View all systems