Sharetribe Outage History
12 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Sharetribe Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 14, 2026 | Elevated latency in Marketplace APIThe Marketplace API response time and error rate was elevated for about 8 minutes. The issue has caused by insufficient API server resources and has been resolved. | -40 min | Resolved |
| Oct 3, 2026 | Elevated latency and error levelsThis incident has been resolved. The issue was caused by one of the servers going into an unhealthy state. The unhealthy server did not terminate automatically and thus traffic was still routed to it. We are… | 1h 29m | Resolved |
| Aug 14, 2026 | Delay in event processingEvent processing pipeline has caught up. The incident is resolved. We will keep investigating for the root cause. | 1h 17m | Resolved |
| Aug 13, 2026 | Delay in event processingThis incident has been resolved. We were able to identify and fix the bad data that caused the Event processing pipeline to get stuck. We will continue investigating the root cause, and once found, we will implement a… | 54 min | Resolved |
| Jul 7, 2026 | Elevated latencyThis incident has been resolved. | 46 min | Resolved |
| Apr 29, 2026 | Search indexes contain stale dataAfter the database maintenance performed today, our data indexing service did not properly recover, resulting in search indexes containing stale data for roughly 2.5 hours. In addition, due to an issue with the… | 3h 20m | Resolved |
| Apr 29, 2026 | Sharetribe database maintenanceMaintenance completed. Estimated downtime of some APIs was about 30-60 seconds. | 2h 0m | Scheduled |
| Mar 24, 2026 | Elevated error rates in Marketplace APIMarketplace API experienced elevated latency and error rates. The incident is resolved. | -23 min | Resolved |
| Mar 20, 2026 | Elevated error rates in Marketplace APIFrom 16:00 to 16:50 UTC on March 20th we saw elevated error rates in Marketplace API. The incident is now solved and we are monitoring the situation. | 0 min | Resolved |
| Feb 11, 2026 | Elevated latency in Marketplace APIWe saw increased latency in the Marketplace API and addressed the issue. It went back to normal after 20 minutes. We keep monitoring the situation. | 0 min | Resolved |
| Jan 19, 2026 | Increased API latencyThis incident has been resolved. | 54 min | Resolved |
| Nov 12, 2025 | Database maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Sharetribe incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Sharetribe Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Sharetribe acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Sharetribe outage in this window ran 3h 20m, against a mean recovery of 1h 10m. If you depend on Sharetribe in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.