Locally status updated
Locally is working normally
This chart shows the number of user-reported issues for Locally service health over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem.
See where users report Locally is down. The map shows recent Locally outages from around the world.
Locally Outage MapIn the last 90 days, Locally had 6 incidents (2 major outages and 4 minor incidents) with a median duration of 4 hours 25 minutes.
Incidents
Major Outages
Minor Incidents
Median Resolution
Check Locally status history below. IsDown detects when Locally is down, tracking both official outages and user-reported issues.
| Title | Started At | Duration |
|---|---|---|
|
The issue has been identified and a fix is being implemented.
|
Jan 23, 2026 at 11:49 AM UTC
|
about 9 hours |
|
We are currently investigating this issue.
|
Jan 22, 2026 at 09:21 PM UTC
|
about 23 hours |
|
The issue has been identified and a fix is being implemented.
|
Jan 22, 2026 at 11:13 AM UTC
|
about 7 hours |
|
The issue has been identified and a fix is being implemented.
|
Dec 24, 2025 at 04:29 PM UTC
|
about 2 hours |
|
We are currently investigating this issue.
|
Dec 08, 2025 at 03:58 PM UTC
|
about 2 hours |
|
We are currently investigating this issue.
|
Nov 07, 2025 at 07:22 PM UTC
|
about 1 hour |
|
We are investigating a site-wide issue. Thanks for your patience while we investigate.
|
Oct 17, 2025 at 09:56 PM UTC
|
about 1 hour |
|
We are currently investigating this issue.
|
Oct 06, 2025 at 12:08 PM UTC
|
about 6 hours |
|
We are currently investigating this issue.
|
Sep 13, 2025 at 12:41 PM UTC
|
about 2 hours |
|
We are currently investigating this issue.
|
Sep 06, 2025 at 10:08 AM UTC
|
about 1 hour |
Check if any Locally component is down. View the current status of 9 services and regions.
IsDown has monitored Locally continuously since January 2021, tracking this E-Commerce for 5 years. Over that time, we've documented 54 outages and incidents, averaging 0.9 per month. When Locally goes down, incidents typically resolve within 428 minutes based on historical data.
We monitor Locally's official status page across 9 components. IsDown interprets Locally statuses (operational, degraded performance, partial outage, and major outage) to deliver precise health metrics and filter alerts by the components you actually use.
To check if Locally is down, IsDown combines official status data with user reports for early detection. Vendors often delay acknowledging problems, so user reports help us alert you before the official announcement.
Engineering and operations teams rely on IsDown to track Locally status and receive verified outage alerts through Slack, Teams, PagerDuty, or 20+ other integrations.
IsDown checks Locally's status page every few minutes, across all 9 components. We combine official status data with user reports to detect when Locally is down, often before the vendor announces it.
When Locally status changes, IsDown sends alerts to your preferred channels. Filter by severity to skip noise and focus on outages that affect your business.
IsDown checks Locally official status page for major/minor outages or downtimes. A major outage is when Locally experiences a critical issue that severely affects one or more services/regions. A minor incident is when Locally experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. The moment we detect a Locally outage, we send you an alert and update your dashboard and status page.
Locally and other vendors don't always report outages on time. IsDown collects user reports to provide early detection of outages. This way, even without an official status update, you can stay ahead of possible problems.
IsDown collects all information from the outages published in Locally status page to provide the context of the outage. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
Locally publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.
IsDown monitors Locally and all their 9 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
Get started in minutes. Monitor all your critical services from one place.
IsDown checks the status of over 5,450+ services every few minutes. We aggregate official status information and normalize it, plus collect crowdsourced reports for early outage detection.
When we detect an incident or status change, you receive an alert immediately. Customize notifications by service, component, or severity to avoid alert fatigue.
View all your services in a unified dashboard or public or private status page. Send alerts to Slack, Teams, PagerDuty, Datadog, and 20+ other tools your team already uses.
No credit card required • 14-day free trial
Looking for Locally outage alerts like Downdetector? IsDown monitors Locally's official status page for verified incident data, not just user reports. Know exactly when Locally is down, which components are affected, and when service health is restored. Here's why official Locally status monitoring beats crowdsourced detection:
| Features | IsDown | Downdetector |
|---|---|---|
| Official Locally status page monitoring. Know when Locally is down with real time incident details. | ||
| Monitor 5,450+ services including Locally in a single dashboard. | ||
| Instant Locally outage alerts sent to Slack, Teams, PagerDuty, and more. | ||
| Combined monitoring: Locally official status plus user reports for early outage detection. | ||
| Maintenance feed for Locally | ||
| Granular alerts filtering by Locally components and regions. |
14-day free trial • No credit card required
Locally isn't down. You can check Locally status and incident details on the top of the page. IsDown continuously monitors Locally official status page every few minutes. In the last 24 hours, there were 0 outages reported.
Locally is currently operational. You can check Locally status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.
No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.
Currently there's no report of Locally being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the Locally official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
Locally last outage was on January 23, 2026 with the title "ShopSense reports are delayed"
Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor Locally and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.
IsDown and DownDetector help users determine if Locally is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information instead of just relying on reports from users. The integration allows us to provide more details about Locally's Outages, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
14-day free trial · No credit card required · No code required