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

Prayer Times Incorrect Results for Manual City Entry

  • Incident
  • major
  • Resolved

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.

Affected Services

  • Prayer Times
  • Posted: Feb 11, 2026, 06:00 UTC
  • Resolved: Feb 11, 2026, 12:45 UTC
  • Duration: 6h 45m

Timeline

  1. resolved

    12:45 UTC

    This incident has been resolved. Prayer times, the next-prayer indicator, and the countdown now reflect the entered city's local time regardless of the viewer's location. The fix was verified across seven cities spanning the Americas, Europe, Africa, the Middle East, Asia, and Oceania. Automatic location detection was unaffected throughout. No data was impacted.

  2. monitoring

    11:30 UTC

    A fix has been implemented and we are monitoring the results. The location lookup, the next-prayer calculation, and the countdown timer now use the entered city's local timezone. We are verifying the result across multiple cities and timezone regions.

  3. identified

    07:30 UTC

    The cause has been identified. Two issues affect manual city entry. The location lookup does not reliably resolve some city names to coordinates, and the next-prayer calculation derives its time from the viewer's clock rather than the entered city's local timezone.

  4. investigating

    06:00 UTC

    We are currently investigating reports that the Prayer Times page returns incorrect results when a city and country are entered manually. The next-prayer indicator appears to follow the viewer's local timezone rather than the timezone of the entered city. Automatic location detection is not affected.

Permalink: /incident/26

View all systems