LOKE Outage History

LOKE is up right now

LOKE had 5 outages in the last 2 years totaling 8h 13m of downtime — averaging 0.2 incidents per month.

There were 5 LOKE outages since May 7, 2026 totaling 8h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.loke.global

Minor August 3, 2026

Incident Notice - Orders Stuck on Pending

Detected by Pingoru
Aug 03, 2026, 11:49 PM UTC
Resolved
Aug 04, 2026, 12:24 AM UTC
Duration
34m
Affected: Back OfficeCustomer ApplicationsTerminalAPIIntegrationsSupportSupport (Australia / New Zealand)Support (United Kingdom)Support (Singapore)Support (United States)
Timeline · 9 updates

Read the full incident report →

Major July 24, 2026

Website Access Issues

Detected by Pingoru
Jul 24, 2026, 10:25 PM UTC
Resolved
Jul 25, 2026, 12:32 AM UTC
Duration
2h 6m
Affected: Back OfficeCustomer ApplicationsTerminalAPIIntegrationsSupportSupport (Australia / New Zealand)Support (United Kingdom)Support (Singapore)Support (United States)
Timeline · 11 updates

Read the full incident report →

Minor May 7, 2026

Ordering Issue – Store Locations Unavailable

Detected by Pingoru
May 07, 2026, 01:28 PM UTC
Resolved
May 07, 2026, 03:00 PM UTC
Duration
1h 31m
Affected: Customer ApplicationsSupport (United States)
Timeline · 3 updates
  1. investigating May 07, 2026, 01:28 PM UTC

    We are currently investigating an issue affecting multiple store locations where customers are unable to place orders and run into an error saying the store location is not available for ordering.

  2. investigating May 07, 2026, 01:48 PM UTC

    Our engineers are actively working to identify the cause and restore normal functionality as quickly as possible. We appreciate your patience and will continue to share updates as more information becomes available.

  3. identified May 07, 2026, 02:03 PM UTC

    Our engineers have identified the issue and are currently implementing a fix. We expect services to return to normal shortly. Thank you for your patience while we work to resolve this.

Read the full incident report →