Twilio Segment Data Ingestion API SLATwilio · Observability · Twilio · Observability
Promise vs reality
Not enough status history yet. How this is measured
All incidents, weighted: 99.63% · Downtime- Promised
- 99.99%
- Observed, 365d
- n/a
- Major incident time
- n/a
- Credit on first breach
- n/a
Commitments and credits
- Segment customersidentify, track, page, screen, group and alias endpoints99.99%
Monthly uptime below, credit of the bill
No credit schedule published for this tier.
Terms
- Measured
- Calendar month, per-minute basis
- Claim window
- Exercise the termination right within thirty (30) days of becoming aware of the failure
- How to claim
- Written notice to Twilio
Not covered
- Use not authorized in Segment Documentation
- General Internet problems, force majeure, DoS attacks, third-party outages
- Customer or vendor infrastructure
- Scheduled maintenance (max 5 hours/month) or emergency maintenance
"Target Availability" means the Data Ingestion API being available and operational to Customer with a threshold of 99.99%, calculated on a calendar month, per-minute basis.
No service credits. The only remedy is a Special Termination Right after missing target in 2 consecutive months or 3 of 6 consecutive months, with a refund of prepaid fees.
Evidence: incidents, last 365 days
No incidents on file for this service.
Other observability SLAs
ServiceDowntime vs allowed
Promised in the SLAObserved on the vendor's status pagePartial historyShortfall
Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.