Is Sharetribe down?

Last checked 1m ago
Current status
Sharetribe is up

No incidents right now.

Sharetribe is operational right now. Last checked 1m ago; the most recent incident resolved 16d ago.

Real-time Sharetribe status, recent outages, and incident history: pulled directly from Sharetribe's official status page at status.sharetribe.com every 5 minutes. Pingoru tracks 21 Sharetribe services and has captured 4 incidents in the last 90 days (99.29% uptime). Get email, Slack, Discord, or webhook alerts the moment Sharetribe reports a new incident, free for 3 monitors, no credit card.

Users who monitor Sharetribe also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 8,000+ providers
Sharetribe uptime 99.29% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 8m
    Started Oct 14, 2026, 04:00 PM UTC · Resolved Oct 14, 2026, 04:08 PM UTC
    Timeline · 1 update
    • resolved · Oct 14, 2026, 04:40 PM UTC

      The 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.

    Latest: The 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.

  2. Resolved 1h 29m
    Started Oct 03, 2026, 04:16 PM UTC · Resolved Oct 03, 2026, 05:45 PM UTC
    Marketplace APIIntegration APIAuthentication APIAsset Delivery APINo-code marketplace web sitesNo-code marketplace web sites with custom domainConsole
    Timeline · 4 updates
    • investigating · Oct 03, 2026, 04:16 PM UTC

      We are currently investigating an issue causing elevated error levels and latency

    • investigating · Oct 03, 2026, 04:22 PM UTC

      We are continuing to investigate this issue.

    • monitoring · Oct 03, 2026, 04:40 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Oct 03, 2026, 05:45 PM UTC

      This 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 investigating the root cause of the server becoming unhealthy and, more importantly, why it did not terminate automatically.

    Latest: This 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…

  3. Resolved 1h 17m
    Started Aug 14, 2026, 01:00 PM UTC · Resolved Aug 14, 2026, 02:18 PM UTC
    Integration API
    Timeline · 3 updates
    • identified · Aug 14, 2026, 01:00 PM UTC

      Due to an error in the Event processing pipeline, events have not been delivered since 2026-08-14T11:50:46.984Z. We have identified the data that is causing this issue and we are investigating ways to fix the data.

    • monitoring · Aug 14, 2026, 01:43 PM UTC

      We have identified and fixed the inconsistent data that caused the issue. The event pipeline is recovering and catching up. We will monitor the situation.

    • resolved · Aug 14, 2026, 02:18 PM UTC

      Event processing pipeline has caught up. The incident is resolved. We will keep investigating for the root cause.

    Latest: Event processing pipeline has caught up. The incident is resolved. We will keep investigating for the root cause.

  4. Resolved 54m
    Started Aug 13, 2026, 01:07 PM UTC · Resolved Aug 13, 2026, 02:02 PM UTC
    Integration API
    Timeline · 3 updates
    • investigating · Aug 13, 2026, 01:07 PM UTC

      Due to an error in the Event processing pipeline, events have not been delivered since 2026-08-13T11:43:14.514Z. We are investigating the issue.

    • monitoring · Aug 13, 2026, 01:31 PM UTC

      We are seeing the event processing pipeline recovering. We will keep monitoring the situation.

    • resolved · Aug 13, 2026, 02:02 PM UTC

      This 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 fix to prevent this from happening again.

    Latest: This 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…

Incident record

Since April 2026 · Statuspage by Atlassian · 21 components checked every 5 minutes
42incidents recorded
10last 12 months
4last 90 days
89 minutestypical duration, 12 months

The longest incident in the last year, Search indexes contain stale data on April 29, 2026, ran for 6 hours. 2 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Integration API5
  • Marketplace API3
  • Asset Delivery API2
  • Authentication API2
  • Console1

Latest incidents

  • Elevated latency in Marketplace API October 14, 2026 · 8 minutes · major outage

    The 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…

  • Elevated latency and error levels October 3, 2026 · 89 minutes · major outage

    We are currently investigating an issue causing elevated error levels and latency

  • Delay in event processing August 14, 2026 · 77 minutes · major outage

    Due to an error in the Event processing pipeline, events have not been delivered since 2026-08-14T11:50:46.984Z. We have identified the data that is causing…

Outage history

Past 90 days · 4 incidents View full outage history →