Skip to content

Commit 9412206

Browse files
committed
rate limit SLA article Added
placed at bottom of Connections list in side nav
1 parent 53117c3 commit 9412206

File tree

2 files changed

+21
-0
lines changed

2 files changed

+21
-0
lines changed

src/_data/sidenav/main.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -225,6 +225,8 @@ sections:
225225
title: Integration Error Codes
226226
- path: /connections/schema-unique-limits
227227
title: Are there limits on my Segment Schema?
228+
- path: /connections/rate-limits
229+
title: Rate Limits and SLA
228230
- section_title: Personas
229231
section:
230232
- path: /personas

src/connections/rate-limits.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: Rate Limits and SLA
3+
---
4+
Segment limits the number of both inbound and outbound requests in order to ensure overall system stability.
5+
6+
## Inbound Data Ingestion API Rate Limit
7+
8+
Segment allows customer sources to send up to 60,000,000 events within any 10 minute period (an average of 100,000 events per second). If, without prior arrangement, Segment reserves the right to queue any events that exceeed this threshold, and process those at a rate that does not exceed 60,000,000 events in a 10 minute period.
9+
10+
## Outbound Downstream
11+
12+
Most destinations have their own rate limits that are outside of Segment's control. In some instances, Segment can inngest and attempt to deliver data faster than the downstream destination can accept that data.
13+
14+
Outbound requests to a destination can also fail for other reasons that are outside of Segment's control. When requests to a downstream destination fail, Segment makes subsequent attempts to deliver the data.
15+
16+
However, Segment reserves the right to limit or reduce the number of retry attempts until the issue is resolved if either of the following conditions are met:
17+
18+
- Failed requests to a downstream destination exceed 1,000 per second
19+
- The failure rate exceeds 50% for more than 72 hours

0 commit comments

Comments
 (0)