Locally incident

Infrastructure issues

Minor Resolved View vendor source →

Locally experienced a minor incident on February 24, 2025 affecting Store Locators and Product Locators and 1 more component, lasting 3h 11m. The incident has been resolved; the full update timeline is below.

Started
Feb 24, 2025, 01:10 PM UTC
Resolved
Feb 24, 2025, 04:21 PM UTC
Duration
3h 11m
Detected by Pingoru
Feb 24, 2025, 01:10 PM UTC

Affected components

Store LocatorsProduct LocatorsBuy it Locally / Carts / TransactionsLocally.comLocally "Pages"Hosted Domains & Sites / Locally Landing PagesSame-day DeliveryDealer Feed IngestionAPI (v1)API (v2 / Headless, Cart, ShopSense, and Marketing)

Update timeline

  1. investigating Feb 24, 2025, 01:10 PM UTC

    We are currently investigating infrastructure issues which are causing problems with dealer feed/data ingestion and management. Please be patient as we work through this.

  2. investigating Feb 24, 2025, 01:24 PM UTC

    We are continuing to investigate the issue. Thanks for your patience!

  3. identified Feb 24, 2025, 01:44 PM UTC

    We have identified the cause of the issue but are working to restore services to 100% efficiency. We will update the status every 15 minutes until resolved. There is no ETA at this time. Thanks for your patience.

  4. identified Feb 24, 2025, 02:06 PM UTC

    We are continuing to work on a fix. Until further notice, all automatically ingested or manually managed dealer list data will not be reflected on Locally web properties. Additionally, all ingested inventory data will not be reflected on any Locally web properties. Only (dealer and inventory) data that was ingested prior to 2 hours ago will be displayed.

  5. identified Feb 24, 2025, 02:15 PM UTC

    We are continuing to work on a fix for this issue.

  6. identified Feb 24, 2025, 02:48 PM UTC

    We are still working to solve the dealer and inventory data ingestion issue. We will post another update within the next 90 minutes.

  7. monitoring Feb 24, 2025, 04:03 PM UTC

    A fix has been implemented. We expect all data to be back to current status within 90 minutes.

  8. resolved Feb 24, 2025, 04:21 PM UTC

    This incident has been resolved.