Incident debugger
Payment succeeds, invoice missing
Step through the failure chain from gateway webhook to database timeout.
Start
Webhook received
Razorpay delivered the payment event and the endpoint returned HTTP 200.
Tools — Systems lab
Small interactive demos of the problems that show up in real payment systems: a webhook that returns 200 while the write fails, duplicate events, bad signatures, and silent database timeouts, plus retry storms and rate limiting. Everything runs in your browser.
Incident debugger
Step through the failure chain from gateway webhook to database timeout.
Start
Razorpay delivered the payment event and the endpoint returned HTTP 200.
API reliability probe
A lightweight reachability check for the domains already on this portfolio. Cross-origin responses are measured as reachable/failed, not inspected.
Webhook simulator
Idempotency key is new, signature is valid, and persistence succeeds.
Log trace explorer
12:04:11.018 waiting for trace...
Architecture snapshot
Click a node to see where things break in a real payment flow.
Spot the bug
A real-world code smell. Click the line you think is wrong, then read the explanation.
Retry storm
200 clients hit a service that is down until t = 4 s. Compare how each retry strategy loads it when it recovers. Seeded, so every run is identical.
0 s
Pick a strategy and press Run.
Rate limiter
Steady traffic of 6 requests/s. A request takes one token; with none left it gets HTTP 429. Hit Burst to see the bucket absorb a spike.
Live status
Reachability measured from your browser. Each product answers within 6s or is marked down.