User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 8 min ago. Last stored result reached it in 51 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 50 ms | 0 |
| Tue 00 | 0 | 0.0 | 90 ms | 0 |
| Tue 02 | 0 | 0.0 | 96 ms | 0 |
| Tue 04 | 0 | 0.0 | 97 ms | 0 |
| Tue 07 | 0 | 0.0 | 389 ms | 0 |
| Tue 09 | 0 | 0.0 | 91 ms | 0 |
| Tue 11 | 0 | 0.0 | 90 ms | 0 |
| Tue 13 | 0 | 0.0 | 91 ms | 0 |
| Tue 15 | 0 | 0.0 | 40 ms | 0 |
| Tue 17 | 0 | 0.0 | 79 ms | 0 |
| Tue 20 | 0 | 0.0 | 93 ms | 0 |
| Tue 22 | 0 | 0.0 | 64 ms | 0 |
| Wed 00 | 0 | 0.0 | 53 ms | 0 |
| Wed 02 | 0 | 0.0 | 52 ms | 0 |
| Wed 05 | 0 | 0.0 | 41 ms | 0 |
| Wed 07 | 0 | 0.0 | 40 ms | 0 |
| Wed 09 | 0 | 0.0 | 63 ms | 0 |
| Wed 11 | 0 | 0.0 | 80 ms | 0 |
| Wed 14 | 0 | 0.0 | 83 ms | 0 |
| Wed 16 | 0 | 0.0 | 80 ms | 0 |
| Wed 18 | 0 | 0.0 | 36 ms | 0 |
| Wed 20 | 0 | 0.0 | 132 ms | 0 |
| Wed 22 | 0 | 0.0 | 28 ms | 0 |
| Thu 00 | 0 | 0.0 | 176 ms | 0 |
| Thu 03 | 0 | 0.0 | 264 ms | 0 |
| Thu 05 | 0 | 0.0 | 97 ms | 0 |
| Thu 07 | 0 | 0.0 | 72 ms | 0 |
| Thu 09 | 0 | 0.0 | 98 ms | 0 |
| Thu 11 | 0 | 0.0 | 124 ms | 0 |
| Thu 13 | 0 | 0.0 | 120 ms | 0 |
| Thu 15 | 0 | 0.0 | 93 ms | 0 |
| Thu 17 | 0 | 0.0 | 109 ms | 0 |
| Thu 19 | 0 | 0.0 | 39 ms | 0 |
| Thu 21 | 0 | 0.0 | 87 ms | 0 |
| Thu 23 | 0 | 0.0 | 130 ms | 0 |
| Fri 01 | 0 | 0.0 | 93 ms | 0 |
| Fri 03 | 0 | 0.0 | 88 ms | 0 |
| Fri 05 | 0 | 0.0 | 133 ms | 0 |
| Fri 07 | 0 | 0.0 | 86 ms | 0 |
| Fri 09 | 0 | 0.0 | 46 ms | 0 |
| Fri 11 | 0 | 0.0 | 35 ms | 0 |
| Fri 12 | 0 | 0.0 | 67 ms | 0 |
| Fri 14 | 0 | 0.0 | 67 ms | 0 |
| Fri 16 | 0 | 0.0 | 89 ms | 0 |
| Fri 18 | 0 | 0.0 | 99 ms | 0 |
| Fri 20 | 0 | 0.0 | 77 ms | 0 |
| Fri 22 | 0 | 0.0 | 72 ms | 0 |
| Fri 23 | 0 | 0.0 | 51 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 Smeetz 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 Smeetz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Smeetz alerts to Slack, Discord or a webhook — free.
Smeetz, at smeetz.com, is one of the Money services we monitor. Online ticketing, POS, payments, dynamic pricing and CRM in one platform for amusement parks, zoos, museums and theatres. Trusted by 100+ venues.
Smeetz publishes an official status page at status.smeetz.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 81 ms average, 35–133 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Smeetz incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
81 ms on average over the last 24 hours (35–133 ms).
Yes, at https://status.smeetz.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Smeetz here at once, the problem is on Smeetz'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 Smeetz. 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.