User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 917 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 10 | 0 | 0.0 | 755 ms | 0 |
| Tue 12 | 0 | 0.0 | 739 ms | 0 |
| Tue 15 | 0 | 0.0 | 455 ms | 0 |
| Tue 17 | 0 | 0.0 | 1262 ms | 0 |
| Tue 19 | 0 | 0.0 | 704 ms | 0 |
| Tue 22 | 0 | 0.0 | 418 ms | 0 |
| Wed 00 | 0 | 0.0 | 897 ms | 0 |
| Wed 02 | 0 | 0.0 | 965 ms | 0 |
| Wed 04 | 0 | 0.0 | 1000 ms | 0 |
| Wed 06 | 0 | 0.0 | 607 ms | 0 |
| Wed 09 | 0 | 0.0 | 686 ms | 0 |
| Wed 11 | 0 | 0.0 | 396 ms | 0 |
| Wed 13 | 0 | 0.0 | 835 ms | 0 |
| Wed 15 | 0 | 0.0 | 501 ms | 0 |
| Wed 17 | 0 | 0.0 | 916 ms | 0 |
| Wed 20 | 0 | 0.0 | 920 ms | 0 |
| Wed 22 | 0 | 0.0 | 1003 ms | 0 |
| Thu 00 | 0 | 0.0 | 855 ms | 0 |
| Thu 02 | 0 | 0.0 | 1265 ms | 0 |
| Thu 04 | 0 | 0.0 | 1035 ms | 0 |
| Thu 06 | 0 | 0.0 | 799 ms | 0 |
| Thu 08 | 0 | 0.0 | 817 ms | 0 |
| Thu 10 | 0 | 0.0 | 488 ms | 0 |
| Thu 12 | 0 | 0.0 | 795 ms | 0 |
| Thu 14 | 0 | 0.0 | 752 ms | 0 |
| Thu 16 | 0 | 0.0 | 580 ms | 0 |
| Thu 19 | 0 | 0.0 | 583 ms | 0 |
| Thu 21 | 0 | 0.0 | 898 ms | 0 |
| Thu 23 | 0 | 0.0 | 862 ms | 0 |
| Fri 01 | 0 | 0.0 | 916 ms | 0 |
| Fri 03 | 0 | 0.0 | 673 ms | 0 |
| Fri 05 | 0 | 0.0 | 579 ms | 0 |
| Fri 07 | 0 | 0.0 | 849 ms | 0 |
| Fri 08 | 0 | 0.0 | 700 ms | 0 |
| Fri 10 | 0 | 0.0 | 862 ms | 0 |
| Fri 11 | 0 | 0.0 | 861 ms | 0 |
| Fri 12 | 0 | 0.0 | 811 ms | 0 |
| Fri 14 | 0 | 0.0 | 683 ms | 0 |
| Fri 16 | 0 | 0.0 | 778 ms | 0 |
| Fri 18 | 0 | 0.0 | 641 ms | 0 |
| Fri 20 | 0 | 0.0 | 1066 ms | 0 |
| Fri 22 | 0 | 0.0 | 690 ms | 0 |
| Sat 00 | 0 | 0.0 | 386 ms | 0 |
| Sat 02 | 0 | 0.0 | 892 ms | 0 |
| Sat 04 | 0 | 0.0 | 1011 ms | 0 |
| Sat 06 | 0 | 0.0 | 1622 ms | 0 |
| Sat 08 | 0 | 0.0 | 837 ms | 0 |
| Sat 10 | 0 | 0.0 | 917 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for NearSt yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when NearSt goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send NearSt alerts to Slack, Discord or a webhook — free.
NearSt is listed in our Shopping category and checked at near.st. The leading in-store inventory feed platform for retail. Connect your products to Google, Meta and more.
NearSt publishes an official status page at status.near.st; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with shopping services: checkout and payment errors, carts not loading, and order tracking problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 866 ms average, 386–1622 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public NearSt incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
866 ms on average over the last 24 hours (386–1622 ms).
Yes, at https://status.near.st.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For shopping services, watch for checkout and payment errors, carts not loading, and order tracking problems. If many people report NearSt here at once, the problem is on NearSt's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with NearSt. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.