Observed arrival · 2026-09-22
Slussen: adaptive throttling for APIs you do not control
Slussen measures how much traffic a destination can absorb, then regulates delivery and backs off when latency or 429 responses rise.
○Open
⊠Login
$Paid
†Ads
✦Pretty
●Pro
◎Niche
◉Human
⚑Risk
ƒJS
- For
- Teams delivering webhooks to unpredictable customer systems
- Worth noticing
- The page contrasts 990 rejected events sent directly with 1,000 delivered through its adaptive rate policy.
Field notes
The homepage frames throttling as a destination-specific measurement problem rather than a fixed sender-side setting. Its example compares the same 1,000-event burst under two paths: direct delivery produces 990 rejected events, while the regulated path spreads arrival over 199 seconds and reports no rejection or loss. The page also describes latency and HTTP 429 responses as signals for backing off when the destination’s capacity changes.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
○OpenPublic substance visible
✦PrettyNotable craft visible
●ProPolished or operationally mature
◎NicheUnusually specific use
One card from the complete issue