Prayer Times - Incorrect Hijri Date Displayed

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.

• Posted: Apr 1, 2026, 10:30 UTC
• Resolved: Apr 1, 2026, 10:43 UTC
• Duration: 13m

Timeline

1. resolved

   10:43 UTC

   Confirmed resolved. The prayer times page is displaying the correct Hijri date across all tested locations. The reduced cache TTL will prevent this issue from recurring at future date boundaries. We apologize for any inconvenience, particularly for users relying on the Hijri date for time-sensitive worship such as the white days of fasting (Ayyam al-Beed).

2. monitoring

   10:40 UTC

   Fix deployed. The API worker cache TTL for prayer timings has been reduced from 24 hours to 1 hour. All stale cache entries have been purged from both the Cloudflare edge cache and the Drupal application cache. The prayer times page now correctly displays Shawwal 13, 1447 AH. Monitoring to confirm the fix holds across all regions.

3. identified

   10:35 UTC

   Root cause identified. The API proxy worker at api.gablvm.org was caching prayer timings responses for 24 hours. A request made on March 31 (Shawwal 12) was still being served on April 1 (Shawwal 13) due to the stale cache. This affected any user viewing the prayer times page during this window.

4. investigating

   10:30 UTC

   We received a report that the prayer times page is displaying Shawwal 12 instead of Shawwal 13. The Hijri calendar page correctly shows the 13th. Our team is investigating the discrepancy between the two pages.

Permalink: /incident/42