User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 30 min ago. Last stored result reached it in 569 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 475 ms | 0 |
| Mon 17 | 0 | 0.0 | 508 ms | 0 |
| Mon 19 | 0 | 0.0 | 483 ms | 0 |
| Mon 21 | 0 | 0.0 | 534 ms | 0 |
| Tue 00 | 0 | 0.0 | 456 ms | 0 |
| Tue 02 | 0 | 0.0 | 357 ms | 0 |
| Tue 04 | 0 | 0.0 | 460 ms | 0 |
| Tue 06 | 0 | 0.0 | 389 ms | 0 |
| Tue 08 | 0 | 0.0 | 477 ms | 0 |
| Tue 10 | 0 | 0.0 | 594 ms | 0 |
| Tue 12 | 0 | 0.0 | 679 ms | 0 |
| Tue 14 | 0 | 0.0 | 518 ms | 0 |
| Tue 17 | 0 | 0.0 | 533 ms | 0 |
| Tue 19 | 0 | 0.0 | 552 ms | 0 |
| Tue 21 | 0 | 0.0 | 324 ms | 0 |
| Tue 23 | 0 | 0.0 | 501 ms | 0 |
| Wed 02 | 0 | 0.0 | 572 ms | 0 |
| Wed 04 | 0 | 0.0 | 492 ms | 0 |
| Wed 06 | 0 | 0.0 | 456 ms | 0 |
| Wed 08 | 0 | 0.0 | 409 ms | 0 |
| Wed 11 | 0 | 0.0 | 765 ms | 0 |
| Wed 13 | 0 | 0.0 | 530 ms | 0 |
| Wed 15 | 0 | 0.0 | 636 ms | 0 |
| Wed 17 | 0 | 0.0 | 652 ms | 0 |
| Wed 19 | 0 | 0.0 | 567 ms | 0 |
| Wed 21 | 0 | 0.0 | 379 ms | 0 |
| Wed 23 | 0 | 0.0 | 488 ms | 0 |
| Thu 02 | 0 | 0.0 | 513 ms | 0 |
| Thu 04 | 0 | 0.0 | 397 ms | 0 |
| Thu 06 | 0 | 0.0 | 506 ms | 0 |
| Thu 08 | 0 | 0.0 | 440 ms | 0 |
| Thu 10 | 0 | 0.0 | 451 ms | 0 |
| Thu 12 | 0 | 0.0 | 510 ms | 0 |
| Thu 14 | 0 | 0.0 | 420 ms | 0 |
| Thu 16 | 0 | 0.0 | 481 ms | 0 |
| Thu 18 | 0 | 0.0 | 485 ms | 0 |
| Thu 20 | 0 | 0.0 | 437 ms | 0 |
| Thu 22 | 0 | 0.0 | 427 ms | 0 |
| Fri 00 | 0 | 0.0 | 616 ms | 0 |
| Fri 02 | 0 | 0.0 | 346 ms | 0 |
| Fri 04 | 0 | 0.0 | 502 ms | 0 |
| Fri 06 | 0 | 0.0 | 470 ms | 0 |
| Fri 09 | 0 | 0.0 | 312 ms | 0 |
| Fri 11 | 0 | 0.0 | 473 ms | 0 |
| Fri 13 | 0 | 0.0 | 452 ms | 0 |
| Fri 15 | 0 | 0.0 | 461 ms | 0 |
| Fri 17 | 0 | 0.0 | 520 ms | 0 |
| Fri 18 | 0 | 0.0 | 569 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 AppCard 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 AppCard goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AppCard alerts to Slack, Discord or a webhook — free.
AppCard, at appcard.com, is one of the Productivity services we monitor. AppCard empowers 3,000+ independent grocers with personalized marketing, shopper analytics, and in-lane engagement tools that drive loyalty and increase sales.
AppCard publishes an official status page at status.appcard.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in 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: 456 ms average, 197–616 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AppCard incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
456 ms on average over the last 24 hours (197–616 ms).
Yes, at https://status.appcard.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report AppCard here at once, the problem is on AppCard'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 AppCard. 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.