Goroutine Dump Analyzer

It groups every goroutine by its state — running, runnable, IO wait, syscall, chan receive, chan send, select, semacquire and so on — so you can see at a glance where they're spending their time. It clusters goroutines by their top function to surface hot spots, and separately lists goroutines that the runtime reports as blocked for minutes, which is the most reliable signal of a goroutine leak or a stalled channel. Click a state to filter the list.

Several ways: a Go program prints all goroutine stacks when it panics or receives SIGQUIT (Ctrl-\ on Unix); net/http/pprof exposes them at the debug endpoint when you import it; and runtime.Stack or pprof.Lookup with goroutine will write them programmatically. For leak hunting, capture two dumps a minute or two apart — a goroutine count that keeps climbing, with the same functions accumulating, is your leak.

No. The whole analysis runs in your browser — the dump you paste never leaves your device and is sent to no server. Goroutine dumps can reveal internal package names, request details and infrastructure, so keeping them local matters. As an EU-built provider, Uptimeify keeps tools like this client-side so there's nothing to transmit or store.