Is Siit down?
Last checked just nowNo incidents right now.
Siit is operational right now. Last checked just now; the most recent incident resolved 2d 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 3 incidents in the last 90 days (97.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Siit reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- 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 …
-
- Customer PortalPublic API & MCPAdmin Dashboard
Timeline · 5 updates
- investigating · Jul 21, 2026, 09:00 AM UTC
Status: Investigating We are currently investigating higher than usual response times Affected components Admin Portal (Degraded performance) API (Degraded performance) Management Portal (Degraded performance)
- identified · Jul 21, 2026, 09:13 AM UTC
Status: Identified Our main database is under heavy load and is taking higher than usual time to process queries, auto-scaling is working to compensate but we're still investigating what caused the issue on the first place. Affected components Admin Portal (Degraded performance) API (Degraded performance) Management Portal (Degraded performance)
- identified · Jul 21, 2026, 09:45 AM UTC
Status: Identified we are still working on fixes to prevent the burst from happening again but our DB metrics are back to normal Affected components Admin Portal (Operational) API (Operational) Management Portal (Operational)
- monitoring · Jul 21, 2026, 03:53 PM UTC
Status: Monitoring A fix has been deployed and we'll keep monitoring for the next few days Affected components Admin Portal (Operational) API (Operational) Management Portal (Operational)
- resolved · Jul 22, 2026, 07:52 AM UTC
Status: Resolved Incident is resolve, we'll keep monitoring tightly for response times Affected components Admin Dashboard (Operational) Public API & MCP (Operational) Customer Portal (Operational)
Latest: Status: Resolved Incident is resolve, we'll keep monitoring tightly for response times Affected components Admin Dashboard (Operational) Public API & MCP (Operational) Customer Por…
-
- AI Agents
Timeline · 3 updates
- identified · May 27, 2026, 03:32 PM UTC
Status: Identified We see a high number of errors due to an issue is currently affecting OpenAI, impacting customers running on its models (cf https://status.openai.com/incidents/01KSMYEEWP0BZYANSMAXWJ3K59) Affected components Chatbot & AI (Degraded performance)
- monitoring · May 27, 2026, 04:23 PM UTC
Status: Monitoring The provider applied corrective actions and we are noticing a big decrease in the error response Affected components Chatbot & AI (Degraded performance)
- resolved · May 27, 2026, 10:26 PM UTC
Status: Resolved We haven't seen any error popping for a while and the provider's incident is closed as well. Affected components Chatbot & AI (Operational)
Latest: Status: Resolved We haven't seen any error popping for a while and the provider's incident is closed as well. Affected components Chatbot & AI (Operational)
-
- Started Jul 29, 2026, 03:41 PM UTC · Resolved Jul 29, 2026, 03:41 PM UTC · —
- Slow response time from our servers ResolvedStarted Jul 22, 2026, 07:52 AM UTC · Resolved Jul 22, 2026, 07:52 AM UTC · —
- Issues affecting OpenAI models ResolvedStarted May 27, 2026, 10:26 PM UTC · Resolved May 27, 2026, 10:26 PM UTC · —