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 122 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 177 ms | 0 |
| Mon 15 | 0 | 0.0 | 146 ms | 0 |
| Mon 17 | 0 | 0.0 | 181 ms | 0 |
| Mon 19 | 0 | 0.0 | 109 ms | 0 |
| Mon 22 | 0 | 0.0 | 188 ms | 0 |
| Tue 00 | 0 | 0.0 | 111 ms | 0 |
| Tue 02 | 0 | 0.0 | 139 ms | 0 |
| Tue 04 | 0 | 0.0 | 99 ms | 0 |
| Tue 06 | 0 | 0.0 | 237 ms | 0 |
| Tue 08 | 0 | 0.0 | 107 ms | 0 |
| Tue 10 | 0 | 0.0 | 114 ms | 0 |
| Tue 12 | 0 | 0.0 | 110 ms | 0 |
| Tue 15 | 0 | 0.0 | 272 ms | 0 |
| Tue 17 | 0 | 0.0 | 120 ms | 0 |
| Tue 19 | 0 | 0.0 | 143 ms | 0 |
| Tue 21 | 0 | 0.0 | 131 ms | 0 |
| Wed 00 | 0 | 0.0 | 158 ms | 0 |
| Wed 02 | 0 | 0.0 | 106 ms | 0 |
| Wed 04 | 0 | 0.0 | 170 ms | 0 |
| Wed 06 | 0 | 0.0 | 78 ms | 0 |
| Wed 08 | 0 | 0.0 | 92 ms | 0 |
| Wed 11 | 0 | 0.0 | 99 ms | 0 |
| Wed 13 | 0 | 0.0 | 118 ms | 0 |
| Wed 15 | 0 | 0.0 | 139 ms | 0 |
| Wed 17 | 0 | 0.0 | 126 ms | 0 |
| Wed 19 | 0 | 0.0 | 107 ms | 0 |
| Wed 21 | 0 | 0.0 | 301 ms | 0 |
| Thu 00 | 0 | 0.0 | 114 ms | 0 |
| Thu 02 | 0 | 0.0 | 94 ms | 0 |
| Thu 04 | 0 | 0.0 | 146 ms | 0 |
| Thu 06 | 0 | 0.0 | 97 ms | 0 |
| Thu 08 | 0 | 0.0 | 136 ms | 0 |
| Thu 10 | 0 | 0.0 | 108 ms | 0 |
| Thu 12 | 0 | 0.0 | 98 ms | 0 |
| Thu 14 | 0 | 0.0 | 159 ms | 0 |
| Thu 16 | 0 | 0.0 | 219 ms | 0 |
| Thu 18 | 0 | 0.0 | 192 ms | 0 |
| Thu 20 | 0 | 0.0 | 113 ms | 0 |
| Thu 22 | 0 | 0.0 | 110 ms | 0 |
| Fri 00 | 0 | 0.0 | 67 ms | 0 |
| Fri 02 | 0 | 0.0 | 200 ms | 0 |
| Fri 05 | 0 | 0.0 | 89 ms | 0 |
| Fri 07 | 0 | 0.0 | 111 ms | 0 |
| Fri 09 | 0 | 0.0 | 105 ms | 0 |
| Fri 10 | 0 | 0.0 | 156 ms | 0 |
| Fri 12 | 0 | 0.0 | 112 ms | 0 |
| Fri 14 | 0 | 0.0 | 180 ms | 0 |
| Fri 15 | 0 | 0.0 | 122 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 Commerce Layer 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 Commerce Layer goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Commerce Layer alerts to Slack, Discord or a webhook — free.
We track Commerce Layer (commercelayer.io) as part of the AI group. AI agents will discover products, make recommendations, and complete purchases on behalf of people. Commerce Layer provides the API infrastructure powering this shift.
Commerce Layer publishes an official status page at status.commercelayer.io; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 130 ms average, 67–200 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Commerce Layer incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
130 ms on average over the last 24 hours (67–200 ms).
Yes, at https://status.commercelayer.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 Commerce Layer here at once, the problem is on Commerce Layer'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 Commerce Layer. 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.