incident.io
incident.io declares 20 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Google Cloud, OpenAI and Microsoft. The list last changed on Nov 2, 2026: 1 added, 1 removed. 21 tracked vendors name incident.io as a subprocessor, including turbopuffer, Paddle and Honeycomb.
Not loaded by any published homepage.
Subprocessors CSV of incident.io's subprocessors · Atom feed of incident.io's subprocessors DORA draft CSV of incident.io's subprocessors as declared by incident.io what's this? ·
20 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Anthropic AI | Artificial Intelligence Provider | United States | |
| ElevenLabs AI | Transcription | United States | |
| Fivetran | Analytics Infrastructure Provider | United States | |
| Cloud Infrastructure | European Regions | ||
| Hex | Data Analytics Tool | United States | |
| Merge.dev | To manage employee on-call coverage | United States | |
| Microsoft Teams (for clients using Microsoft Teams as their Communications Platform) | Customer Support | United Kingdom | |
| Omni | Data Analytics Tool | United States | |
| OpenAI AI | Artificial Intelligence Provider | United States | |
| Planhat | Account Management Support | European Regions | |
| Pylon | Customer Support | United States | |
| Recall | Transcription | United States | |
| Sentry | Exception Tracking | United States | |
| Slack | Customer Support | United States | |
| Svix | Send Product Webhooks | United States | |
| Telnyx | SMS, Phone and email notifications | United States | |
| Temporal | Workflow Orchestration | European Regions | |
| Twilio | SMS, Phone and email notifications | United States | |
| WhatsApp Business Platform (operated by Meta Platforms, Inc.) | To send/receive on-call notifications | United States | |
| WorkOS | SCIM/SAML Authentication Flows | United States |
Web TechnologiesCSV of incident.io's web technologies · Atom feed of incident.io's web technologies
incident.io's homepage made 217 requests to 30 domains, 15 services controlled by another company, and 2 domains not identified.
15 third parties by category: Advertising 4Analytics 4Marketing automation 2Live chat 1Cookie compliance 1Other 3
cr-relay.comusbrowserspeed.com
7 tracked companies loaded by the homepage are not in incident.io's subprocessor list. A website can use a service without it processing customer data.
Subprocessor of (21)CSV of the companies listing incident.io · Atom feed of the companies listing incident.io
Aiven aiven.io
ArborXR arborxr.com Incident Management and Status Page
Doozy doozy.live Operational monitoring and alerts
Fiddler AI fiddler.ai Operational incident management
FINBOURNE finbourne.com
Fly.io fly.io Incident response and on-call management
FundApps fundapps.co
Hasura hasura.io
Honeycomb honeycomb.io Incident tracking and response
Infracost infracost.io Incident management, used internally to detect, manage, and resolve operational incidents affecting our platform.
Jimdo jimdo.com
Lago getlago.com Incident management, alerting, and on-call scheduling. Processes internal operational data only.
Paddle paddle.com Paddle's platform for on-call, incident response, and status page.; Status Page
Reducto reducto.ai Incident management, operational communications, and alerts; Operational incident-management subprocessor; may process alerts, debugging context, and customer metadata. No customer document content by design.
Restate restate.dev Alerting and incident management, public service status; Incident Response
Tella tella.tv To manage incidents and investigate issues in our production systems, including with its AI assistant.
Tinybird tinybird.co Ltd. incident management tool used to alert Tinybird’s on-call team of incidents
turbopuffer turbopuffer.com Production monitoring and alerting
Unify unifygtm.com Incident Management; Used to coordinate our incident response and on-call. Stores limited customer data referenced while diagnosing issues.
Vasco vasco.app Operations
Zuplo zuplo.com
ComplianceCSV of incident.io's compliance · Atom feed of incident.io's compliance
- Certified
- Says it complies with
Certifications as incident.io's trust center lists them; reports are usually shared on request (evidence)
Service statusCSV of incident.io's status page incidents · Atom feed of incident.io's status page incidents
90 days agotoday
- 5 incidents in 90 days
- 1 major or critical
- 1 h 56 min typical time to resolve
- 4 h 24 min longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Disruption to Slack incident channels and messages | major | 4 h 24 min | |
| Sentry integration degraded | minor | 1 h 56 min | |
| Login errors for subset of Slack Enterprise Grid customers | minor | 1 h 13 min | |
| Increased latency in Microsoft Teams | minor | 1 h 48 min | |
| Issue with listing alerts in the public API and dashboard | minor | — | |
| Delays in webhooks from Opsgenie | minor | 1 h 7 min | |
| AI features degraded | major | — | |
| Issues affecting login with SAML | critical | 2 h 22 min |
Incidents per month
critical major minor no impact stated
As incident.io's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by incident.io's subprocessorsCSV of incidents reported by vendors incident.io lists · Atom feed of incidents reported by vendors incident.io lists
313 reported incidents in the last 30 days, by 12 of the vendors incident.io lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that incident.io was involved.
And 288 more. All of them: CSV · Who is around them.
ChangesCSV of incident.io's changes · Atom feed of incident.io's changes
See the list as we read it on any date: Time machine
- Removed subprocessor: Explo evidence: subprocessor: Explo list before and after: subprocessor: Explo
- Added subprocessor: Temporal evidence: subprocessor: Temporal list before and after: subprocessor: Temporal