[{"data":1,"prerenderedAt":220},["ShallowReactive",2],{"blog:video-buffering-with-vpn":3},{"zh-CN":4,"en":118},{"blocks":5,"faq":99},[6,9,11,13,15,19,21,26,28,31,33,35,37,39,45,48,50,52,64,66,69,71,80,83,85,92,95,97],{"type":7,"html":8},"p","视频一直转圈缓冲，很少是单一原因，而是三个环节接连出问题：播放器实际给出的画质、这条线路当下的带宽、还有设备本身。三者要按顺序查，因为前一个环节没搞清楚，后面查的都是错的方向——尤其是画质这一环，播放器显示的数字经常不可信。",{"type":7,"html":10},"很多人第一反应是怪 VPN，理由通常只是「感觉连上以后就变卡了」，但这种感觉本身并不能说明问题出在哪一环。同样的连接，看新闻网页很快，看视频却一直转圈，这种反差恰好说明问题很可能不在连接本身，而在上面这条链的某一环。",{"type":7,"html":12},"排查原则不变：\u003Cstrong>一次只改一个变量\u003C\u002Fstrong>。换节点、降画质、重启设备一起做，卡顿消失了也不知道是哪一步管用的。",{"type":7,"html":14},"这条链有意思的地方在于，三个环节的排查成本完全不一样——确认画质十几秒，确认带宽一两分钟，怀疑设备却往往要下载一个文件慢慢测。按由易到难的顺序查，比凭感觉先怀疑最麻烦的那个更省时间。",{"type":16,"id":17,"html":18},"h2","bp-triage","先做一次十秒测试",{"type":7,"html":20},"把播放器的画质手动锁定在最低一档，重新播放同一段内容，看还卡不卡。",{"type":22,"items":23},"list",[24,25],"锁定最低档还是卡：问题不在带宽，也不在线路，直接看设备那一节。","锁定最低档就流畅，换回自动或者更高档才卡：问题出在画质判断或带宽上，往下按顺序查。",{"type":7,"html":27},"这一步能省掉大量瞎猜的时间，因为它一次性排除了设备这个最容易被忽略的可能。很多人卡顿的第一反应是换节点，换完不管用又开始怀疑网速，其实设备本身能不能扛住那个分辨率，从头到尾都没被认真怀疑过。",{"type":16,"id":29,"html":30},"bp-quality","第一环：播放器实际给的画质，不是你选的那个",{"type":7,"html":32},"自动画质的逻辑是先卡顿、再降级，不是提前判断网络够不够用再决定。也就是说，看到画面卡了一下，说明播放器已经落后于实际情况一步，它显示的档位数字反映的是刚才的判断，不是这一秒的真实状况。",{"type":7,"html":34},"还有一种更容易被忽略的情况：一部分视频平台会识别看起来像数据中心或商用地址的出口 IP，主动把能给的最高画质压低，跟那条线路实际带宽够不够没有关系，纯粹是平台自己的判断。遇到这种情况，等待没有用，多等多久画质都不会自己涨回去，因为限制的源头不是带宽，是平台那一侧的策略，换一个不那么容易被归类的地区节点才有用。",{"type":7,"html":36},"判断是不是这种情况也不难：同一条线路，看视频画质总卡在某个不高的档位上不动，但用同一条线路做别的下载或者浏览却很顺畅，这种「网络明明够用、画质却上不去」的反差，基本就是平台在限制，不是带宽的问题。",{"type":7,"html":38},"确认实际画质，按这个顺序：",{"type":22,"items":40,"ordered":44},[41,42,43],"打开播放器自带的画质菜单，看它显示的具体档位数字，不是「自动」两个字本身。","暂停几秒钟让缓冲条走够一段，再手动选一个固定档位重新播放，而不是继续交给自动判断。","同一段内容用固定档位从头放一遍，对比会不会仍然卡——如果固定低档都卡，问题在下面两环，不在画质判断。",true,{"type":16,"id":46,"html":47},"bp-bandwidth","第二环：这条线路当下的带宽够不够",{"type":7,"html":49},"测速工具连的是就近的测速服务器，视频平台的内容节点是另一条完全不同的路线，两者经过的中间环节不一样。测速数字好看，只能说明到测速服务器这一段没问题，不能代表到视频节点的那一段也没问题。",{"type":7,"html":51},"这也是为什么「测速数字很好看，看视频还是卡」听起来矛盾，其实完全说得通——高速那一段和卡顿那一段根本不是同一条路，两个数字压根不能直接比。真正有意义的测试，是让流量走的路径尽量接近实际看视频时走的那条路径。",{"type":53,"items":54},"steps",[55,59],{"title":56,"body":57},"怎么确认",[58],"用同一个网络，不开 VPN 直接测一次速度，再开着 VPN 测一次，两个数字都记下来；然后实际播放视频，观察卡顿是不是集中在开着 VPN 的时候。如果两次测速差别不大，视频却只在开 VPN 时卡，说明瓶颈更可能在节点到内容服务器这一段，不是节点到测速服务器这一段，两段路径不能一概而论。",{"title":60,"body":61},"怎么处理",[62,63],"换一个地区更接近内容平台服务器的节点，晚高峰时段换一条没那么多人挤的线路。同一个地区里的出口经常共享上游带宽，换到不同地区比在同一地区里来回换更有效。","平台服务器的具体位置猜不出来，但可以用排除法：换两三个不同地区各测一遍，哪个地区放起来最稳，之后就固定用那一片的节点，不用每次都重新猜。",{"type":65},"downloads",{"type":16,"id":67,"html":68},"bp-device","第三环：设备本身跟不上",{"type":7,"html":70},"前两环都排除了，就该怀疑设备。老一点的手机或者电视盒子解码高画质视频本身就吃力，长时间播放还会发热降频，表现出来跟网络卡顿几乎一样，很容易被误会成线路问题。",{"type":53,"items":72},[73,76],{"title":56,"body":74},[75],"下载一段同分辨率的视频文件到本地，不经过网络直接播放。本地文件都卡，基本可以确定是设备的问题，不用再怀疑线路或节点。",{"title":60,"body":77},[78,79],"手动把播放画质固定在设备能流畅处理的档位，比反复换节点更管用；长时间使用发烫的设备，中途歇一会儿再继续，也有一部分帮助。","电视盒子和几年前的手机是最常见的重灾区——当年买的时候能流畅播放的画质标准，跟不上现在视频平台默认给的码率，不是设备坏了，是它本来就没打算处理这么高的负载，换更省流量的固定档位是唯一真正管用的办法。",{"type":16,"id":81,"html":82},"bp-pitfalls","容易被忽略的原因",{"type":7,"html":84},"排查完三个主环节，还有几个常见的干扰因素值得留意——它们不属于画质、带宽或设备中的任何一个，但同样会让人误以为是网络出了问题：",{"type":22,"items":86},[87,88,89,90,91],"系统或者其他 App 在后台悄悄下载更新，占掉了大半带宽，视频只能分到剩下的一小部分。","同一个网络下好几台设备同时在看视频或者下载，实际可用带宽被平分了，看起来像是线路不行，其实是分给自己的那一份变小了。","投屏到电视时多了一段电视和路由器之间的 Wi-Fi 跳转，这一段本身也可能是瓶颈，跟手机端的表现是两件事，需要分开测。","长期用同一个节点没换过，赶上那个节点所在地区的晚高峰，大家都在挤同一条线路。\u003Ca href=\"\u002Fblog\u002Fslow-at-night-peak-hours\u002F\">为什么一到晚上就变慢\u003C\u002Fa>那篇专门讲了这类时段性拥堵的判断方法。","浏览器或者播放器装了来源不明的插件，中途转码或者插广告，也会拖慢实际播放速度，这类问题跟网络和设备都没关系，先怀疑最近有没有新装什么。",{"type":16,"id":93,"html":94},"bp-final","总结",{"type":7,"html":96},"视频缓冲按画质、带宽、设备这条链查：先确认播放器给的是不是真实画质，再看带宽是不是真的够到内容节点，最后才怀疑设备本身，别漏了平台限速和后台干扰这两个容易被忽略的变量。十秒测试能一次性排除最容易被忽略的设备原因，省掉大量瞎猜的时间。",{"type":7,"html":98},"节点选得顺手，能省掉大半这类折腾，不用每次卡顿都从头猜一遍是哪一环出的问题。\u003Ca href=\"\u002Ffeatures\u002F\">快橙\u003C\u002Fa>换节点只要一步，遇到晚高峰或者某个节点被限速，几秒钟就能换到别的线路上试。注册后每天有免费试用时长，先拿它把上面的三环测一遍，比猜半天更快知道问题到底出在哪一环。想直接体验，\u003Ca href=\"\u002Fsignup\u002F\">注册账号\u003C\u002Fa>几步就能完成。",[100,103,106,109,112,115],{"q":101,"a":102},"播放器显示 1080p，为什么还是一直缓冲？","显示的档位不代表当下真实的传输码率。自动画质是先卡顿、再降级，不是提前预判，看到卡顿本身就说明它已经落后于实际情况一步了。",{"q":104,"a":105},"测速显示的数字很高，为什么看视频还是卡？","测速连的是就近的测速服务器，视频真正要连的是内容平台自己的节点，两条路线经过的地方完全不同。测速好看不代表看视频那条路径也够用，\u003Ca href=\"\u002Fblog\u002Fwhy-speed-test-looks-wrong\u002F\">为什么测速数字好看实际却很卡\u003C\u002Fa>讲得更细。",{"q":107,"a":108},"换了节点以后，画质反而变差了？","有一部分视频平台会识别看起来像数据中心或者商用地址的出口，主动把画质压低，不管那条线路实际带宽够不够，换一个地区的节点通常能避开。",{"q":110,"a":111},"手机上放会卡，投到电视上也卡，是同一个原因吗？","不一定。投屏多了一段电视和路由器之间的 Wi-Fi 跳转，这段本身也可能是瓶颈，跟手机端的画质或带宽问题是两件事，需要分开测。",{"q":113,"a":114},"Netflix 提示地区不支持，这篇能解决吗？","不能，这篇只讲已经能打开、只是画面卡顿的情况。地区和账号相关的问题看\u003Ca href=\"\u002Fblog\u002Fhow-to-watch-netflix-abroad\u002F\">Netflix 看不了怎么办\u003C\u002Fa>。",{"q":116,"a":117},"换了节点还是缓冲，接下来查什么？","先确认是不是只有这一个平台卡：其他视频站正常就说明问题在平台侧。都卡再看设备和家里的网络。",{"blocks":119,"faq":201},[120,122,124,126,128,130,132,136,138,140,142,144,146,148,153,155,157,159,170,171,173,175,184,186,188,195,197,199],{"type":7,"html":121},"Video that keeps spinning is rarely down to one cause — it's three links failing one after another: the quality the player is actually delivering, whether the line has the bandwidth for it right now, and the device itself. They have to be checked in that order, because getting the first one wrong sends every step after it in the wrong direction — especially quality, where the number on screen is often not to be trusted.",{"type":7,"html":123},"The first instinct for most people is to blame the VPN, usually on nothing more than a feeling that things got slower right after connecting — but that feeling alone says nothing about which link actually failed. The same connection loading news pages instantly while video spins endlessly is exactly the kind of contrast that points away from the connection itself and toward one specific link in this chain.",{"type":7,"html":125},"The same rule as always: \u003Cstrong>change one variable at a time\u003C\u002Fstrong>. Switch the node, drop the quality and restart the device together, and even if the stutter stops you will not know which step actually fixed it.",{"type":7,"html":127},"What makes this chain worth knowing is that the three links cost very different amounts of effort to check — confirming quality takes seconds, confirming bandwidth takes a minute or two, and suspecting the device usually means downloading a file and testing it slowly. Working from cheapest to most expensive beats jumping straight to suspecting whichever one feels most convenient to blame.",{"type":16,"id":17,"html":129},"Start with a ten-second test",{"type":7,"html":131},"Lock the player's quality to its lowest setting by hand and replay the same content. See whether it still stutters.",{"type":22,"items":133},[134,135],"Still stutters at the lowest setting: the problem isn't bandwidth or the line — go straight to the device section.","Smooth at the lowest setting, but stutters again on auto or anything higher: the problem is in quality reporting or bandwidth — keep reading in order.",{"type":7,"html":137},"This step alone saves a lot of guessing, because it rules out the device in one move — the possibility everyone forgets to suspect. The usual first move is to switch nodes, and when that doesn't help, to blame the network speed next; whether the device itself can even handle that resolution rarely gets a serious look at all.",{"type":16,"id":29,"html":139},"Link one: the quality the player is actually giving you, not what you picked",{"type":7,"html":141},"Auto quality's logic is to stall first and downgrade second — it does not predict whether the network can keep up and decide in advance. In other words, a visible stall means the player is already a step behind reality; the number it shows reflects its last judgment, not what's true this exact second.",{"type":7,"html":143},"There's a less obvious case worth knowing too: some streaming platforms detect an exit IP that looks like a datacenter or commercial address and deliberately cap the best quality they'll offer it, regardless of whether that line actually has enough bandwidth. Waiting does nothing here — no amount of waiting brings the quality back up, because the limit isn't about bandwidth at all, it's a policy on the platform's side. Switching to a region that doesn't get flagged the same way is what actually works.",{"type":7,"html":145},"Spotting this case isn't hard: the same line keeps video quality capped at some unremarkable setting, while downloads or browsing over that same line run just fine. That contrast — the network is clearly good enough, yet quality won't climb — is usually the platform imposing a limit, not a bandwidth shortfall.",{"type":7,"html":147},"To confirm the real quality, work through this in order:",{"type":22,"items":149,"ordered":44},[150,151,152],"Open the player's own quality menu and read the specific number it reports, not just the word "Auto."","Pause for a few seconds to let the buffer fill, then pick a fixed setting by hand and replay rather than leaving it on auto.","Replay the same content from the start at that fixed setting and see whether it still stutters — if a low fixed setting still stutters, the problem sits in one of the next two links, not in quality reporting.",{"type":16,"id":46,"html":154},"Link two: whether this line has the bandwidth right now",{"type":7,"html":156},"A speed test tool connects to a nearby test server; the streaming platform's content node is a completely different route with different hops in between. A good speed test number only tells you that leg to the test server is fine — it says nothing about the leg to the actual video node.",{"type":7,"html":158},"That's also why "a great speed test number, and the video still stutters" sounds contradictory but actually makes complete sense — the fast leg and the stuttering leg are simply not the same path, so the two numbers were never comparable in the first place. A test that actually means something has to follow a path close to the one video traffic really takes.",{"type":53,"items":160},[161,165],{"title":162,"body":163},"How to confirm it",[164],"On the same network, run one speed test without the VPN and one with it, and note both numbers. Then actually play the video and watch whether the stuttering clusters around the times the VPN is on. If the two speed test numbers are close but video only stutters with the VPN on, the bottleneck is more likely between the node and the content server than between the node and the speed-test server — the two legs are not interchangeable.",{"title":166,"body":167},"How to fix it",[168,169],"Switch to a node in a region closer to the platform's own servers, and during peak hours switch to a line with fewer people on it. Exits in the same region often share upstream capacity, so moving to a different region works better than cycling through nodes within the same one.","There's no way to know exactly where the platform's servers sit, but elimination works: test two or three different regions, keep whichever one plays the most reliably, and stick with that region afterward instead of re-guessing every time.",{"type":65},{"type":16,"id":67,"html":172},"Link three: the device itself can't keep up",{"type":7,"html":174},"With the first two links ruled out, suspect the device. An older phone or streaming box can genuinely struggle to decode high-quality video, and heats up and throttles itself over a long session — which looks almost identical to network stuttering and gets blamed on the line far too often.",{"type":53,"items":176},[177,180],{"title":162,"body":178},[179],"Download a video file at the same resolution and play it locally, with no network involved. If the local file still stutters, that settles it — it's the device, and there's no more reason to suspect the line or the node.",{"title":166,"body":181},[182,183],"Manually cap playback at a quality the device can actually handle smoothly — that does more than switching nodes ever will. On a device that's overheating during long sessions, a short break partway through helps too.","Streaming boxes and phones bought a few years ago are the most common culprits — the quality standard they handled smoothly back then simply hasn't kept pace with what platforms default to today. The device isn't broken; it was never built for this much load, and switching to a lighter fixed setting is the one thing that reliably works.",{"type":16,"id":81,"html":185},"Easy to overlook",{"type":7,"html":187},"Once the three main links are ruled out, a few other common distractions are worth knowing — none of them are quality, bandwidth or the device, but they get mistaken for a network problem all the same:",{"type":22,"items":189},[190,191,192,193,194],"The system or some other app is quietly downloading an update in the background, eating most of the bandwidth and leaving video with whatever is left over.","Several devices on the same network are streaming or downloading at once, so the bandwidth actually available gets divided up — it looks like the line is bad when really your own share just got smaller.","Casting to a TV adds a Wi-Fi hop between the TV and the router that can be its own bottleneck, a separate question from how things look on the phone and worth testing on its own.","The same node has been in use for a long time and happens to sit in a region hitting its own evening peak, with everyone crowding the same line. \u003Ca href=\"\u002Fen\u002Fblog\u002Fslow-at-night-peak-hours\u002F\">Why everything slows down at night\u003C\u002Fa> covers how to spot this kind of time-based congestion specifically.","A browser or player extension from an unclear source is transcoding on the fly or injecting ads, which slows real playback and has nothing to do with either the network or the device — worth suspecting first if something was installed recently.",{"type":16,"id":93,"html":196},"In summary",{"type":7,"html":198},"Work through buffering along the chain: quality, bandwidth, device. Confirm what the player is really delivering first, then check whether the bandwidth genuinely reaches the content node, and only then suspect the device — without forgetting platform throttling and background interference, the two variables people miss most. The ten-second test rules out the device in one move, the possibility everyone forgets, and saves a lot of guessing.",{"type":7,"html":200},"Picking a node that just works removes most of this hassle. \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">FastOrange\u003C\u002Fa> switches nodes in one tap, so hitting peak-hour congestion or a throttled node is a matter of trying another line within seconds. Every registered account gets free daily trial time — run the three-link check above with it instead of guessing which link actually broke. To try it directly, \u003Ca href=\"\u002Fen\u002Fsignup\u002F\">signing up\u003C\u002Fa> takes a few steps.",[202,205,208,211,214,217],{"q":203,"a":204},"The player says 1080p. Why does it still keep buffering?","The number on screen does not reflect the real bitrate right now. Auto quality stalls first and downgrades second, not the other way around — seeing a stall at all means the player is already a step behind reality.",{"q":206,"a":207},"My speed test shows a high number. Why does video still stutter?","A speed test hits a nearby test server; the video actually needs the streaming platform's own content node, and the two routes go through completely different places. A good speed test number says nothing about whether that other path holds up — \u003Ca href=\"\u002Fen\u002Fblog\u002Fwhy-speed-test-looks-wrong\u002F\">why a good speed test can still feel slow\u003C\u002Fa> covers this in more depth.",{"q":209,"a":210},"Quality got worse after I switched nodes. Why?","Some streaming platforms detect an exit address that looks like a datacenter or commercial IP and deliberately cap the quality they'll serve it, regardless of whether that line actually has the bandwidth. Switching to a different region usually avoids it.",{"q":212,"a":213},"It stutters on my phone and it stutters when I cast to the TV too. Same cause?","Not necessarily. Casting adds a Wi-Fi hop between the TV and the router that can be its own bottleneck — that's a separate question from quality or bandwidth on the phone, and worth testing on its own.",{"q":215,"a":216},"Netflix says this region isn't supported. Does this article cover that?","No — this one is only about video that already opens but stutters. Region and account issues are covered in \u003Ca href=\"\u002Fen\u002Fblog\u002Fhow-to-watch-netflix-abroad\u002F\">what to do when Netflix won't play\u003C\u002Fa>.",{"q":218,"a":219},"I switched nodes and it still buffers. What next?","Check whether only this one platform stutters. If other video sites play fine, the problem sits on the platform side; if everything stutters, look at the device and your home network.",1793276291384]