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 16 min ago. Last stored result reached it in 688 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 519 ms | 0 |
| Tue 04 | 0 | 0.0 | 744 ms | 0 |
| Tue 06 | 0 | 0.0 | 598 ms | 0 |
| Tue 08 | 0 | 0.0 | 342 ms | 0 |
| Tue 11 | 0 | 0.0 | 735 ms | 0 |
| Tue 13 | 0 | 0.0 | 304 ms | 0 |
| Tue 15 | 0 | 0.0 | 465 ms | 0 |
| Tue 17 | 0 | 0.0 | 376 ms | 0 |
| Tue 19 | 0 | 0.0 | 946 ms | 0 |
| Tue 22 | 0 | 0.0 | 288 ms | 0 |
| Wed 00 | 0 | 0.0 | 900 ms | 0 |
| Wed 02 | 0 | 0.0 | 1300 ms | 0 |
| Wed 04 | 0 | 0.0 | 560 ms | 0 |
| Wed 07 | 0 | 0.0 | 808 ms | 0 |
| Wed 09 | 0 | 0.0 | 761 ms | 0 |
| Wed 11 | 0 | 0.0 | 515 ms | 0 |
| Wed 13 | 0 | 0.0 | 559 ms | 0 |
| Wed 15 | 0 | 0.0 | 773 ms | 0 |
| Wed 17 | 0 | 0.0 | 300 ms | 0 |
| Wed 20 | 0 | 0.0 | 638 ms | 0 |
| Wed 22 | 0 | 0.0 | 275 ms | 0 |
| Thu 01 | 0 | 0.0 | 700 ms | 0 |
| Thu 03 | 0 | 0.0 | 264 ms | 0 |
| Thu 05 | 0 | 0.0 | 669 ms | 0 |
| Thu 07 | 0 | 0.0 | 608 ms | 0 |
| Thu 09 | 0 | 0.0 | 287 ms | 0 |
| Thu 11 | 0 | 0.0 | 649 ms | 0 |
| Thu 13 | 0 | 0.0 | 330 ms | 0 |
| Thu 15 | 0 | 0.0 | 802 ms | 0 |
| Thu 17 | 0 | 0.0 | 384 ms | 0 |
| Thu 19 | 0 | 0.0 | 846 ms | 0 |
| Thu 21 | 0 | 0.0 | 630 ms | 0 |
| Thu 23 | 0 | 0.0 | 393 ms | 0 |
| Fri 01 | 0 | 0.0 | 589 ms | 0 |
| Fri 03 | 0 | 0.0 | 611 ms | 0 |
| Fri 05 | 0 | 0.0 | 270 ms | 0 |
| Fri 07 | 0 | 0.0 | 841 ms | 0 |
| Fri 08 | 0 | 0.0 | 567 ms | 0 |
| Fri 10 | 0 | 0.0 | 699 ms | 0 |
| Fri 11 | 0 | 0.0 | 638 ms | 0 |
| Fri 12 | 0 | 0.0 | 319 ms | 0 |
| Fri 14 | 0 | 0.0 | 331 ms | 0 |
| Fri 16 | 0 | 0.0 | 357 ms | 0 |
| Fri 17 | 0 | 0.0 | 742 ms | 0 |
| Fri 18 | 0 | 0.0 | 304 ms | 0 |
| Fri 20 | 0 | 0.0 | 831 ms | 0 |
| Fri 22 | 0 | 0.0 | 633 ms | 0 |
| Sat 00 | 0 | 0.0 | 653 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 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 559 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 8 days ago.
From our own checks: 100% over 8 days of checks.
559 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.