User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 1 hr ago. Last stored result reached it in 107 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 184 ms | 0 |
| Tue 00 | 0 | 0.0 | 163 ms | 0 |
| Tue 02 | 0 | 0.0 | 149 ms | 0 |
| Tue 04 | 0 | 0.0 | 66 ms | 0 |
| Tue 06 | 0 | 0.0 | 117 ms | 0 |
| Tue 08 | 0 | 0.0 | 113 ms | 0 |
| Tue 10 | 0 | 0.0 | 374 ms | 0 |
| Tue 12 | 0 | 0.0 | 100 ms | 0 |
| Tue 15 | 0 | 0.0 | 166 ms | 0 |
| Tue 17 | 0 | 0.0 | 132 ms | 0 |
| Tue 19 | 0 | 0.0 | 238 ms | 0 |
| Tue 21 | 0 | 0.0 | 157 ms | 0 |
| Wed 00 | 0 | 0.0 | 85 ms | 0 |
| Wed 02 | 0 | 0.0 | 352 ms | 0 |
| Wed 04 | 0 | 0.0 | 121 ms | 0 |
| Wed 06 | 0 | 0.0 | 229 ms | 0 |
| Wed 08 | 0 | 0.0 | 163 ms | 0 |
| Wed 11 | 0 | 0.0 | 162 ms | 0 |
| Wed 13 | 0 | 0.0 | 253 ms | 0 |
| Wed 15 | 0 | 0.0 | 917 ms | 0 |
| Wed 17 | 0 | 0.0 | 101 ms | 0 |
| Wed 19 | 0 | 0.0 | 409 ms | 0 |
| Wed 21 | 0 | 0.0 | 125 ms | 0 |
| Thu 00 | 0 | 0.0 | 121 ms | 0 |
| Thu 02 | 0 | 0.0 | 176 ms | 0 |
| Thu 04 | 0 | 0.0 | 136 ms | 0 |
| Thu 06 | 0 | 0.0 | 138 ms | 0 |
| Thu 08 | 0 | 0.0 | 214 ms | 0 |
| Thu 10 | 0 | 0.0 | 132 ms | 0 |
| Thu 12 | 0 | 0.0 | 273 ms | 0 |
| Thu 14 | 0 | 0.0 | 128 ms | 0 |
| Thu 16 | 0 | 0.0 | 233 ms | 0 |
| Thu 18 | 0 | 0.0 | 272 ms | 0 |
| Thu 20 | 0 | 0.0 | 195 ms | 0 |
| Thu 22 | 0 | 0.0 | 199 ms | 0 |
| Fri 00 | 0 | 0.0 | 338 ms | 0 |
| Fri 02 | 0 | 0.0 | 182 ms | 0 |
| Fri 05 | 0 | 0.0 | 112 ms | 0 |
| Fri 07 | 0 | 0.0 | 100 ms | 0 |
| Fri 09 | 0 | 0.0 | 241 ms | 0 |
| Fri 10 | 0 | 0.0 | 101 ms | 0 |
| Fri 11 | 0 | 0.0 | 104 ms | 0 |
| Fri 12 | 0 | 0.0 | 133 ms | 0 |
| Fri 14 | 0 | 0.0 | 164 ms | 0 |
| Fri 16 | 0 | 0.0 | 121 ms | 0 |
| Fri 18 | 0 | 0.0 | 85 ms | 0 |
| Fri 20 | 0 | 0.0 | 156 ms | 0 |
| Fri 22 | 0 | 0.0 | 107 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Creem 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 Creem goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Creem alerts to Slack, Discord or a webhook — free.
Creem, at creem.io, is one of the AI services we monitor. Creem is the money platform for the AI era. Sell software and digital products globally.
Creem publishes an official status page at status.creem.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 150 ms average, 85–338 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 Creem incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
150 ms on average over the last 24 hours (85–338 ms).
Yes, at https://status.creem.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Creem here at once, the problem is on Creem'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 Creem. 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.