HIVE80lab — Ops notes

Vendor Incident Contact Matrix

Purpose: Centralized vendor contact matrix for incident response. Know who to call, how to reach them, and what to expect.

Vendor Matrix Overview

VendorTierProduct/ServiceOn-CallEmailPhonePagerDutySLA ResponseSLA Compensation
StripeTier 1Payment GatewaySupportsupport@stripe.com+1 (855) 641-2193Stripe-P115 minCredit per SLA violation
SendGridTier 1Email ServiceSupportsupport@sendgrid.com+1 (855) 481-7446SendGrid-P115 minRefund unused credits
CloudFlareTier 1CDN / DDoS Protection24/7 Support24x7@cloudflare.com1-844-933-1553CloudFlare-P115 minCredit per SLA violation
AWSTier 2Cloud InfrastructureGlobal Supportsupport@aws.amazon.com1-800-767-1727AWS-P130 minService credits
VercelTier 2Frontend Hosting24/7 Supportsupport@vercel.com1-855-973-8355Vercel-P115 minCredits
GumroadTier 2Payment / OrdersSupportsupport@gumroad.com[internal]Gumroad-P115 minService credits
DatadogTier 1MonitoringSupportsupport@datadoghq.com1-855-252-2362Datadog-P115 minCredits
New RelicTier 1MonitoringSupportsupport@newrelic.com1-855-207-6061NewRelic-P115 minCredits
SentryTier 1Error TrackingSupportsupport@sentry.io1-415-795-3566Sentry-P115 minCredits
IntercomTier 1Customer SupportSupportsupport@intercom.com1-888-330-9241Intercom-P115 minCredits
ZendeskTier 2Customer Support24/7 Supportsupport@zendesk.com1-888-888-8247Zendesk-P130 minCredits
CloudinaryTier 2Media HostingSupportsupport@cloudinary.com1-310-909-3173Cloudinary-P115 minCredits

Vendor Categories

Tier 1: Critical Infrastructure Vendors

Products/Services: Payments, CDNs, DDoS protection, monitoring, error tracking

VendorOn-CallPagerDutySLAEscalation Path
StripeSupportStripe-P115 minPagerDuty → VP Engineering
SendGridSupportSendGrid-P115 minPagerDuty → VP Engineering
CloudFlare24/7 SupportCloudFlare-P115 minPagerDuty → VP Engineering
DatadogSupportDatadog-P115 minPagerDuty → VP Engineering
New RelicSupportNewRelic-P115 minPagerDuty → VP Engineering
SentrySupportSentry-P115 minPagerDuty → VP Engineering
IntercomSupportIntercom-P115 minPagerDuty → VP Engineering

Vendor Escalation Rules:

Tier 2: Secondary Infrastructure Vendors

Products/Services: Cloud infrastructure, frontend hosting, media hosting, customer support

VendorOn-CallPagerDutySLAEscalation Path
AWSGlobal SupportAWS-P130 minPagerDuty → SRE Lead
Vercel24/7 SupportVercel-P115 minPagerDuty → SRE Lead
GumroadSupportGumroad-P115 minPagerDuty → SRE Lead
Zendesk24/7 SupportZendesk-P130 minPagerDuty → SRE Lead
CloudinarySupportCloudinary-P115 minPagerDuty → SRE Lead

Vendor Escalation Rules:

Vendor Contact Info

Stripe

SendGrid

CloudFlare

AWS

Vercel

Gumroad

Datadog

New Relic

Sentry

Intercom

Zendesk

Cloudinary

Escalation Protocols

Step 1: Initial Contact

1. Contact method: PagerDuty → Email → Phone 2. Message format: Incident ID, severity, impact, what you need 3. Response time: Vendor SLA target (15 min for Tier 1, 30 min for Tier 2) 4. Observation log: Document time, contact method, response

Step 2: If No Response

1. Escalate to primary on-call: PagerDuty escalates automatically 2. Alternative contact: Try different channel (email vs phone) 3. Check vendor status page: Is the vendor having an outage? 4. Prepare workaround: Can you switch providers?

Step 3: SLA Violation

1. Calculate credit: Vendor SLA violation → credit 2. Document SLA violation: Time, severity, credit amount 3. Notify customer: If customer affected, notify them 4. Track credits: Log in financial system

Step 4: Vendor Performance Review

1. Review SLA violations: How often do they fail? 2. Evaluate alternative providers: Is there a better vendor? 3. Negotiate terms: Update SLA terms if needed 4. Consider switching: If SLA violations are frequent

Vendor Management

Vendor Performance Tracking

VendorSLA Violations (Last 90 days)Response Time AverageCustomer ImpactRatingAction Needed
Stripe[count]____ min[yes/no]Excellent / Good / Needs Improvement[none / review / switch]
SendGrid[count]____ min[yes/no]Excellent / Good / Needs Improvement[none / review / switch]
CloudFlare[count]____ min[yes/no]Excellent / Good / Needs Improvement[none / review / switch]
AWS[count]____ min[yes/no]Excellent / Good / Needs Improvement[none / review / switch]
Vercel[count]____ min[yes/no]Excellent / Good / Needs Improvement[none / review / switch]
Gumroad[count]____ min[yes/no]Excellent / Good / Needs Improvement[none / review / switch]

Vendor Onboarding Process

1. Evaluate vendor: SLA, support quality, pricing 2. Negotiate terms: Ensure SLA terms are documented 3. Onboard vendor: Add to matrix, enable PagerDuty 4. Monitor performance: Track SLA violations, response times 5. Review regularly: Quarterly vendor performance review

Vendor Offboarding Process

1. Evaluate alternatives: Is there a better vendor? 2. Plan migration: Transition away from vendor 3. Notify customers: If vendor is critical, notify customers 4. Switch providers: Migrate to alternative vendor 5. Close vendor: Remove from matrix, archive contacts

Documentation Fields

Vendor SLA Summary

VendorSLA ResponseSLA UptimeCompensation TypeAuto-Credit
Stripe15 min99.9%CreditYes
SendGrid15 min99.9%RefundYes
CloudFlare15 min99.99%CreditYes
AWS30 min99.99%CreditsYes
Vercel15 min99.9%CreditsYes
Gumroad15 min99.9%CreditsYes
Datadog15 min99.99%CreditsYes
New Relic15 min99.99%CreditsYes
Sentry15 min99.99%CreditsYes
Intercom15 min99.9%CreditsYes
Zendesk30 min99.9%CreditsYes
Cloudinary15 min99.9%CreditsYes

Usage: Use during vendor incidents. Contact vendor using the matrix, track SLA violations, and calculate credits. Works with vendor-escalation-protocols.md and customer-vendor-incident-comms.md.

Product links: /l/ops-starter-kit-vol-2 | /l/ops-starter-kit | /l/automation-starter-pack

From the HIVE80lab kit

Part of the five-pillar incident-response set: see the pillars overview and the blameless post-incident review template.