Subprocessors

Last updated

Instatus uses the third-party subprocessors below to provide the Service. Each one only receives the data it needs for the purpose listed, and each has signed data processing terms with us that are at least as protective as our Data Processing Addendum. Where a subprocessor is outside the EEA, UK or Switzerland, transfers are protected by the EU Standard Contractual Clauses or another lawful mechanism.

Our primary data store is in the United States: Amazon Web Services in Ohio (us-east-2) and North Virginia (us-east-1).

Infrastructure

SubprocessorPurposeLocation
Amazon Web Services, Inc.Primary hosting: application servers, primary database, queues, file storage, backups and email sending (Amazon SES)United States
Vercel Inc.Hosting and edge delivery for status pages, the dashboard and our websites, including custom domainsUnited States, with a global edge network
Cloudflare, Inc.Network security, DDoS protection and delivery for our APIUnited States, with a global edge network
Hetzner Online GmbHServers that run monitoring checks and background workersEuropean Union, United States, Asia
ClickHouse, Inc.Database for monitoring results and team activity logsUnited States
Redis Ltd.Caching and job queuesUnited States
Temporal Technologies, Inc.Workflow scheduling for on-call escalations and incident automationsUnited States
Backblaze, Inc.Storage of monitor response bodies and app feedback attachmentsUnited States
Cloudinary Ltd.Storage and delivery of uploaded images and incident attachmentsUnited States
SimpleBackupsRunning scheduled database backups, which are stored in our own AWS accountUnited States

Notifications

SubprocessorPurposeLocation
Mailgun Technologies, Inc.Sign-in emails, backup email delivery, and receiving alert emails from monitoring toolsUnited States
Twilio Inc.Phone call alerts to on-call team membersUnited States
650 Industries, Inc. (Expo)Push notifications to the Instatus mobile apps, delivered through Apple Push Notification service and Firebase Cloud MessagingUnited States

Subscriber SMS messages and emails sent through your own provider account (for example your own Twilio, Vonage or SendGrid account) are processed by that provider under your agreement with it. They are not our subprocessors.

AI

These providers power AI features that are part of the Service. Some run automatically: incident summaries are refreshed whenever an incident changes, status page content is translated into the languages your page offers, and subscriber imports and new status pages are checked for abuse. Others run when you use them, such as drafting updates or answering questions in the dashboard, Slack and Microsoft Teams. The data sent can include incident content and timelines, responder names, monitor context and subscriber email domains. Providers process it only to return a result to us and are contractually prohibited from training their models on it.

SubprocessorPurposeLocation
Anthropic, PBCTranslation, the dashboard assistant and AI status page designsUnited States
Google LLC (Gemini API)Incident summaries, chat replies in Slack and Teams, and checks that protect subscriber imports from abuseUnited States

Accounts, billing and support

SubprocessorPurposeLocation
WorkOS, Inc.Multi-factor authentication, Google sign-in and earlier SSO connectionsUnited States
Paddle.com Market LimitedReseller and Merchant of Record: payments, tax and invoicesUnited Kingdom
Urlbox Ltd.Creating PDF copies of invoicesUnited Kingdom
Help Scout PBCCustomer support conversationsUnited States
Intuition Machines, Inc. (hCaptcha)Bot protection on sign-up, sign-in and status page subscribe formsUnited States
PostHog, Inc.Feature flags for rolling out new featuresUnited States
SmartBear Software, Inc. (Bugsnag)Error monitoring for our web appsUnited States

SAML single sign-on and SCIM directory sync are provided by OrbitID, a product operated by Instatus, Inc. and covered by the same commitments.

Integrations you turn on

When you connect a third-party service, such as Slack, Microsoft Teams, Discord, Google Chat, X, Zapier, PagerDuty, Jira, Datadog, Intercom, Zendesk, WhatsApp, your own email or SMS provider, or a webhook, we send it the data needed for that integration on your instruction. These services work under their own terms with you and are not Instatus subprocessors. Turning an integration off stops the data flow.

Get notified about changes

We give at least 30 days' notice before a new subprocessor starts processing customer data, as described in section 5 of our DPA. To get these notices by email, write to privacy@instatus.com with the subject "Subscribe to subprocessor updates". Every change is also recorded on our policy updates page.