Tools — Systems lab

Backend failures, made visible.

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. Everything runs in your browser.

Incident debugger

Payment succeeds, invoice missing

Case study

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.

API reliability probe

Check public endpoints

A lightweight reachability check for the domains already on this portfolio. Cross-origin responses are measured as reachable/failed, not inspected.

oakstat.us Idle

easybin.xyz Idle

lorm.pro Idle

uscs.sufi.my Idle

invoice.sufi.my Idle

Webhook simulator

Choose a failure mode

Fintech

HTTP 200 Persist transaction, publish invoice event.

Idempotency key is new, signature is valid, and persistence succeeds.

Log trace explorer

Trace by transaction ID

Transaction ID

12:04:11.018 waiting for trace...

Architecture snapshot

Payment flow boundaries

Click a node

request webhook write logs

System map

Every boundary can fail silently.

Click a node to see where things break in a real payment flow.

Spot the bug

Find the defect

A real-world code smell. Click the line you think is wrong, then read the explanation.

Pick a line to check.

Live status

oakstat.us Uptime Monitoring Checking… easybin.xyz Secure Transfer Checking… lorm.pro Fake Data Toolkit Checking… uscs.sufi.my Signal Transceiver Checking… invoice.sufi.my E-Invoicing Checking…

Reachability measured from your browser. Each product answers within 6s or is marked down.

Demos