Twitch buffering: is it you or Twitch?
The player buffers and the question shows up instantly: is it me, Twitch or my ISP? Without records you can argue. With records you can compare.
The three cases leave different traces
Router steady while external targets fail in the same window: the failure is beyond your PC. Everything wobbling together, router included: the local path becomes a suspect. Network steady with only the player buffering: the problem may be on the video path.
If the PC itself was downloading or uploading a lot during a spike, the report says that traffic can explain the buffering, before you blame Twitch or your ISP.
1. Leave the recorder running
It measures the router, three external destinations, DNS lookups and HTTPS checks while the PC is on. The DNS lookups ask for the address of www.twitch.tv, through the system resolver and directly through two public servers on different networks, 1.1.1.1 and 8.8.8.8. There's nothing to open before the stream.
2. Install and connect the extension
The extension is optional and needs Something Just Lagged running on the same PC. In Firefox, install it from Mozilla Add-ons. In Chrome or Edge, load the extension folder included with the app. Then copy the pairing code from the dashboard and paste it into the extension. After the free trial, connecting the extension requires a license.
Haven't installed the app yet? Download the Windows app.
Firefox 140+ (desktop)
Install the extension from Mozilla Add-ons
This installation stays after restarting Firefox; you do not need to load a temporary add-on.
Chrome or Edge 120+: manual installation
- In Chrome, copy chrome://extensions into the address bar. In Edge, use edge://extensions.
- Turn on Developer mode and click Load unpacked.
- Select the extension folder that comes with the app, not a ZIP. For a standard installation, copy this path into the folder picker:
%LOCALAPPDATA%\SomethingJustLagged.Desktop\current\extension
Connect to the app and check
For Firefox, the dashboard may still show instructions for loading a temporary add-on. Those instructions are for testing the unsigned local package. If you installed from Mozilla Add-ons, skip that loading step and just copy the pairing code; do not install a second extension.
- In the tray icon menu near the clock, choose Open dashboard. Under Twitch in your browser, open Connect the browser extension and click Copy pairing code.
- Open the extension icon, paste that code and click “Conectar ao programa” (Connect to the app). The code is not your license: it is a local key and should not be shared.
- Allow access to Twitch sites if the browser asks. Reload the Twitch tab and watch a live stream. With the app recording, the popup should show “Conectado” (Connected) and accepted events.
The extension popup is in Portuguese. If it shows “Conexão indisponível” (Connection unavailable), check that the app is running, copy a current pairing code from the dashboard and connect again.
The extension checks the Twitch player every two seconds: whether it is playing or waiting, how many seconds of video are buffered and how many frames were dropped. It also notes how long each media request took and whether it failed.
3. Press Ctrl+Alt+L when it buffers
The lag is saved right away, with the 5 minutes before and the 2 after, without opening a window. Then, from the notification, choose Twitch buffering and, if you like, say when the problem started: when you marked it, 30 s or 1 min before, or another time. The end, only if you know it. Without that start, the analysis looks at the 15 seconds on either side of the mark.
4. Read the report
The report says whether the router and the external destinations answered at the moment of the buffering. With the extension, it also shows the lowest video buffer, the dropped frames, the media requests that took 3 seconds or more or failed, and whether playback resumed after each wait.
Your next lag, recorded.
Free 7-day trial. Then US$14.99 one-time, no subscription.
What is not measured
We do not collect Twitch private bytes or player internals. Pauses, seeks and observations without a safe tab association are reported separately, so symptoms never mix with measurements.
Of each request, the extension keeps only the host and the type (playlist, segment or media), never the full address. It can't tell ads from the stream, because both go through the same player, and it only works on Twitch.
If it is the game that freezes, not the stream, the steps are the same, just without the extension. Game lag: how to prove the connection wobbled.
The next test
The report for a Twitch buffering incident suggests comparing the same stream, at a fixed video quality, on this PC and on a second device on the same network during the next incident. If both buffer at the same times, the likely cause is shared: the router, the ISP or the stream itself. If only the PC buffers, look at the PC and its session. Different servers and buffers can still explain differences, so neither result names the culprit on its own.
If both sides wobble together, the next step is separating Wi-Fi from the link. Wi-Fi or internet: how to tell which one fails.
With the records in hand, the next step is the support ticket. How to file an ISP complaint with evidence.
One payment in US dollars
No recurring charges. No automatic renewal.
Try it free for 7 days- Free 7-day trial before buying
- Reports for incidents recorded after the trial
- Recorder and local dashboard
- Internet outages and lag recorded automatically
- Shortcut to mark a lag as it happens
- Full measurements from the last 7 days
- Incident reports and record exports
- 30-day history (PDF) with availability and outages for each day
- Automatic speed test compared with your plan
- Continued use of the purchased version