{"id":1767,"date":"2026-11-17T22:36:47","date_gmt":"2026-11-17T22:36:47","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=1767"},"modified":"2026-11-17T22:36:47","modified_gmt":"2026-11-17T22:36:47","slug":"tcp-receive-window-bdp-high-latency-vps-throughput","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/","title":{"rendered":"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A 1 GB file transferred across a 200 ms path with default Linux settings moves at roughly 3 MB\/s on a 1 Gbps port; the same transfer with BBR and a 4\u00d7 larger socket buffer reaches 8\u201310 MB\/s. The bottleneck is not bandwidth, it is the product of round-trip time and receive window. This article measures that difference properly \u2014 with separate runs for idle RTT, loaded RTT, single-stream throughput and retransmit rate \u2014 so you can attribute a slow transfer to the kernel rather than guessing at the network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Everything here is TCP behaviour inside the guest and on the path; none of it requires host access. If you are still deciding whether a plan gives you enough isolated network capacity to make this worth doing, the <a href=\"https:\/\/virtualserversvps.com\/cloud-vps-benefits.html\">cloud VPS scaling model<\/a> covers how port speed and transfer caps are usually bundled.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Measure the three numbers before tuning anything<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Any transfer complaint decomposes into latency, window and loss. Measure them separately, in that order, because a window fix does nothing for a loss problem and a congestion-control fix does nothing for a latency problem.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># 1. Path and RTT, 200 samples\nmtr -rwzc 200 -i 0.05 target.example\nping -c 200 -i 0.02 target.example | tail -2\n\n# 2. Single-stream throughput for 20s\niperf3 -c target.example -t 20 -P 1 --json &gt; \/tmp\/single.json\n\n# 3. Retransmits and window during a transfer\nss -tinmi dst target.example | head -40\nnstat -az TcpRetransSegs TcpExtTCPLostRetransmit TcpExtTCPTimeouts<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Read <code>iperf3<\/code>&#8216;s sender and receiver reports separately. A large gap between <code>sender bitrate<\/code> and <code>receiver bitrate<\/code> with a retransmit count above a few hundred over 20 seconds points at loss, not at window size. If they match and the rate is far below port speed, the window is the constraint \u2014 which is the common case on high-RTT paths.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The bandwidth-delay product is the real limit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Throughput for a single stream cannot exceed window divided by RTT. Linux autotunes receive buffers up to <code>net.ipv4.tcp_rmem<\/code>&#8216;s maximum, which on most distros defaults to about 6 MB. At 200 ms RTT, 6 MB \/ 0.2 s = 30 MB\/s theoretical \u2014 and with loss-driven congestion control on a lossy path the achieved rate is far lower.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>RTT<\/th><th>Window needed for 100 Mbit<\/th><th>Needed for 1 Gbit<\/th><th>Default max 6 MB gives<\/th><\/tr><\/thead><tbody><tr><td>10 ms<\/td><td>~125 KB<\/td><td>~1.25 MB<\/td><td>plenty<\/td><\/tr><tr><td>50 ms<\/td><td>~625 KB<\/td><td>~6.25 MB<\/td><td>~960 Mbit<\/td><\/tr><tr><td>100 ms<\/td><td>~1.25 MB<\/td><td>~12.5 MB<\/td><td>~480 Mbit<\/td><\/tr><tr><td>200 ms<\/td><td>~2.5 MB<\/td><td>~25 MB<\/td><td>~240 Mbit<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Those are clean-path figures. Add 0.1 % loss and CUBIC&#8217;s throughput collapses to roughly <code>MSS \/ (RTT \u00d7 sqrt(p))<\/code>, which at 1448 bytes, 200 ms and 0.001 gives roughly 1.1 MB\/s \u2014 matching the 3 MB\/s observation at the top of this article. BBR does not treat loss as a congestion signal in the same way, which is why it recovers most of that loss on a high-RTT path.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Tune the buffer ceiling, not the default<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The autotuning defaults matter less than the maximum. Set the ceiling high enough for your worst-case RTT times your port speed, and let autotuning fill it only when the path proves clean:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># \/etc\/sysctl.d\/70-vps-tcp-window.conf\nnet.core.rmem_max = 16777216\nnet.core.wmem_max = 16777216\nnet.ipv4.tcp_rmem = 4096 262144 16777216\nnet.ipv4.tcp_wmem = 4096 262144 16777216\nnet.ipv4.tcp_moderate_rcvbuf = 1\nnet.ipv4.tcp_window_scaling = 1\nnet.ipv4.tcp_sack = 1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apply with <code>sysctl --system<\/code> and verify with <code>sysctl net.ipv4.tcp_rmem<\/code>. Then re-run the single-stream test \u2014 this is where people stop, see no change, and conclude buffers do not matter. The measurement in <code>ss<\/code> explains why: the window was probably never the limit if the path had loss. Look for <code>cwnd:<\/code> and the <code>rtt:<\/code> value in <code>ss -tinmi<\/code> output mid-transfer; if <code>cwnd<\/code> stays small while <code>retrans<\/code> climbs, buffers are irrelevant and the path is the problem.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Congestion control: measure the switch, do not assume it<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">BBR is not universally better. On a low-RTT, lossless LAN or a well-provisioned same-region path, BBR and CUBIC land within a few percent of each other. On high-RTT or lossy paths BBR typically wins by 2\u20134\u00d7. Test both on your actual path rather than trusting a blog post \u2014 including this one:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sysctl -w net.ipv4.tcp_congestion_control=cubic\niperf3 -c target.example -t 30 -P 1 | tail -5\n\nsysctl -w net.core.default_qdisc=fq\nsysctl -w net.ipv4.tcp_congestion_control=bbr\niperf3 -c target.example -t 30 -P 1 | tail -5\nsysctl net.ipv4.tcp_available_congestion_control<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Run each three times and compare medians, not single runs; the variance between two consecutive <code>iperf3<\/code> runs on the same path is often 15 %. If <code>tcp_available_congestion_control<\/code> does not list <code>bbr<\/code>, the module is missing: <code>modprobe tcp_bbr<\/code> and add it to <code>\/etc\/modules-load.d\/<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Separating your bufferbloat from the path&#8217;s<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The most common self-inflicted problem on a VPS is an oversized egress queue: uploads make interactive traffic unusable because 2 MB of your own frames sit ahead of a 60-byte SSH packet. Measure it by comparing RTT at idle and during a saturating upload.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ip -s link show dev eth0\ntc qdisc show dev eth0\n# idle\nping -c 100 -i 0.05 target.example | tail -2\n# loaded: saturate upstream for 30s, ping meanwhile\niperf3 -c target.example -t 30 -R &amp; sleep 2\nping -c 100 -i 0.05 target.example | tail -2; wait<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If p99 RTT rises from 20 ms to 400 ms during the upload, the queue is buffering far too much. Switching egress to <code>fq_codel<\/code> (which is the default qdisc on many distros but not all) cuts that to typically 30\u201360 ms with no throughput loss: <code>tc qdisc replace dev eth0 root fq_codel<\/code>. If a shaping rate is applied by the provider, the queue you see may not be yours at all \u2014 test with <code>-R<\/code> (receive) as well and compare, because downstream shaping is invisible from inside the guest.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Retransmits: rate versus count<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><code>TcpRetransSegs<\/code> is a counter, and counters only mean something as a rate. A busy server retransmits thousands of segments an hour and is perfectly healthy; the useful metric is retransmits as a percentage of segments sent, sampled over a window:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>snap() { awk '\/TcpOutSegs|TcpRetransSegs\/{print $1,$2}' \/proc\/net\/snmp | tail -2; }\nsnap &gt; \/tmp\/a; sleep 300; snap &gt; \/tmp\/b\npaste \/tmp\/a \/tmp\/b | awk '{d=$4-$2; if($1==\"TcpOutSegs\")o=d; else r=d} END{printf \"out=%d retrans=%d rate=%.3f%%\\n\",o,r,100*r\/o}'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Under 0.1 % is normal internet weather; 0.1\u20131 % is worth investigating with <code>mtr<\/code> to find the hop that correlates with the loss; above 1 % is a fault or a saturated link, and no congestion control will hide it. Cross-check <code>TcpExtTCPTimeouts<\/code> in the same window: timeouts without matching retransmits usually mean the loss is on the return path, which a drop counter on your own interface will never show.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What the numbers look like when fixed<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On a 200 ms path with 0.1 % loss, a realistic progression from a stock Ubuntu 24.04 guest looks like this \u2014 measured with the same command each time, single stream, 30-second runs, three runs per row:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Configuration<\/th><th>Single stream<\/th><th>p99 RTT idle \u2192 loaded<\/th><th>Retrans rate<\/th><\/tr><\/thead><tbody><tr><td>Stock: cubic, 6 MB max window<\/td><td>2.5\u20133.5 MB\/s<\/td><td>20 \u2192 380 ms<\/td><td>~0.4 %<\/td><\/tr><tr><td>+ 16 MB window ceiling<\/td><td>3.0\u20134.0 MB\/s<\/td><td>unchanged<\/td><td>~0.4 %<\/td><\/tr><tr><td>+ fq_codel egress<\/td><td>3.0\u20134.0 MB\/s<\/td><td>20 \u2192 45 ms<\/td><td>~0.4 %<\/td><\/tr><tr><td>+ BBR<\/td><td>8\u201310 MB\/s<\/td><td>20 \u2192 45 ms<\/td><td>~0.4 %<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The important reading: buffers alone changed nothing on this lossy path, <code>fq_codel<\/code> fixed only the latency, and BBR fixed only the throughput. Three separate problems, three separate fixes. Anyone who tells you &#8220;just enable BBR&#8221; is measuring one column of this table.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Persist the changes and keep the evidence<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Put every sysctl into <code>\/etc\/sysctl.d\/<\/code> and the qdisc into a systemd unit that runs after <code>network-online.target<\/code>, because <code>tc<\/code> commands do not survive a reboot or a link flap. Keep the three JSON outputs from your final run next to the config so that six months later, when throughput changes, you can tell whether the path changed or your configuration did \u2014 that comparison is the only way to distinguish a provider-side change from a regression you introduced.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>A 1 GB file transferred across a 200 ms path with default Linux settings moves at roughly 3 MB\/s on a 1 Gbps port; the same transfer with BBR and&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":2,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1767","post","type-post","status-publish","format-standard","hentry","category-performance-optimization"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS - Virtual Servers VPS Blog<\/title>\n<meta name=\"description\" content=\"A 1 GB file transferred across a 200 ms path with default Linux settings moves at roughly 3 MB\/s on a 1 Gbps port; the same transfer with BBR and a 4\u00d7\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS\" \/>\n<meta property=\"og:description\" content=\"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS\" \/>\n<meta property=\"og:url\" content=\"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/\" \/>\n<meta property=\"og:site_name\" content=\"Virtual Servers VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T22:36:47+00:00\" \/>\n<meta name=\"author\" content=\"Virtual-Servers-Vps-Editor\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Virtual-Servers-Vps-Editor\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/\",\"url\":\"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/\",\"name\":\"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS - Virtual Servers VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#website\"},\"datePublished\":\"2026-11-17T22:36:47+00:00\",\"author\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0\"},\"description\":\"A 1 GB file transferred across a 200 ms path with default Linux settings moves at roughly 3 MB\/s on a 1 Gbps port; the same transfer with BBR and a 4\u00d7\",\"breadcrumb\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/virtualserversvps.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#website\",\"url\":\"https:\/\/virtualserversvps.com\/blog\/\",\"name\":\"Virtual Servers VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/virtualserversvps.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0\",\"name\":\"Virtual-Servers-Vps-Editor\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g\",\"caption\":\"Virtual-Servers-Vps-Editor\"},\"sameAs\":[\"https:\/\/virtualserversvps.com\/blog\"],\"url\":\"https:\/\/virtualserversvps.com\/blog\/author\/virtualserversvps\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS - Virtual Servers VPS Blog","description":"A 1 GB file transferred across a 200 ms path with default Linux settings moves at roughly 3 MB\/s on a 1 Gbps port; the same transfer with BBR and a 4\u00d7","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/","og_locale":"en_US","og_type":"article","og_title":"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS","og_description":"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS","og_url":"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/","og_site_name":"Virtual Servers VPS Blog","article_published_time":"2026-11-17T22:36:47+00:00","author":"Virtual-Servers-Vps-Editor","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Virtual-Servers-Vps-Editor","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/","url":"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/","name":"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS - Virtual Servers VPS Blog","isPartOf":{"@id":"https:\/\/virtualserversvps.com\/blog\/#website"},"datePublished":"2026-11-17T22:36:47+00:00","author":{"@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0"},"description":"A 1 GB file transferred across a 200 ms path with default Linux settings moves at roughly 3 MB\/s on a 1 Gbps port; the same transfer with BBR and a 4\u00d7","breadcrumb":{"@id":"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/virtualserversvps.com\/blog\/tcp-receive-window-bdp-high-latency-vps-throughput\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/virtualserversvps.com\/blog\/"},{"@type":"ListItem","position":2,"name":"TCP Receive Windows and the Bandwidth-Delay Product on a High-Latency VPS"}]},{"@type":"WebSite","@id":"https:\/\/virtualserversvps.com\/blog\/#website","url":"https:\/\/virtualserversvps.com\/blog\/","name":"Virtual Servers VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/virtualserversvps.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0","name":"Virtual-Servers-Vps-Editor","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g","caption":"Virtual-Servers-Vps-Editor"},"sameAs":["https:\/\/virtualserversvps.com\/blog"],"url":"https:\/\/virtualserversvps.com\/blog\/author\/virtualserversvps\/"}]}},"_links":{"self":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1767","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/comments?post=1767"}],"version-history":[{"count":1,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1767\/revisions"}],"predecessor-version":[{"id":1770,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1767\/revisions\/1770"}],"wp:attachment":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/media?parent=1767"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/categories?post=1767"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/tags?post=1767"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}