Check your stack: is it you, or is it your vendors? | OutageDeck<br>Skip to content<br>Search⌘KBrowse providers
Check your stack<br>Checked Aug 8, 2026, 7:50 PM UTC<br>Pick the vendors your product depends on<br>Choose your stack below to get one live answer instead of a dozen open status pages. Nothing is stored, and the link is shareable.<br>Or start from a common stack<br>Modern web appAWS shopAI productTeam tools<br>Or paste your package.jsonDependencies are matched to tracked vendors in your browser. The file is never uploaded.<br>Build my board
Choose your vendors<br>Up to 12 providers. Nothing is saved; the selection lives in the link.
0 / 12 selected
Filter providers<br>AWS<br>Azure<br>Google Cloud<br>Cloudflare<br>GitHub<br>OpenAI<br>Vercel<br>Supabase<br>DigitalOcean<br>Slack<br>Anthropic<br>Zoom<br>Notion<br>Discord<br>Datadog<br>Netlify<br>Twilio<br>Figma<br>Canva<br>Reddit<br>Linear<br>Jira<br>Bitbucket<br>Confluence<br>Trello<br>Google Workspace<br>Firebase<br>Dropbox<br>Twitch<br>Coinbase<br>Shopify<br>npm<br>PyPI<br>Sentry<br>MongoDB Atlas<br>CircleCI<br>Fly.io<br>Render<br>Cursor<br>Heroku<br>SendGrid<br>Auth0<br>HubSpot<br>Mailgun<br>Segment<br>LaunchDarkly<br>Snowflake<br>Kraken<br>Box<br>1Password<br>Tailscale<br>Postman<br>PlanetScale<br>Elastic Cloud<br>Plaid<br>Groq<br>Replicate<br>Cohere<br>ElevenLabs<br>RubyGems<br>Linode<br>Scaleway<br>Akamai<br>OVHcloud<br>CockroachDB Cloud<br>Confluent Cloud<br>Upstash<br>Resend<br>Cloudinary<br>New Relic<br>Grafana Cloud<br>Asana<br>monday.com<br>Airtable<br>Docusign<br>Calendly<br>Zapier<br>Squarespace<br>Wix<br>GoDaddy<br>Kinsta<br>Amplitude<br>Klaviyo<br>Typeform<br>Webflow<br>Clerk<br>WorkOS<br>Pinecone<br>Temporal Cloud<br>Retool<br>Make<br>Mixpanel<br>Brevo<br>Vimeo<br>Cloudsmith<br>Loom<br>Vonage<br>Telnyx<br>Plivo<br>Sinch<br>Bird (MessageBird)<br>Infobip<br>Bandwidth<br>Dialpad<br>GoTo<br>Aircall<br>Nextiva<br>Hologram<br>emnify<br>Cisco Duo<br>JumpCloud<br>Ping Identity<br>FusionAuth<br>Frontegg<br>Snyk<br>Vanta<br>Doppler<br>Oracle Cloud (OCI)<br>Incorta<br>ClickHouse Cloud<br>Astronomer<br>Prefect<br>Starburst Galaxy<br>Dremio<br>InfluxDB Cloud<br>Neo4j Aura<br>Couchbase Capella<br>Cloudera<br>Sisense<br>Hex<br>Metabase<br>Aiven<br>Materialize<br>Statuspage<br>Opsgenie<br>Kong<br>Buildkite<br>Harness<br>HashiCorp Cloud<br>GitLab<br>Docker<br>NetSuite<br>Proton<br>OpenVPN<br>SentinelOne<br>ESET<br>Palo Alto Networks<br>Check Point<br>KnowBe4<br>Qualys<br>Tenable<br>Rapid7<br>Wiz<br>Imperva<br>Keeper Security<br>Ubiquiti<br>Cisco Meraki<br>Travis CI<br>Codecov<br>JFrog<br>Octopus Deploy<br>Semaphore<br>Pulumi<br>Bitrise<br>Sauce Labs<br>BrowserStack<br>ngrok<br>ReadMe<br>Perplexity<br>Stytch<br>Kinde<br>Airbyte<br>Check this stackClear<br>How this answers the question<br>OutageDeck re-reads the official status feed of all 172 tracked providers about every 10 minutes and stores what it finds. This board simply shows you the subset you chose. A green stack is a real statement (every one of those vendors is publicly claiming to be fine right now), and a red one gives you the incident to link in your own status update. Browse every tracked provider or set up alerts so the next one finds you instead.<br>Want this board somewhere your team already looks? Turn it into a status wall: one line of Markdown for a README, wiki, or dashboard, and it keeps itself current.<br>Using a coding agent? The same verdict is one tool call away: connect the MCP server and your agent can ask "is it us or them?" mid-task, before it starts tearing apart your code.<br>A stack board holds up to 12 vendors and nothing about it is stored. Reload it, bookmark it, or paste it into your incident channel.