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 22 min ago. Last stored result reached it in 299 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 09 | 0 | 0.0 | 99 ms | 0 |
| Tue 11 | 0 | 0.0 | 151 ms | 0 |
| Tue 13 | 0 | 0.0 | 136 ms | 0 |
| Tue 15 | 0 | 0.0 | 473 ms | 0 |
| Tue 18 | 0 | 0.0 | 183 ms | 0 |
| Tue 20 | 0 | 0.0 | 220 ms | 0 |
| Tue 22 | 0 | 0.0 | 122 ms | 0 |
| Wed 00 | 0 | 0.0 | 307 ms | 0 |
| Wed 02 | 0 | 0.0 | 221 ms | 0 |
| Wed 04 | 0 | 0.0 | 154 ms | 0 |
| Wed 06 | 0 | 0.0 | 269 ms | 0 |
| Wed 09 | 0 | 0.0 | 293 ms | 0 |
| Wed 11 | 0 | 0.0 | 355 ms | 0 |
| Wed 13 | 0 | 0.0 | 190 ms | 0 |
| Wed 15 | 0 | 0.0 | 291 ms | 0 |
| Wed 17 | 0 | 0.0 | 244 ms | 0 |
| Wed 20 | 0 | 0.0 | 407 ms | 0 |
| Wed 22 | 0 | 0.0 | 854 ms | 0 |
| Thu 00 | 0 | 0.0 | 185 ms | 0 |
| Thu 02 | 0 | 0.0 | 186 ms | 0 |
| Thu 04 | 0 | 0.0 | 85 ms | 0 |
| Thu 06 | 0 | 0.0 | 129 ms | 0 |
| Thu 08 | 0 | 0.0 | 187 ms | 0 |
| Thu 10 | 0 | 0.0 | 147 ms | 0 |
| Thu 12 | 0 | 0.0 | 167 ms | 0 |
| Thu 15 | 0 | 0.0 | 180 ms | 0 |
| Thu 17 | 0 | 0.0 | 311 ms | 0 |
| Thu 19 | 0 | 0.0 | 152 ms | 0 |
| Thu 21 | 0 | 0.0 | 131 ms | 0 |
| Thu 23 | 0 | 0.0 | 174 ms | 0 |
| Fri 01 | 0 | 0.0 | 176 ms | 0 |
| Fri 03 | 0 | 0.0 | 740 ms | 0 |
| Fri 05 | 0 | 0.0 | 297 ms | 0 |
| Fri 06 | 0 | 0.0 | 284 ms | 0 |
| Fri 08 | 0 | 0.0 | 379 ms | 0 |
| Fri 10 | 0 | 0.0 | 202 ms | 0 |
| Fri 11 | 0 | 0.0 | 236 ms | 0 |
| Fri 13 | 0 | 0.0 | 328 ms | 0 |
| Fri 15 | 0 | 0.0 | 232 ms | 0 |
| Fri 17 | 0 | 0.0 | 312 ms | 0 |
| Fri 19 | 0 | 0.0 | 108 ms | 0 |
| Fri 20 | 0 | 0.0 | 134 ms | 0 |
| Fri 21 | 0 | 0.0 | 162 ms | 0 |
| Fri 23 | 0 | 0.0 | 251 ms | 0 |
| Sat 01 | 0 | 0.0 | 199 ms | 0 |
| Sat 03 | 0 | 0.0 | 112 ms | 0 |
| Sat 05 | 0 | 0.0 | 83 ms | 0 |
| Sat 07 | 0 | 0.0 | 317 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Sharetribe 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 Sharetribe goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sharetribe alerts to Slack, Discord or a webhook — free.
Sharetribe is listed in our AI category and checked at sharetribe.com. Marketplace software to build and launch your own marketplace. Payments, listings, and user accounts come built in. Customize with no-code, AI tools, or code.
Sharetribe publishes an official status page at status.sharetribe.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 225 ms average, 83–379 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Sharetribe incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
225 ms on average over the last 24 hours (83–379 ms).
Yes, at https://status.sharetribe.com.
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 Sharetribe here at once, the problem is on Sharetribe'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 Sharetribe. 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.