Incident History

On the morning of September 25, 2026, the automatic update process for gablvm.org applied a new release of a page rendering library that turned out to break every page. The process detected this within seconds through its own test requests and restored the previous version each time, in about thirty seconds, but it repeated the attempt at 8:30, 8:45, 9:00 and 9:15 AM Central before it was stopped. Our server logs show that every error response in those windows went to the update process itself, and none to a visitor, a search engine or the GABLVM app. No data was affected. The upstream fix was released on September 26, and the site now runs the updated library normally. The update process was also changed so a version that fails its test is not tried again.

Sep 25, 2026 minor

Planned work on the delivery of Quran audio on Thursday 17 September 2026, between 5:00 PM and 5:30 PM Central Time, which is 22:00 to 22:30 UTC. During this window, playing or downloading Quran audio on gablvm.org or in the GABLVM iOS app may briefly fail or need to be started again. Prayer times, the calendar, community events and the rest of the site are unaffected, and no data is affected. The work itself is expected to take only a few minutes of the window, and this notice will be updated when it begins and again when it is complete.

Sep 16, 2026 to Sep 17, 2026 maintenance

In the Quran player on gablvm.org and in the GABLVM iOS app, available to testers through TestFlight, playing a surah verse by verse with the English translation switched on could cut short the end of some verses for the reciter Abdurrahman As-Sudais before the translation started, most noticeably in the short surahs. During the investigation we also found that the English translation clips carried a faint background tone in the pause before the narrator speaks. Chapter playback, other reciters, and playback without the translation were unaffected, and no data was affected. Both issues trace to how the source recordings were cut into per-verse clips rather than to a failure of our systems. The player is being changed to keep together the verses this reciter recites in one breath, and the translation clips are being re-cut with the tone removed. These issues have been present since verse-by-verse English playback was introduced.

Sep 15, 2026 to Sep 16, 2026 minor

In the GABLVM iOS app, available to testers through TestFlight, downloading a surah together with its English translation could stop partway through with a message that the audio server returned an error, after roughly a third of the translation files had been saved. Streaming playback, downloads without the translation, and the Quran player on gablvm.org were unaffected, and no data was affected. The cause was a request limit on our audio delivery service that also counted the app's bulk translation download; the limit has been adjusted so these downloads complete, and a download that failed can simply be started again. The failure was intermittent and may have occurred at any time since translation downloads were introduced.

Sep 12, 2026 minor

On forms across gablvm.org, including the contact form, screen readers could announce a required field as containing invalid data the moment a page loaded, before the visitor had entered anything. VoiceOver on iPhone and Mac was the most affected, hearing invalid data on fields that were simply empty. Every form remained fully usable throughout: options could be selected, steps advanced, and submissions completed normally, and no data was affected. The way required fields are marked has been reworked so screen readers now announce them as required rather than invalid. The behavior was likely present since the contact form launched in early July.

Aug 31, 2026 minor

Since the Mute control was added to the Quran player, it was displayed at the far left of the playback toolbar while keyboard focus and screen reader reading order reached it last, after Skip forward 30 seconds. Sighted keyboard users saw Mute first but had to Tab past every other control to reach it, and people using a screen reader with sight heard the controls in a different order from the one on screen. Every control worked normally throughout, playback was unaffected, and no data was affected. The toolbar now displays the controls in the same order they are reached by keyboard and screen reader: Skip back 30, Skip back 10, Play or Pause, Skip forward 10, Skip forward 30, Mute.

Aug 29, 2026 to Aug 30, 2026 minor

Since June 26, the Quran player's single-key keyboard shortcuts, such as K to play or pause and J and L to skip backward and forward, did not respond while keyboard focus was on the player's control bar. Because the control bar is where keyboard focus naturally rests during listening, keyboard and screen reader users on all devices were affected. The on-screen buttons, arrow-key navigation between controls, and playback itself worked normally throughout, and no data was affected. The shortcuts were silenced by a side effect of a June 26 accessibility improvement made for Windows screen reader users. A listener report on August 16 led us to the cause, and a fix was deployed the same day restoring the shortcuts while keeping the improved control bar.

Aug 16, 2026 minor

During three brief windows overnight, visitors to gablvm.org may have received a stale cached response from our content delivery layer instead of the requested page. Each window lasted about ten minutes or less and cleared automatically, and most visitors were unaffected. A fault in our automated cache recovery process was identified and corrected the same morning.

Aug 15, 2026 minor

For roughly 46 minutes on August 14 (from about 21:29 to 22:15 UTC), a portion of visitors who were not signed in were shown a repeating loading page reading "One moment, please" instead of the requested page. The site itself remained fully operational throughout, signed-in visitors were unaffected, and no data was involved; the loading page came from a stale cached response in our content delivery layer. The cache was cleared to restore normal access immediately, and we have since shortened how long pages may be cached and added automated monitoring that detects and clears this condition within minutes if it ever recurs.

Aug 14, 2026 minor

Screen reader users on some devices may not hear the question above a set of multiple-choice answer options announced before the options themselves on gablvm.org forms, including the community research form. All questions, options, and form submissions continue to work normally, and the question text remains reachable by moving backward one step from the options. An initial fix was deployed on August 7 and did not fully resolve the behavior; a revised fix is in progress.

Aug 6, 2026 to Aug 7, 2026 minor

At locations far enough north that the last prayer of the night falls after midnight, which in the summer months includes much of northern Europe, Iceland, Canada and the northern United States, the Prayer Times page could name the wrong upcoming prayer. Just after midnight the page could point to the following morning's Fajr while a prayer was in fact only minutes away, and in the evening the countdown to the last prayer of the night could announce that its time had arrived early and then stop counting down. Separately, for up to an hour after local midnight the page could still show the previous day's Islamic date. The listed prayer times themselves were correct throughout, visitors at other latitudes were unaffected, and no account data was involved. All three have been corrected and the page has been checked against several northern locations.

Jul 24, 2026 minor

With English translation turned on, pausing the Quran player while an English translation was being read and then resuming could skip the remainder of that translation and continue at the next verse in Arabic. Arabic-only listening, seeking, and all other player features were unaffected, and no data was involved. The cause was a recovery check that runs after resuming playback: it could misread healthy translation playback as stalled and restart playback at the following verse. The check now recognizes translation playback correctly, so pausing and resuming during a translation continues exactly where it left off.

Jul 17, 2026 minor

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.

Jul 16, 2026 minor

Some signed-in listeners found that when they used Continue reading to pick up where they left off, the player did not remember the reciter they had been listening to, and playback could start again from the beginning of the surah instead of the saved verse. A separate report described the two-finger control for pausing playback not behaving as expected on some devices. Most listening worked normally and no account data was affected. Both behaviors have been corrected and confirmed: Continue reading now restores the saved reciter and resumes at the saved verse, and the two-finger pause control holds as expected. A Clear option was also added so listeners can empty their Continue reading list at any time.

Jul 16, 2026 minor

between 23:05 UTC on July 11 and 11:46 UTC on July 12, visitors to gablvm.org were shown our maintenance page instead of the website. A routine software update the previous evening did not finish cleanly and left the site in maintenance mode. For much of that window our content delivery network continued to serve saved copies of pages, so many visitors still saw the site normally, but direct visits increasingly reached the maintenance page instead. No data was lost and visitor security was never affected; the site content itself was intact throughout. Maintenance mode has been switched off, cached copies have been refreshed, and the site has been verified healthy. We are also tightening our monitoring so a stuck maintenance page is caught much sooner in the future.

Jul 11, 2026 to Jul 12, 2026 major

Shortly after the new country and region menus were released on the Prayer Times page, choosing a country, or a country and a region, without typing a city worked for that visit but was not remembered: the next visit fell back to the default location. The location label could also show a stray leading comma when no city was chosen, which screen readers read aloud. Prayer times themselves were always calculated correctly for the chosen place, and no personal data was involved. Both issues were fixed and verified the same afternoon, about half an hour after the release.

Jul 7, 2026 minor

For a period after the after-each-verse English translation was extended to more reciters in the Quran player, the spoken English translation did not play for a small number of reciters, even though the option appeared available for them. Arabic recitation played normally throughout. A listener reported it. The cause was identified and corrected, and the English translation now plays for these reciters as well. Other reciters were unaffected and no personal data was involved.

Jul 6, 2026 minor

Navigation links intended for site staff were visible to all visitors on the Contact page. The links did not expose any information: the pages behind them remained protected throughout and no form submissions or personal data were accessible. The issue has been resolved and the links no longer appear.

Jul 4, 2026 minor

On the Quran Player page, several controls stopped responding: enabling English translation did not add the translation audio, playback no longer continued automatically to the next surah when that option was selected, and the previous and next surah buttons did not respond. Reciter selection and standard Arabic recitation continued to work normally, and no personal data was affected. The issue has been resolved and the affected controls now respond as expected.

Jul 3, 2026 minor

The Prayer Times page remembers a visitor's location between visits, and an issue in how that location was stored meant it could continue showing a location the visitor had since left. Prayer times were always calculated correctly for the location shown and no data was affected, and most visitors were unaffected. The issue has been resolved and the location handling redesigned so a saved location now updates when a visitor moves.

Jul 3, 2026 minor

On July 1 we upgraded gablvm.org to Drupal 11.4, the newest release of the platform the website runs on. During the upgrade the site was briefly unavailable: for roughly twelve minutes visitors saw an error page and then a maintenance page instead of the site. Two upgrade steps did not complete in the expected order, which we identified and finished within minutes; the site was then restored, every tool was verified working, and the upgrade completed successfully. No data was affected, and nothing changes in how the site or its tools work. The new platform release makes pages faster for the server to build, which keeps the site quick as it grows.

Jul 1, 2026 major

For a period, the Quran player's playback-speed control did not respond when it was changed while audio was playing, on all devices; the chosen speed only took effect after pausing and resuming or moving to the next chapter. Setting the speed before starting playback worked normally, and no data was affected. A listener reported it. Initial improvements to speed handling did not resolve it, and a deeper investigation found the underlying cause: the speed control was not being connected to the player when the page loaded, so changing it had no effect. That has been corrected and confirmed working.

Jul 1, 2026 minor

For a period, with the English audio translation turned on, the Quran player's Mute button and the keyboard speed shortcuts did not take effect, and turning the translation on at the very start of a chapter could move playback to the wrong verse. The recitation itself kept playing and no data was affected. These were found in a routine review of the player rather than reported, and each was fixed; mute and the speed controls now work with the translation on, and enabling it at the start of a chapter keeps your place. If you still see the older behavior, reload the page once.

Jul 1, 2026 minor

Some visitors saw an incorrect next prayer on the Prayer Times page, or a stale date on the Islamic Calendar, with different devices showing different values for the same location. The cause was a caching issue: these time-sensitive values were calculated when the page was generated and then cached, so they could freeze and be served out of date. Both pages now keep these values current on every visit.

Jun 25, 2026 major

When using the Quran player, turning the English translation audio on or off during playback could move the position forward, sometimes skipping a verse, instead of continuing from the same place. This was limited to the English-translation toggle on verse-by-verse reciters; ordinary Quran playback was unaffected and no audio was ever wrong. The issue has been fixed and verified on the live player.

Jun 22, 2026 minor

During a routine review of the Quran tools we identified and corrected a few minor issues. The audio reader could fail to show an error message when speech could not start on a device, and a linked Quran.com account could remain shown as connected after its link had expired. These were edge cases affecting a small number of situations; the tools remained available throughout, and no data was affected. All items have been fixed and verified.

Jun 20, 2026 to Jun 21, 2026 minor

On iPhone, switching headphones during Quran playback could briefly interrupt the audio while the device reconfigured its audio output. The recitation always recovered on its own and no audio or saved data was lost, but because it affected a core feature we treated it as a genuine playback-quality issue. After investigation we identified the cause in how iOS handles audio route changes and resolved it by changing how Arabic recitation is delivered so the device manages the transition natively. A brief, self-recovering transition now remains only in the English translation mode.

Jun 18, 2026 minor

During an internal accessibility and reliability review, we found and fixed several minor issues across a few of our tools, most of them affecting screen-reader users in specific situations. The tools kept working normally throughout and no data was affected, and most visitors saw no difference. The issues have been resolved.

Jun 16, 2026 to Jun 17, 2026 minor

For a period, the Quran player could play the English audio translation out of step with the recited verse, pause briefly between verses, lose your place when seeking, and stop playing when the device was locked, in the background, or after a headphone change. Most listening worked normally throughout and no data was affected. These came up while we rebuilt the player on a new audio engine, and each one was identified and fixed; the player now plays seamlessly, keeps the translation in sync, seeks reliably including while paused, and continues in the background. This was a major rebuild of the site's flagship feature, and the work is complete.

Jun 15, 2026 to Jun 16, 2026 major

The website homepage intermittently returned an error response to some requests due to an issue in our caching layer. The underlying site remained healthy throughout and most visitors were unaffected. The issue has been resolved and a safeguard added to prevent recurrence.

Jun 2, 2026 minor

The account features in the Quran Player that sync with your Quran.com account, your bookmarks, notes, reading streaks, today's reading plan, and the My Account dashboard, were unavailable from May 7 to May 8, 2026. These features are powered by Quran.com, and the cause was an outage in the Quran.com service they connect to. The rest of the Quran Player, including audio playback for all 20 reciters, English audio, reciter selection, verse navigation, and search, kept working normally throughout.

May 7, 2026 to May 9, 2026 minor

On 23 April 2026, screen reader users on iOS Safari reported that the location permission prompt on the Prayer Times page was not completing successfully. Investigation identified three browser-compatibility issues with iOS Safari's Permissions and Dialog APIs, each one masking the next. All three were resolved in releases 2.0.2, 2.0.3, and 2.0.4 of the gablvm_core module, with additional UX and accessibility refinements shipping through release 2.0.8. A subsequent user report was traced to an iOS Safari Website Setting that silently grants location access without showing a system prompt; in that case the application was functioning as designed, but the outcome was not visible to the user. Users who wish to restore the native iOS Safari prompt can change their Safari Website Settings for gablvm.org from 'Allow' to 'Ask'. The application's in-app acceptance flag can be reset at any time by visiting /prayer-times?resetLocation=1. All fixes are live on both origin servers.

Apr 23, 2026 minor

At 00:00:01 UTC on 2026-04-20, the external status-page probe detected that status.gablvm.org returned a 200 response that did not contain the expected v3 template marker. The response cleared on the next probe cycle 10 minutes later with no intervention. No deploy happened in that window (the live Cloudflare Worker version did not change). Investigation identified the most likely cause as a transient Cloudflare edge bot-fight challenge triggered by the probe's fixed-IP 10-minute pattern. Mitigation applied: probe now sends an identifiable User-Agent and the server IP is whitelisted in Cloudflare's firewall. Site was never unreachable to real users during this window.

Apr 20, 2026 minor

The status page briefly displayed 0% uptime for the Support Portal and Status Page services themselves, while both services were actually operational. This was a display regression caused by an older version of the status page template remaining active on the edge. No actual service was affected, and no data was lost. Only the displayed uptime percentages for those two services were incorrect. The fix restored the correct display behavior, which excludes services whose uptime is manually tracked rather than automatically monitored.

Apr 19, 2026 minor

A client-side bug could cause the Quran Player's seek bar and skip buttons to stop responding if the audio stream was interrupted mid-playback and the recovery path encountered a network error. Users experiencing this could recover by reloading the page. The issue has been identified and resolved. The player now preserves playback state across network interruptions so the controls remain responsive, and a clear retry message is shown if audio fails to load. No data loss, no security impact.

Apr 17, 2026 minor

Two unrelated fixes shipped together in this update. First, the Support Portal and Status Page services were incorrectly showing 0% uptime over the last 90 days because an older version of the monitoring worker was writing health check records for services that are managed manually. A fix for this exact issue was made yesterday but the deployment bundle was stale and did not include the correction. The monitoring worker has now been redeployed with the correct code, the inaccurate records have been cleaned up, and the 90 day uptime display has been restored to an accurate value. Second, on small mobile viewports the cookie consent banner could take up more than 80 percent of the screen and cover form fields on the Contact Us and Newsletter pages of gablvm.org, which made it difficult for mobile visitors to reach the full form before accepting or declining cookies. The banner has been redesigned to be compact on mobile, its height is now capped, and content above it is automatically adjusted so every form field remains reachable. The site footer has also been reorganized on tablet and desktop into a two column layout, reducing its overall height by roughly 20 percent on short content pages. No data or functionality was affected by either fix.

Apr 12, 2026 maintenance

The main website and API were unreachable for approximately 43 minutes this morning due to a fault affecting the origin server. Service was restored after a restart, and a permanent fix has since been applied at the infrastructure layer to prevent the issue from recurring.

Apr 11, 2026 major

Complete visual redesign of gablvm.org inspired by the tradition of illuminated Islamic manuscripts, delivered as release v2.0.1. The site moved from a stock Olivero template look to a warm ivory background with deep forest green and antique gold accents, Fraunces serif headings throughout, and an editorial layout style across every public page. The release was shipped in four phases on 2026-04-10: initial design deployment, polish sweep to fix issues found during the page-by-page review, screen reader accessibility fixes after VoiceOver testing surfaced duplicate-announcement bugs from CSS pseudo-element content, and a desktop layout fix after testing on wide viewports revealed an empty social bar region stealing 90 pixels of space. Throughout the release the site maintained its zero WCAG 2.2 AA violation record, and every change was verified against AAA contrast thresholds before shipping. The eu-cookie-compliance banner was also restyled to match the new aesthetic. No user-facing downtime during the change.

Apr 10, 2026 maintenance

The status page displayed 0% uptime for the Support Portal and Status Page services. All services were operating normally throughout this period. The issue was caused by the health monitoring system incorrectly recording health check results for manually-managed services, which do not require automated health checks. This resulted in inaccurate uptime data being displayed to visitors. The monitoring system has been corrected and the erroneous data has been removed.

Apr 4, 2026 to Apr 5, 2026 minor

The prayer times page displayed Shawwal 12 instead of the correct Shawwal 13 due to a stale 24-hour API cache. This could have impacted users planning to observe the white days of fasting (Ayyam al-Beed: 13th, 14th, 15th of each lunar month). The root cause was the API proxy caching prayer data for 24 hours, which meant date transitions were delayed. The cache TTL has been reduced to 1 hour to prevent recurrence.

Apr 1, 2026 minor

All GABLVM services experienced an unplanned disruption due to a hosting infrastructure issue. The root cause has been identified and resolved.

Mar 29, 2026 to Mar 30, 2026 major

All GABLVM services experienced an unplanned disruption lasting approximately 11 hours due to a hosting infrastructure issue. The root cause has been identified and resolved.

Mar 22, 2026 to Apr 15, 2026 major

Routine security updates were applied and verified. All services are operating normally.

Mar 22, 2026 maintenance minor

The events page continued to display Upcoming status for approximately 5 minutes after the YouTube livestream went live for Ramadan Night 30. This was caused by two issues: the YouTube API proxy was caching the Upcoming response, and the YouTube sync was overwriting the Ongoing status set by the scheduled time check. Both issues have been resolved.

Mar 19, 2026 minor

The English audio translation feature on the Quran Player was not playing. Listeners could enable the option, but no English audio played after the Arabic recitation; Arabic playback and the rest of the website were unaffected and no data was affected. A client-side initialization issue was identified and fixed, and English translation playback has been verified across all supported reciters.

Mar 9, 2026 to Mar 10, 2026 major

Two issues were identified with the prayer times page: (1) When the page transitioned to showing the following day's prayer schedule after Isha, the underlying time data used for next-prayer calculations was not updated, causing the wrong prayer to be highlighted. (2) Drupal's page cache was serving stale prayer time data for up to one hour, which could display incorrect times, the wrong Hijri date, and an inaccurate next prayer indicator. Both issues have been resolved. The prayer times page now always returns fresh data on each request.

Mar 8, 2026 to Mar 9, 2026 major

Prayer times displayed the next day's schedule for visitors in timezones behind UTC, across the Americas and the Pacific. The server requested times from the prayer API using the UTC date, but during evening hours in the United States the UTC date has already advanced to the next day. The result was a schedule shifted by about an hour, for example daylight time figures shown to a viewer still on standard time. The fix stops sending an explicit date, so the prayer API determines the correct local date from the viewer's coordinates.

Mar 8, 2026 major

Planned migration of all GABLVM services to an upgraded hosting environment with improved performance, reliability, and security. All services were migrated and verified with zero data loss and no user-facing downtime.

Mar 8, 2026 to Mar 13, 2026 maintenance minor

On February 28, 2026, we migrated our email delivery to a new infrastructure provider to improve cost efficiency and long-term scalability. During a window on March 1 to 2, 2026, the new provider experienced an outbound delivery issue caused by a false positive in their spam protection system, which temporarily blocked some legitimate messages. Ticket notifications, account registration, password resets, and newsletter delivery may have been affected. The provider resolved the issue on March 2, and all email delivery is operating normally.

Feb 28, 2026 to Mar 2, 2026 minor

A security middleware update introduced a service configuration error that caused error pages for any request not served from edge cache. Primarily affected the Islamic Calendar page and other pages with unique query parameters that bypass cache. Root cause identified and fixed within 33 minutes. Edge cache purged to clear any cached error pages.

Feb 22, 2026 major

Prayer times API calls are now routed through our edge proxy at api.gablvm.org with Cloudflare edge caching. This reduces latency from 1-3 seconds to near-instant on cache hits worldwide. The migration was completed ahead of schedule during Ramadan 2026. Additionally, a timezone bug was identified and fixed where the server used UTC date instead of the user's local date, causing prayer times to show the wrong day's times for users in timezones behind UTC.

Feb 14, 2026 to Mar 8, 2026 maintenance minor

Changing the calculation method for a city with a non-Latin name, such as Kathmandu, Beijing, Cairo, or Moscow, could cause prayer times to fail. The location lookup returned city names in their local script when no language preference was set, and those names failed on re-lookup. The issue has been resolved and a safeguard added to request Latin-script results consistently.

Feb 11, 2026 minor

Visitors who entered a city and country manually on the Prayer Times page could receive incorrect results. The location lookup did not reliably resolve city names to coordinates, and the next-prayer calculation used the viewer's local timezone instead of the entered city's timezone. Both issues have been resolved and verified across multiple global regions. Automatic location detection was not affected.

Feb 11, 2026 major

Emails sent to support@gablvm.org were being received by our email routing service but were not being processed into support tickets. The email processing system was failing silently due to an internal configuration mismatch.

Feb 8, 2026 major

Scheduled infrastructure update in preparation for Ramadan 2026. No downtime was expected or experienced.

Feb 7, 2026 to Feb 14, 2026 maintenance minor

We migrated Quran Player audio files to a global content delivery network (CDN) to improve loading times and playback reliability worldwide.

Jan 25, 2026 maintenance minor

Scheduled maintenance was performed on our security monitoring systems to improve threat detection accuracy.

Jan 20, 2026 maintenance

Our automated backup system encountered a temporary storage issue. Backups have been optimized and are now running successfully.

Jan 17, 2026 to Jan 19, 2026 major

The Islamic Calendar and Prayer Times were not automatically updating after midnight. Users may have seen the previous day's date until refreshing. This has been fixed.

Jan 4, 2026 minor

The Islamic Events dropdown was defaulting to 2025 instead of 2026 when viewing the calendar in January 2026. This display issue has been corrected.

Jan 2, 2026 to Jan 4, 2026 minor

Some users experienced incomplete Islamic events when viewing the full year calendar. The issue was related to how event data was being retrieved and has been resolved.

Jan 1, 2026 to Jan 9, 2026 major

Screen reader users experienced an issue where navigation items were being announced incorrectly. This accessibility issue affected some users and has been fixed to ensure proper navigation announcements.

Dec 28, 2025 major

Screen readers were announcing additional descriptive text along with menu item names, causing verbosity for assistive technology users. Menu items now announce cleanly.

Dec 28, 2025 minor

The "Skip to main content" accessibility feature required two clicks to work properly. This has been fixed for keyboard and screen reader users.

Dec 27, 2025 minor

Automated backups were running at inconsistent times each day. The scheduling has been corrected to run at a fixed time.

Dec 25, 2025 to Dec 31, 2025 minor

Enhanced our security monitoring capabilities to better detect and respond to potential threats.

Dec 23, 2025 minor

Updated system components for improved compatibility and performance. No user-facing impact.

Dec 23, 2025 minor

Automated scheduled tasks were temporarily not executing. The issue has been identified and resolved, and all scheduled operations are running normally.

Dec 20, 2025 major

The "Skip to main content" link was landing on the wrong page element. This accessibility feature now correctly takes users to the main page content.

Dec 12, 2025 minor

The website logo was temporarily displaying as text instead of the image. This visual issue has been corrected.

Dec 12, 2025 minor

Some system-generated emails contained incorrect website links. Email links now correctly point to the proper website address.

Dec 11, 2025 minor

Some Quran reciters' audio was not playing correctly. The audio playback system has been updated to support all available reciters.

Dec 6, 2025 major

The Quran Player was occasionally skipping surahs during continuous playback. The playback navigation has been fixed for seamless listening.

Dec 6, 2025 major