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 min ago. Last stored result reached it in 303 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 781 ms | 0 |
| Nov 7 | 0 | 0.0 | 284 ms | 0 |
| Nov 7 | 0 | 0.0 | 263 ms | 0 |
| Nov 7 | 0 | 0.0 | 260 ms | 0 |
| Nov 7 | 0 | 0.0 | 447 ms | 0 |
| Nov 8 | 0 | 0.0 | 460 ms | 0 |
| Nov 8 | 0 | 0.0 | 370 ms | 0 |
| Nov 8 | 0 | 0.0 | 782 ms | 0 |
| Nov 8 | 0 | 0.0 | 585 ms | 0 |
| Nov 9 | 0 | 0.0 | 338 ms | 0 |
| Nov 9 | 0 | 0.0 | 652 ms | 0 |
| Nov 9 | 0 | 0.0 | 334 ms | 0 |
| Nov 9 | 0 | 0.0 | 676 ms | 0 |
| Nov 10 | 0 | 0.0 | 519 ms | 0 |
| Nov 10 | 0 | 0.0 | 598 ms | 0 |
| Nov 10 | 0 | 0.0 | 387 ms | 0 |
| Nov 10 | 0 | 0.0 | 617 ms | 0 |
| Nov 11 | 0 | 0.0 | 900 ms | 0 |
| Nov 11 | 0 | 0.0 | 761 ms | 0 |
| Nov 11 | 0 | 0.0 | 559 ms | 0 |
| Nov 11 | 0 | 0.0 | 629 ms | 0 |
| Nov 12 | 0 | 0.0 | 669 ms | 0 |
| Nov 12 | 0 | 0.0 | 457 ms | 0 |
| Nov 12 | 0 | 0.0 | 384 ms | 0 |
| Nov 12 | 0 | 0.0 | 630 ms | 0 |
| Nov 13 | 0 | 0.0 | 589 ms | 0 |
| Nov 13 | 0 | 0.0 | 638 ms | 0 |
| Nov 13 | 0 | 0.0 | 341 ms | 0 |
| Nov 13 | 0 | 0.0 | 633 ms | 0 |
| Nov 14 | 0 | 0.0 | 617 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for AppFollow 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 AppFollow goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AppFollow alerts to Slack, Discord or a webhook — free.
We track AppFollow (appfollow.io) as part of the Shopping group. #1 tools for managing app store reviews and ratings. Analyze user feedback, respond to reviews, automate workflows, grow app visibility for iOS, Android, Amazon, Huawei.
AppFollow publishes an official status page at status.appfollow.io; when we can read it, its incident level is folded into the status shown here.
Common problems for shopping services: checkout and payment errors, carts not loading, and order tracking problems.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 543 ms average, 270–841 ms range across 18 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AppFollow incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
543 ms on average over the last 24 hours (270–841 ms).
Yes, at https://status.appfollow.io.
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 AppFollow here at once, the problem is on AppFollow'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 AppFollow. 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.