Is Siit down?

Last checked 6m ago
Current status
Siit is up

No incidents right now.

Official status page: https://status.siit.io · Polled every 5 minutes · 4 components tracked

Siit is operational right now. Last checked 6m ago; the most recent incident resolved 4d ago.

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

Users who monitor Siit also follow these Project Management services: Atlassian Jira Software Trello Asana Incident IQ Notion Shortcut Jira Service Management LaunchDarkly Basecamp View all 6,000+ providers
Siit uptime 94.44% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Sep 10, 2026, 03:21 PM UTC · Resolved Sep 10, 2026, 03:21 PM UTC
    Customer PortalPublic API & MCPAdmin DashboardAI Agents
    Timeline · 3 updates
    • investigating · Sep 10, 2026, 02:32 PM UTC

      Status: Investigating We are experiencing an issue with our infra and our team is on it Affected components Admin Dashboard (Partial outage) Public API & MCP (Partial outage) AI Agents (Partial outage) Customer Portal (Partial outage)

    • monitoring · Sep 10, 2026, 02:43 PM UTC

      Status: Monitoring We have deployed a fix and are monitoring Affected components AI Agents (Operational) Customer Portal (Operational) Admin Dashboard (Operational) Public API & MCP (Operational)

    • resolved · Sep 10, 2026, 03:21 PM UTC

      Status: Resolved This incident is now resolved. It was caused by an infrastructure configuration change that had unintended side effects. The change has been rolled back and we've added safeguards so it can't happen again. Apologies for the disruption and thank you for your patience. Affected components Admin Dashboard (Operational) Public API & MCP (Operational) AI Agents (Operational) Customer Portal (Operational)

    Latest: Status: Resolved This incident is now resolved. It was caused by an infrastructure configuration change that had unintended side effects. The change has been rolled back and we've …

  2. Resolved
    Started Sep 02, 2026, 08:41 AM UTC · Resolved Sep 02, 2026, 08:41 AM UTC
    AI Agents
    Timeline · 2 updates
    • identified · Sep 01, 2026, 01:42 PM UTC

      Status: Identified We are seing an unusualy elevated error rate response from one of our LLM provider (OpenAI), our own AI agents are impacted Affected components AI Agents (Degraded performance)

    • resolved · Sep 02, 2026, 08:41 AM UTC

      Status: Resolved We haven't received such errors for the past 12h on OpenAI's LLM Affected components AI Agents (Operational)

    Latest: Status: Resolved We haven't received such errors for the past 12h on OpenAI's LLM Affected components AI Agents (Operational)

  3. Resolved
    Started Sep 01, 2026, 06:12 PM UTC · Resolved Sep 01, 2026, 06:12 PM UTC
    Customer PortalPublic API & MCPAdmin DashboardAI Agents
    Timeline · 3 updates
    • investigating · Sep 01, 2026, 11:58 AM UTC

      Status: Investigating We are investigating an increase in latency Affected components Customer Portal (Degraded performance) Admin Dashboard (Degraded performance) Public API & MCP (Degraded performance) AI Agents (Degraded performance)

    • monitoring · Sep 01, 2026, 12:29 PM UTC

      Status: Monitoring Infrastructure is back to "normal" state - we are still working on improving the delay to resorb such spikes even more. Timeline (CEST): 13:51 - issues affecting our read cluster started pilling up 13.56 - Autoscalers started kicking in 14:01 - Autoscalers fully resorbed the issue Affected components Admin Dashboard (Operational) Public API & MCP (Operational) AI Agents (Operational) Customer Portal (Operational)

    • resolved · Sep 01, 2026, 06:12 PM UTC

      Status: Resolved The issue didn't reproduce - we implemented a few counter mesure for future occurences. Affected components Admin Dashboard (Operational) Public API & MCP (Operational) AI Agents (Operational) Customer Portal (Operational)

    Latest: Status: Resolved The issue didn't reproduce - we implemented a few counter mesure for future occurences. Affected components Admin Dashboard (Operational) Public API & MCP (Operati…

  4. Resolved
    Started Aug 27, 2026, 11:05 AM UTC · Resolved Aug 27, 2026, 11:05 AM UTC
    Customer PortalPublic API & MCPAdmin DashboardAI Agents
    Timeline · 4 updates
    • investigating · Aug 27, 2026, 07:50 AM UTC

      Status: Investigating We are investigating why our job processing are being much slower than usual Affected components Admin Dashboard (Degraded performance) Public API & MCP (Degraded performance) AI Agents (Partial outage) Customer Portal (Degraded performance)

    • identified · Aug 27, 2026, 08:00 AM UTC

      Status: Identified we have identified the issue and are working on resolving it asap Affected components Admin Dashboard (Degraded performance) Public API & MCP (Degraded performance) AI Agents (Partial outage) Customer Portal (Degraded performance)

    • monitoring · Aug 27, 2026, 08:30 AM UTC

      Status: Monitoring Our metrics are back to normal, we are still implementing more safeguards in the meantime while we keep monitoring Affected components AI Agents (Operational) Customer Portal (Operational) Admin Dashboard (Operational) Public API & MCP (Operational)

    • resolved · Aug 27, 2026, 11:05 AM UTC

      Status: Resolved We have resolved the incident and improved some of our infra to lower the risk of it happening again with those conditions. Affected components AI Agents (Operational) Customer Portal (Operational) Admin Dashboard (Operational) Public API & MCP (Operational)

    Latest: Status: Resolved We have resolved the incident and improved some of our infra to lower the risk of it happening again with those conditions. Affected components AI Agents (Operatio…

  5. Resolved
    Started Jul 29, 2026, 03:41 PM UTC · Resolved Jul 29, 2026, 03:41 PM UTC
    Admin Dashboard
    Timeline · 4 updates
    • identified · Jul 29, 2026, 01:49 PM UTC

      Status: Identified We are investigating an issue of old Zendesk messages from existing Siit threads being re-imported following a fix we recently pushed. This issue only affects messages with attachments, we are working on a fix and we'll keep you update. Affected components Admin Dashboard (Degraded performance)

    • identified · Jul 29, 2026, 02:39 PM UTC

      Status: Identified After thorough investigation the blast radius has been identified to only a handful of customers, you should receive a message shortly after the fix is pushed explaining the impact. A fix is being pushed shortly to avoid those conditions occurring again - we'll also run a cleanup of the few affected requests (~80). Important: no data was lost or exposed. The re-imported messages came from your own tickets and were only ever visible to people who already had access to the requests in question. Unfortunately, Slack notifications that were already sent cannot be recalled. Affected components Admin Dashboard (Operational)

    • monitoring · Jul 29, 2026, 03:09 PM UTC

      Status: Monitoring The fix is currently being pushed Affected components Admin Dashboard (Operational)

    • resolved · Jul 29, 2026, 03:41 PM UTC

      Status: Resolved Post mortem What happened: We received a report of old integration comments surfacing on stale requests at 13:39 UTC today, after investigation, and until the fix was shippe (between 2026-07-29 13:30:08 UTC to 2026-07-29 15:12:06 UTC) a handful of customers were impacted. Why it happened: following a sync-configuration update on our ticketing integrations (Jira, Intercom…), our synchronization provider re-delivered historical comments from your tickets. Some of these old comments were re-imported as new messages on the affected requests, specifically on customers that had previously removed / re-plugged their ticketing integration. What we did: A fix has been shipped live shortly after: historical comments can no longer be re-imported as new messages, and the import pipeline is now protected against this kind of re-delivery. We've also run a cleanup of the duplicated data. We'll contact the affected customer shortly with final number on affected imported messages. We're sorry for the inconvenience. Affected components Admin Dashboard (Operational)

    Latest: Status: Resolved Post mortem What happened: We received a report of old integration comments surfacing on stale requests at 13:39 UTC today, after investigation, and until the fix …

See the full Siit outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Siit outage history →

Or sign up free to get alerts when Siit breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 6 incidents View full outage history →