Breaking

Open now

Resolved in the last 3 days

Freshness

Time from a provider publishing an update to Spike recording it, last 24 hours: median 1 min, 95th percentile 30 min over 88 updates. Every provider is read every minute, directly from its status page. Status pages show what providers choose to publish; a provider can be slow to post, which no monitor can see.

Sources

ProviderCategoryLast checkedOpen
✅ Amazon Web ServicesCloud0
✅ Microsoft AzureCloud0
✅ Google CloudCloud0
✅ CloudflareNetwork and CDN2
✅ AkamaiNetwork and CDN3
✅ DigitalOceanCloud1
✅ NetlifyCloud0
✅ GitHubDeveloper platforms0
✅ npmDeveloper platforms0
✅ AtlassianDeveloper platforms0
✅ SentryDeveloper platforms0
✅ SalesforceBusiness software0
✅ HubSpotBusiness software0
✅ ZoomCommunications0
✅ TwilioCommunications5
✅ DiscordCommunications0
✅ MailgunCommunications0
✅ DropboxBusiness software0
✅ BoxBusiness software0
✅ FigmaBusiness software0
✅ Cisco DuoIdentity and access0
✅ 1PasswordIdentity and access0
✅ SquarePayments and finance0
✅ ShopifyPayments and finance0
✅ PlaidPayments and finance0
✅ CoinbasePayments and finance2
✅ WisePayments and finance0
✅ MarqetaPayments and finance0
✅ FireblocksPayments and finance0
✅ MongoDB AtlasData platforms1
✅ SnowflakeData platforms0
✅ Elastic CloudData platforms1
✅ OpenAIAI platforms0
✅ AnthropicAI platforms0

Spike Evidence Brief: paste a provider incident link or an alert and get a sourced, versioned handoff. For developers: /api/v1/incidents · change feed · OpenAPI. Spike Pro workspaces can list the vendors they depend on and get each change, with why it matters, in Slack, Teams, email or a signed webhook.