Locally logo

Is Locally Down?

SaaSLive status, outages, and incident history

No. Locally is up right now.

Every monitored Locally system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Locally breaks

Locally is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Locally status page
How we know: the official Locally status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Locally Status Summary

As of 04:25 UTC on 9 November 2026, Locally is operational. PulsAPI checked Locally's official status page and found 12 of 12 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Locally, counting degraded performance as up. The latest incident, "Increased latency on search endpoints", was on Aug 31, 2026 and lasted 1h 45m.

Cite as: PulsAPI, “Locally status”, checked 9 November 2026, 04:25 UTC. https://www.pulsapi.com/services/locally

Locally Component Status

The main Locally systems on this page. All 12 are operational right now.

12operational
API · v1
Operational
API · v2 / Headless, Cart, ShopSense, and Marketing
Operational
Brand & Retailer Analytics
Operational

9 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Buy it Locally / Carts / Transactions, Dealer Feed Ingestion, Inventory Ingestion, Locally "Pages", Locally.com, Product Locators, Same-day Delivery, Store Locators, Storefronts.

See all of them free

Component statuses may change independently during partial outages.

Recent Locally Outages & Incidents

Incident history from the official Locally status page, including resolution updates.

Increased latency on search endpointsResolved Aug 31, 2026 · 1h 45mResolved

This incident has been resolved. --- [2026-08-31T08:07:12.023Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-08-31T07:31:11.507Z] (identified) We are continuing to work on a fix for this issue. --- [2026-08-31T07:12:29.571Z] (identified) We have identified the issue and are working on a fix. In the meantime some customers using Storefronts sites and other product search surfaces continue to experience degraded performance. --- [2026-08-31T07:02:15.776Z] (investigating) We are continuing to investigate this issue. --- [2026-08-31T06:28:41.023Z] (investigating) We are currently investigating this issue.

Problems with data ingestion and reportingResolved Aug 26, 2026 · 13 minResolved

This incident has been resolved. --- [2026-08-26T20:40:24.538Z] (investigating) We are currently investigating this issue.

Currently experiencing a search service outage for a small number of clients due to an abnormal amount of traffic.Resolved Aug 24, 2026 · 55 minResolved

This incident has been resolved. --- [2026-08-24T15:40:53.344Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-08-24T15:14:55.738Z] (identified) The issue has been identified and a fix is being implemented.

Locally Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Locally incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history1 day observed
Nov 9100.00% averageNov 9

Live Locally Outage Reports

Problems reported by engineers using Locally. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Locally problems reported yet.

Something wrong with Locally on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Locally

Locally posts its status at status.lcly.co. The page covers 12 components, among them Store Locators, Product Locators and Buy it Locally / Carts / Transactions. Past incidents and uptime for Locally stay on this page, which helps when you want to know how often it has trouble.

Over the past 30 days, PulsAPI has measured Locally uptime at 100.00%. Response times, incident history, and SLA tracking for Locally are available on the PulsAPI dashboard.

Locally Status FAQ

Is Locally down right now?

The verdict at the top of this page comes from the latest poll of the official Locally status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Locally is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Locally recovers.

How do I check Locally uptime history?

PulsAPI tracks Locally uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Locally changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Locally outages?

PulsAPI reads the official Locally status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Locally components?

Yes. PulsAPI monitors 12 individual Locally components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Locally goes down?

Yes. Create a free account and subscribe to Locally: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Locally to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Locally problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Locally?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Locally plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Locally with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services