> ## Documentation Index > Fetch the complete documentation index at: https://docs.webhook.co/llms.txt > Use this file to discover all available pages before exploring further. # Reliability > How webhook.co protects your events end to end — durable capture, at-least-once delivery, automatic retries, and dead-lettering. Here's how webhook.co is built to hold onto your events, so a hiccup on any side doesn't lose them. A request that reaches your ingest URL is written down **before** it's verified or processed. A bad signature, an unknown provider, or a downstream outage labels an event — it doesn't discard it. Outbound events are delivered at least once, with automatic retries on a fixed schedule and **dead-lettering** when a receiver stays down — so a brief outage on your side doesn't drop events. A delivery counts once, when first dispatched — however many retry attempts it takes. A receiver's downtime is never your cost. Every captured event stays replayable within your [retention window](/help/usage/data-retention) — recover from an outage by replaying, instead of asking the provider to resend. webhook.co runs on a best-effort basis and doesn't publish an uptime or service-level guarantee. What it does provide is the durability model above: your captured events are safe to inspect and replay, and delivery keeps retrying rather than dropping. ## Related The retry schedule and dead-lettering in detail. When something doesn't get through.