You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.163.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 17:28, 10 March 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 18:27, 12 November 2023
- Expiry of block: 18:27, 12 November 2028
Your current IP address is 54.163.179.242. The blocked range is 54.163.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Short description|Intentional slowing of data transmission))
((Network neutrality))

'''Bandwidth throttling''' consists in the limitation of the communication speed (bytes or kilobytes per second), of the ingoing (received) or outgoing (sent) [[data]] in a [[Node (networking)|network node]] or in a [[Networking hardware|network device]].

The data speed and rendering may be limited depending on various parameters and conditions.

==Overview==

Limiting the speed of data sent by a data originator (a [[Client (computing)|client computer]] or a [[Server (computing)|server computer]]) is much more efficient than limiting the speed in an intermediate network device between client and server because while in the first case usually no [[network packet]]s are lost, in the second case network packets can be lost / discarded whenever ingoing data speed overcomes the bandwidth limit or the capacity of device and data packets cannot be temporarily stored in a buffer queue (because it is full or it does not exist); the usage of such a buffer queue is to absorb the peaks of incoming data for very short time lapse.

In the second case discarded data packets can be resent by transmitter and received again.

When a low level network device discards incoming data packets usually can also notify that fact to data transmitter in order to slow down the transmission speed (see also [[network congestion]]).<ref>((cite web|url=https://www.sciencedirect.com/topics/computer-science/dropping-packet|title=Dropping packet - an overview|author1=Deep Medhi|author2=Karthik Ramasamy|publisher=ScienceDirect|access-date=September 24, 2021|url-status=live|archive-url=https://web.archive.org/web/20200507140514/https://www.sciencedirect.com/topics/computer-science/dropping-packet|archive-date=May 7, 2020))</ref>

NOTE: Bandwidth throttling should not be confused with [[rate limiting]] which operates on client requests at application server level and/or at network management level (i.e. by inspecting protocol data packets).  Rate limiting can also help in keeping peaks of data speed under control.

These bandwidth limitations can be implemented:
* at ((strong|[[application software]] level)) (a client program or a server program, i.e. [[ftp server]], [[web server]], etc.) which can be run and configured to throttle data sent through network or even to throttle data received from network (by reading data at most at a throttled amount per second);
* at ((strong|[[network management]] level)) (typically done by an [[Internet Service Provider|ISP]]).

The ((strong|first one)) (client/server program) is usually perfectly ((strong|legal)) because it is a choice of the client manager or the server manager (by [[server administrator]]) to limit or not to limit the speed of data received from remote program via network or the speed of data sent to target program (server or client).

The ((strong|second one)) (ISP) instead is considered an ((strong|offense)) in the USA under [[Federal Communications Commission|FCC]] regulations. While ISPs prey on the individual's inability to fight them, fines can range up to $25,000 USD for throttling. In the United States, net neutrality, the principle that Internet service providers (ISPs) treat all data on the Internet the same, and not discriminate, has been an issue of contention between network users and access providers since the 1990s. With net neutrality, ISPs may not intentionally block, slow down, or charge money for specific online content.

Defined as the intentional slowing or speeding of an internet service by an [[Internet service provider]] (ISP). It is a reactive measure employed in communication networks to regulate network traffic and minimize bandwidth congestion. Bandwidth throttling can occur at different locations on the network. On a local area network ([[LAN]]), a [[system administrator]] ("sysadmin") may employ bandwidth throttling to help limit [[network congestion]] and server crashes. On a broader level, the [[Internet service provider]] may use bandwidth throttling to help reduce a user's usage of bandwidth that is supplied to the local network. Bandwidth throttling is also used as a measurement of data rate on Internet speed test websites.

Throttling can be used to actively limit a user's upload and download rates on programs such as [[video streaming]], [[BitTorrent (protocol)|BitTorrent]] protocols and other [[file sharing]] applications, as well as even out the usage of the total bandwidth supplied across all users on the network. Bandwidth throttling is also often used in [[Internet]] applications, in order to spread a load over a wider network to reduce local network congestion, or over a number of servers to avoid overloading individual ones, and so reduce their risk of the system [[Crash (computing)|crashing]], and gain additional revenue by giving users an incentive to use more expensive tiered pricing schemes, where bandwidth is not throttled.

==Operation==
A [[computer network]] typically consists of a number of [[Server (computing)|servers]], which host data and provide services to [[Client (computing)|clients]]. The Internet is a good example, in which [[web server]]s are used to host websites, providing information to a potentially very large number of client computers. Clients will make requests to servers, which will respond by sending the required [[data]], which may be a song file, a video, and so on, depending on what the client has requested. As there will typically be many clients per server, the data processing demand on a server will generally be considerably greater than on any individual client. And so servers are typically implemented using computers with high data capacity and processing power. The traffic on such a network will vary over time, and there will be periods when client requests will peak or sent responses will be huge, sometimes exceeding the capacity of parts of network and causing congestion, especially in parts of the network that form [[Bottleneck (engineering)|bottlenecks]]. This can cause data request failures, or in worst cases, server crashes.

In order to prevent such occurrences, a client / server / system administrator may enable (if available) bandwidth throttling:
* at ((strong|application software level)), to control the speed of ingoing (received) data and/or to control the speed of outgoing (sent) data:
** a '''client program''' could be configured to throttle the sending (upload) of a big file to a server program in order to reserve some network bandwidth for other uses (i.e. for sending emails with attached data, browsing web sites, etc.);
** a '''server program''' (i.e. web server) could throttle its outgoing data to allow more concurrent active client connections without using too much network bandwidth (i.e. using only 90% of available bandwidth in order to keep a reserve for other activities, etc.);
:: '''examples''': assuming to have a server site with speed access to Internet of 100[[Megabyte|MB]]/s (around 1000[[Megabit|Mbit]]/s), assuming that most clients have a 1MB/s (around 10Mbit/s) network speed access to Internet and assuming to be able to download huge files (i.e. 1 GB each):
::* '''with bandwidth throttling''', a server using a max. output speed of 100[[Kilobyte|kB]]/s (around 1Mbit/s) for each [[Transmission Control Protocol|TCP]] connection, could allow at least ((strong|1000 active TCP connections)) (or even 10000 if output is limited to 10kB/s) (active connections means that data content, such as a big file, is being downloaded from server to client);
::* '''without bandwidth throttling''', a server could efficiently serve only ((strong|100 active TCP connections)) (100MB/s / 1MB/s) before saturating network bandwidth;  a saturated network (i.e. with a bottleneck through an Internet Access Point) could slow down a lot the attempts to establish other new connections or even to force them to fail because of timeouts, etc.; besides this new active connections could not get easily or fastly their proper share of bandwidth.

* at ((strong|network management level)), to control the speed of data received or sent both at low level (data packets) and/or at high level (i.e. by inspecting application protocol data):
** policies similar or even more sophisticated than those of application software level could be set in low level network devices near Internet access point.

==Application==
A bandwidth intensive device, such as a [[Server (computing)|server]], might limit (throttle) the speed at which it receives or sends data, in order to avoid overloading its processing capacity or to saturate network bandwidth. This can be done both at the local network servers or at the ISP servers. ISPs often employ [[deep packet inspection]] (DPI), which is widely available in routers or provided by special DPI equipment. Additionally, today's networking equipment allows ISPs to collect statistics on flow sizes at line speed, which can be used to mark large flows for [[traffic shaping]].<ref>((cite web|url=http://www.mpi-sws.org/~gummadi/papers/traffic_shaping.pdf|title=The Local and Global Effects of Traffic Shaping in the Internet|author=Massimiliano Marcon|publisher=MPI|access-date=May 3, 2011|display-authors=etal|url-status=live|archive-url=https://web.archive.org/web/20110722140358/http://www.mpi-sws.org/~gummadi/papers/traffic_shaping.pdf|archive-date=July 22, 2011))</ref> Two ISPs, Cox and Comcast, have stated that they engage in this practice, where they limit users' bandwidth by up to 99%.<ref>((cite web |url=http://broadband.mpi-sws.org/transparency/results/ |title=Glasnost: Results from tests for BitTorrent traffic blocking |author=Max Planck Institute |date=March 18, 2008 |access-date=April 3, 2011 |url-status=live |archive-url=https://web.archive.org/web/20110404134316/http://broadband.mpi-sws.org/transparency/results/ |archive-date=April 4, 2011 ))</ref> Today most if not all [[Internet service provider|Internet Service Providers]] throttle their users' bandwidth, with or without the user ever even realizing it.<ref>((cite web |url=http://netequalizernews.com/2009/03/21/analysis-the-white-lies-isps-tell-about-broadband-speeds/ |title=Is Your ISP Throttling Your Bandwidth? |author=netequalizer |date=March 21, 2009 |access-date=April 3, 2011 |url-status=live |archive-url=https://web.archive.org/web/20110405170221/http://netequalizernews.com/2009/03/21/analysis-the-white-lies-isps-tell-about-broadband-speeds/ |archive-date=April 5, 2011 ))</ref> In the specific case of [[Comcast]], an equipment vendor called [[Sandvine]] developed the network management technology that throttled P2P file transfers.<ref>((cite journal |author=Kevin Werbach |year=2009 |title=Higher Standards Regulation in the Network Age |journal=Harvard Journal of Law & Technology |volume=23 |issue=1 |pages=217 |publisher=Harvard University |ssrn=1557265))</ref>

Those that could have their bandwidth throttled are typically someone who is constantly downloading and uploading torrents, or someone who just watches a lot of online videos. If this is done by an ISP, many consider this practice as an unfair method of regulating the bandwidth because consumers are not getting the required bandwidth even after paying the prices set by the ISPs. By throttling the people who are using so much bandwidth, the ISPs claim to enable their regular users to have a better overall quality of service.<ref>((cite web |url=https://www.geekdashboard.com/what-is-internet-throttling/ |title=What is Internet Throttling? Everything You Need To Know |date=July 27, 2021 |access-date=July 27, 2021 |url-status=live |archive-url=https://web.archive.org/web/20210816064331/https://www.geekdashboard.com/what-is-internet-throttling/ |archive-date=2021-08-16 ))</ref>

==Network neutrality==
[[Net neutrality]] is the principle that all Internet traffic should be treated equally. It aims to guarantee a level playing field for all websites and Internet technologies. With net neutrality, the network's only job is to move data—not to choose which data to privilege with higher quality, that is faster, service. In the US, on February 26, 2015, the [[Federal Communications Commission]] adopted Open Internet rules. They are designed to protect free expression and innovation on the Internet and promote investment in the nation's broadband networks. The Open Internet rules are grounded in the strongest possible legal foundation by relying on multiple sources of authority, including: Title II of the Communications Act and Section 706 of the Telecommunications Act of 1996. The new rules apply to both fixed and mobile broadband services.<ref name="Open Internet | FCC.gov">((Cite web|title = Open Internet|url = https://www.fcc.gov/openinternet|website = www.fcc.gov|access-date = 2015-06-03|url-status = live|archive-url = https://web.archive.org/web/20150615044837/https://www.fcc.gov/openinternet|archive-date = 2015-06-15))</ref> However, these rules were rolled back on December 14, 2017.

Bright line rules:
* No blocking: broadband providers may not block access to legal content, applications, services, or non-harmful devices.
* No throttling: broadband providers may not impair or degrade lawful Internet traffic on the basis of content, applications, services, or non-harmful devices.
* No paid prioritization: broadband providers may not favor some lawful Internet traffic over other lawful traffic in exchange for consideration or payment of any kind—in other words, no "fast lanes." This rule also bans ISPs from prioritizing content and services of their own affiliated businesses.<ref name="Open Internet | FCC.gov" />

==Throttling vs. capping==
Bandwidth throttling works by limiting (throttling) the speed at which a bandwidth intensive device (a [[Server (computing)|server]]) receives data or the speed (i.e. bytes / kilobytes per second) of each data response. If these limits are not in place, the device can overload its processing capacity.

Contrary to throttling, in order to use bandwidth when available, but prevent excess, each node in a proactive system should set an outgoing [[bandwidth cap]] that appropriately limits the ((strong|total number of bytes sent per unit time)).<ref>((cite conference |citeseerx=10.1.1.71.7264 |title=Proactive replication for data durability |author=Emil Sit |author2=Andreas Haeberlen |author3=Frank Dabek |author4=Byung-Gon Chun |author5=Hakim Weatherspoon |author6=Robert Morris |author7=M. Frans Kaashoek |author7-link=M. Frans Kaashoek |author8=John Kubiatowicz |pages=6))</ref> There are two types of bandwidth capping. A standard cap limits the [[bitrate]] or speed of data transfer on a broadband Internet connection. Standard capping is used to prevent individuals from consuming the entire transmission capacity of the medium. A lowered cap reduces an individual user's bandwidth cap as a defensive measure and/or as a punishment for heavy use of the medium's [[Bandwidth (signal processing)|bandwidth]]. Oftentimes this happens without notifying the user.

The difference is that bandwidth throttling regulates a bandwidth intensive device (such as a [[Server (computing)|server]]) by limiting how much data that device can receive from each node / client or can output or can send for each response. Bandwidth capping on the other hand limits the total transfer capacity, upstream or downstream, of data over a medium.

==Court cases==

===''Comcast Corp. v. FCC''===
((Main|Comcast Corp. v. FCC))
In 2007, [[Free Press (organization)|Free Press]], [[Public Knowledge]], and the [[Federal Communications Commission]] filed a complaint against Comcast's Internet service. Several subscribers claimed that the company was interfering with their use of peer-to-peer networking applications. The Commission stated that it had jurisdiction over Comcast's network management practices and that it could resolve the dispute through negotiation rather than through rulemaking. The Commission believed that Comcast had "significantly impeded consumers' ability to access the content and use the applications of their choice", and that because Comcast "ha[d] several available options it could use to manage network traffic without discriminating" against peer-to-peer communications, its method of [[bandwidth management]] "contravene[d] ... federal policy". At this time, "Comcast had already agreed to adopt a new system for managing bandwidth demand, the Commission simply ordered it to make a set of disclosures describing the details of its new approach and the company's progress toward implementing it". Comcast complied with this Order but petitioned for a review and presented several objections.<ref>((cite court |litigants=Comcast vs. FCC & U.S. |vol=08-1291 |opinion=Chief Judge David S. Tatel |court=[[United States Court of Appeals for the District of Columbia]] |date=April 6, 2010 |url=https://www.eff.org/files/Comcast%20v%20FCC%20(DC%20Cir%202010).pdf))</ref>

==ISP bandwidth throttling==

===Canada===
((More citations needed section|date=March 2019))
In 2008, the [[Canadian Radio-television and Telecommunications Commission]] (CRTC) decided to allow [[Bell Canada]] to single out [[peer-to-peer]] (P2P) traffic for bandwidth throttling between the hours of 4:30&nbsp;p.m. to 2&nbsp;a.m.<ref>((cite news |url=https://arstechnica.com/old/content/2008/11/canadian-regulators-allow-p2p-throttling.ars |title=Canadian regulators allow P2P throttling |newspaper=[[Ars Technica]] |first=Nate |last=Anderson |date=20 November 2008 |access-date=April 3, 2011 |url-status=live |archive-url=https://web.archive.org/web/20110325062508/http://arstechnica.com/old/content/2008/11/canadian-regulators-allow-p2p-throttling.ars |archive-date=25 March 2011 ))</ref> In 2009, the CRTC released a guideline for bandwidth throttling rules.<ref>((cite web|url=http://www.crtc.gc.ca/eng/archive/2009/2009-657.htm|title=Telecom Regulatory Policy CRTC 2009-657|publisher=CRTC|year=2009|access-date=April 21, 2012|url-status=live|archive-url=https://web.archive.org/web/20120712184101/http://www.crtc.gc.ca/eng/archive/2009/2009-657.htm|archive-date=July 12, 2012))</ref>

In 2011, following a major [[Rogers Hi-Speed Internet#Throttling|complaint]] by the Canadian Gamers Organization against Rogers for breaking the 2009 rules already in place, the CRTC created an addendum<ref>((cite web|url=http://www.crtc.gc.ca/eng/archive/2011/2011-609.htm|title=Internet traffic management practices – Guidelines for responding to complaints and enforcing framework compliance by Internet service providers|publisher=CRTC|year=2011|access-date=April 21, 2012|url-status=live|archive-url=https://web.archive.org/web/20120712184106/http://www.crtc.gc.ca/eng/archive/2011/2011-609.htm|archive-date=July 12, 2012))</ref> to their ITMP policy, allowing them to send the complaint to their Enforcements Division. The Canadian Gamers Organization in their submissions alluded to filing a complaint against Bell Canada. On December 20, 2011, Bell Canada announced they would end throttling by March 31, 2012 for their customers, as well as their wholesale customers.<ref>((cite news|url=http://www.cbc.ca/news/technology/story/2011/12/20/technology-bell-throttling-crtc.html|title=Bell to stop internet throttling|year=2011|access-date=April 21, 2012|publisher=CBC News|url-status=live|archive-url=https://web.archive.org/web/20120419160703/http://www.cbc.ca/news/technology/story/2011/12/20/technology-bell-throttling-crtc.html|archive-date=April 19, 2012))</ref> On February 4, 2012, in an effort to get out of trouble with the CRTC (which had continued its own testing and had found additional non-compliance and demanded immediate compliance), Rogers announced 50% of their customers would be throttle-free by June 2012, and 100% of their customers would be throttle-free by the end of 2012.<ref>((cite news|url=http://www.cbc.ca/news/technology/story/2012/02/03/tech-rogers-throttling.html|title=Rogers promises to end internet throttling|year=2012|access-date=April 21, 2012|publisher=CBC News|url-status=live|archive-url=https://web.archive.org/web/20120427164122/http://www.cbc.ca/news/technology/story/2012/02/03/tech-rogers-throttling.html|archive-date=April 27, 2012))</ref> Unfortunately for Rogers, this did not mollify the CRTC Enforcements Division.

ISPs in Canada that throttle bandwidth:
* Acanac: No
* Altima telecom: No
* [[Bell Canada]]: No<ref>((cite web |url=https://www.theverge.com/2011/12/23/2656618/bell-canada-ends-internet-throttling-usage-based-billing |title=Bell Canada ends internet throttling in favor of usage-based billing |author=<!--Not stated--> |date=23 December 2011 |website=www.theverge.com |publisher=The Verge |access-date= 8 November 2019|quote=ISP Bell Canada has announced that it will stop throttling peer-to-peer file-sharing next year))</ref>
* [[Cogeco Cable]]: No
* [[DeryTelecom]]: Yes (Netflix)
* [[Distributel]]: Yes
* [[Bell MTS]]: No (Only with unlimited data mobile devices)
* [[Oxio (ISP)|Oxio]]: No
* [[Rogers Cable]]: Yes (Netflix) (Android)
* [[SaskTel]]: Yes
* [[Primus Telecom]]: No
* [[Shaw Communications|Shaw]]: Yes (25% of the traffic)
* [[Xplornet]]: Yes, and also prioritizes VoIP
* [[TELUS]]: Yes(2% of the traffic)
* [[EastLink (company)|EastLink]]: Yes – The public statement was "Confidential".
* Sunwire Cable: No<ref name="Sunwire Residential Support's Frequently Asked Questions">((cite web |url=https://www.sunwire.ca/residential/support/faq/ | title=Sunwire Support FAQ))</ref>
* Sunwire DSL: No<ref name="Sunwire Residential Support's Frequently Asked Questions" />
* [[Teksavvy]] Cable: No
* Teksavvy DSL: No
* Teksavvy DSL MLPPP: No
* Talk Wireless Inc.: Yes
* Internet Lightspeed Cable: No
* Internet Lightspeed DSL: No
* Internet Lightspeed Bonded (MLPPP): No

===Europe===
In April 2011, the [[European Union]] launched an investigation into Internet service providers' methods for managing traffic on their networks. Some ISPs, for instance, restrict access to services such as [[Skype]] or the BBC iPlayer at peak times so that their users all receive an equal service. The EU's commissioner for the digital agenda, [[Neelie Kroes]], said: "I am absolutely determined that everyone in the EU should have the chance to enjoy the benefits of an open and lawful Internet, without hidden restrictions or slower speeds than they have been promised." The Body of European Regulators for Electronic Communications (Berec) will examine the issues for the EU, and will ask both businesses and consumers for their views. The EU published the results of its investigation at the end of 2011.<ref>((cite news |url=https://www.telegraph.co.uk/technology/internet/8462422/EU-launches-net-neutrality-investigation.html |title=EU launches net neutrality investigation |author=Matt Warman |date=April 20, 2011 |work=The Telegraph |access-date=May 3, 2011 |location=London |url-status=live |archive-url=https://web.archive.org/web/20110426010403/http://www.telegraph.co.uk/technology/internet/8462422/EU-launches-net-neutrality-investigation.html |archive-date=April 26, 2011 ))</ref> New laws mean that ISPs are prohibited from blocking or slowing down of Internet traffic, except where necessary.<ref>((cite web | url=https://berec.europa.eu/eng/netneutrality/ | title=All you need to know about Net Neutrality rules in the EU &#124; BEREC ))</ref>

===Singapore===
In Singapore, [[net neutrality]] has been the law since 2011. November 2010, defined by the [[Infocomm Development Authority of Singapore|Infocomm Development Authority]] (IDA).<ref>((cite web|title=NET NEUTRALITY|url=https://www.ida.gov.sg/~/media/Files/PCDG/Consultations/20101111_Neteutrality/NetNeutralityExplanatoryMemo.pdf|access-date=28 April 2015|url-status=dead|archive-url=https://web.archive.org/web/20150721221250/http://www.ida.gov.sg/~/media/Files/PCDG/Consultations/20101111_Neteutrality/NetNeutralityExplanatoryMemo.pdf|archive-date=2015-07-21))</ref> But despite the law, the majority of the [[Internet service provider|ISPs]] do throttle bandwidth.

ISPs in Singapore that throttle bandwidth:<ref>((cite web|title=Bad ISPs|url=https://wiki.vuze.com/w/Bad_ISPs#Singapore|access-date=28 April 2015|url-status=live|archive-url=https://web.archive.org/web/20150428015041/http://wiki.vuze.com/w/Bad_ISPs#Singapore|archive-date=28 April 2015))</ref>
{| class="sortable wikitable"
|-
! ISP Name !! Limits bandwidth
|-
| [[Starhub]] || Yes 
|-
| [[Singtel]] || Yes<ref>((cite web|title=Does SingNet perform any network management activities?|url=http://www.singnet.com.sg/technical/broadband/qns/adsltech.html#Q10|access-date=28 April 2015|url-status=dead|archive-url=https://web.archive.org/web/20150326031738/http://www.singnet.com.sg/technical/broadband/qns/adsltech.html#Q10|archive-date=26 March 2015))</ref>
|-
| [[M1 Limited]] || Yes 
|-
| [[MyRepublic]] || No<ref>((cite web|title=Does MyRepublic throttle BitTorrent / P2P traffic?|url=https://support.myrepublic.com.sg/hc/en-us/articles/202899034-Does-MyRepublic-throttle-BitTorrent-P2P-traffic-|access-date=28 April 2015|url-status=dead|archive-url=https://web.archive.org/web/20160304103402/https://support.myrepublic.com.sg/hc/en-us/articles/202899034-Does-MyRepublic-throttle-BitTorrent-P2P-traffic-|archive-date=4 March 2016))</ref>
|-
| Viewqwest || No
|-
|}

===United States===
((update|FCC [[net neutrality]] rules|date=September 2015))
In 2007, [[Comcast]] was caught interfering with peer-to-peer traffic. Specifically, it falsified packets of data that fooled users and their peer-to-peer programs into thinking they were transferring files.<ref>((cite web |url=http://www.nbcnews.com/id/21376597 |title=Comcast blocks some Internet traffic |author=Peter Svensson |date=2007-10-19 |publisher=Associated Press |access-date=May 3, 2011))</ref> Comcast initially denied that it interfered with its subscribers' uploads, but later admitted it.<ref>((cite web |url=http://news.cnet.com/8301-13578_3-10004508-38.html |title=FCC formally rules Comcast's throttling of BitTorrent was illegal |author=Declan McCullagh |date=August 1, 2008 |publisher=CNET News |access-date=May 3, 2011 |url-status=live |archive-url=https://web.archive.org/web/20111110153951/http://news.cnet.com/8301-13578_3-10004508-38.html |archive-date=November 10, 2011 ))</ref> The FCC held a hearing and concluded that Comcast violated the principles of the Internet Policy Statement because Comcast's "discriminatory and arbitrary practice unduly squelched the dynamic benefits of an open and accessible Internet and did not constitute reasonable network management."<ref>((cite conference |url=http://cyberlaw.stanford.edu/system/files/FccComcastOrder.pdf |title=Comcast Memorandum Opinion and Order |author=FCC |date=2008-08-01 |url-status=dead |archive-url=https://web.archive.org/web/20110801224516/http://cyberlaw.stanford.edu/system/files/FccComcastOrder.pdf |archive-date=2011-08-01 ))</ref> The FCC also provided clear guidelines to any ISP wishing to engage in reasonable network management. The FCC suggested ways that Comcast could have achieved its goal of stopping network congestion, including capping the average user's capacity and charging the most aggressive users overage (going over a maximum) fees, throttling back the connections of all high capacity users, or negotiating directly with the application providers and developing new technologies.<ref>((cite journal |author=Michael P. Murtagh |year=2008 |title=The FCC, the DMCA, and Why Takedown Notices Are Not Enough |journal=[[Hastings Law Journal]] |volume=61 |issue=233 |pages=242–243 |publisher=University of California |url=http://uchastings.edu/hlj/archive/vol61/Murtagh_61-HLJ-233.pdf |access-date=2011-05-03 |url-status=dead |archive-url=https://web.archive.org/web/20110927174951/http://uchastings.edu/hlj/archive/vol61/Murtagh_61-HLJ-233.pdf |archive-date=2011-09-27 ))</ref>

However, in 2008, [[Comcast]] amended their Acceptable Usage Policy and placed a specific 250 GB monthly cap. Comcast has also announced a new bandwidth-throttling plan. The scheme includes a two-class system of "priority-best-effort" and "best-effort" where "sustained use of 70% of your up or downstream throughput triggers the BE state, at which point you'll find your traffic priority lowered until your usage drops to 50% of your provisioned upstream or downstream bandwidth for "a period of approximately 15 minutes". A throttled Comcast user being placed in a BE state "may or may not result in the user's traffic being delayed or, in extreme cases, dropped before PBE traffic is dropped". Comcast explained to the FCC that "If there is no congestion, packets from a user in a BE state should have little trouble getting on the bus when they arrive at the bus stop. If, on the other hand, there is congestion in a particular instance, the bus may become filled by packets in a PBE state before any BE packets can get on. In that situation, the BE packets would have to wait for the next bus that is not filled by PBE packets".<ref>((cite web |url=http://www.dslreports.com/shownews/New-Comcast-Throttling-System-100-Online-100015 |title=New Comcast Throttling System 100% Online |author=Karl Bode |date=January 5, 2009 |access-date=March 14, 2011 |url-status=live |archive-url=https://web.archive.org/web/20110810104724/http://www.dslreports.com/shownews/New-Comcast-Throttling-System-100-Online-100015 |archive-date=August 10, 2011 ))</ref>

US cell phone ISP's have also increasingly resorted to bandwidth throttling in their networks. [[Verizon]] and [[AT&T]] even applied such throttling to data plans advertised as "unlimited", resulting an FCC complaint against Verizon.((citation needed|date=September 2019)) Though AT&T had told its customers throttling was a possibility, the FTC filed a lawsuit against the company in 2014, charging that the disclosure was insufficiently specific.<ref>((cite news |url=https://www.nytimes.com/2014/10/29/technology/FTC-says-ATT-deceived-consumers-on-unlimited-data-plan.html |title=AT&T Accused of Deceiving Smartphone Customers With Unlimited Data Plans |author=Edward Wyatt |newspaper=The New York Times |date=October 28, 2014 |access-date=October 29, 2014 |url-status=live |archive-url=https://web.archive.org/web/20141029143304/http://www.nytimes.com/2014/10/29/technology/FTC-says-ATT-deceived-consumers-on-unlimited-data-plan.html |archive-date=October 29, 2014 ))</ref> A nation-wide study of video streaming speeds in 2018-2019 found major wireless carriers throttling a majority of the time, including when traffic was light, and with significant discrepancies between video services.<ref>[https://www.bostonglobe.com/business/2019/08/19/wireless-carrier-throttling-online-video-pervasive/Kduc91RgQ3AxM8UEhItYoM/story.html Wireless carrier throttling of online video is pervasive]</ref>

===Uruguay===
[[Antel]] has a state-enforced monopoly forcing consumers who require non-wireless Internet access (i.e. ADSL or fiber – cable Internet is outlawed<ref>[http://www.elobservador.com.uy/noticia/103433/solo-cuba-y-uruguay-no-ofrecen-internet-por-cable-modem/ Only Cuba and Uruguay don't offer Internet access via cable modem (In Spanish)] ((webarchive|url=https://web.archive.org/web/20130514135318/http://www.elobservador.com.uy/noticia/103433/solo-cuba-y-uruguay-no-ofrecen-internet-por-cable-modem/ |date=2013-05-14 ))</ref>) to purchase it directly from Antel. Its practices provide insight into the probable behavior of ISPs in markets that have little or no competition and/or lack balancing regulations in the interest of consumers. All of Antel's Internet access plans for consumers are either capped or throttled. Capped plans are typically marketed under the brand "flexible". On such plans once a user reaches a data tier (e.g. 5&nbsp;GB) additional data usage is billed at a rate of approximately $5 US/GB. Once a second tier is reached (e.g., 15&nbsp;GB), Internet services are suspended until the start of the next billing cycle. Throttled plans are typically marketed under the brand "Flat Rate" (for ADSL) and "Vera" (for fiber.) Such plans allow full bandwidth on the connection (e.g. 20 Mbit/s down on the Vera fiber plan) from the beginning of the billing month but are restricted to a percentage of the contracted transmission rate (e.g., to 2Mbit/s down, or 10% of the advertised speed) once a data tier (e.g. 150&nbsp;GB) is reached. Full bandwidth capability is restored at the beginning of the next billing month.<ref>[[Telecommunications in Uruguay]]</ref><ref>[https://archive.today/20130114063450/http://www.antel.com.uy/antel/personas-y-hogares/internet/planes/ Planes de Internet] – Antel</ref>

==Metrics for ISPs==
Whether aimed at avoiding network congestion or at pushing users to upgrade to costlier Internet plans, the increasingly common capping and throttling practices of ISPs undoubtedly have an effect on the value proposition of the plans they offer. For consumers to be able to make an informed decision when choosing an Internet plan, ISPs should publish their capping and throttling practices with the necessary level of detail. While the net effect of some throttling and capping strategies can be hard to compare across ISPs, some basic metrics that are of interest for any kind of throttled/capped Internet connection are:
* '''Maximum monthly payload:''' This is the amount of data that an Internet connection would be able to carry in a hypothetical setting assuming no bottlenecks external to the ISP. In the example Antel 20Mbs fiber connection (see ''Uruguay'' above), the maximum monthly payload in that hypothetical setting would be reached by running the connection at 20Mbs for the first 150 GB, and at 2Mbs for the rest of the month. Thus the maximum monthly payload of that connection is 60,000 seconds * 2.5 MB/s + 2,532,000 seconds * 0.25 MB/s = 783 GB (about the size of a large laptop disk drive in 2013.)
* '''Maximum utilization percentage:''' This is the ratio of the maximum monthly payload of a throttled Internet connection to the maximum unthrottled monthly payload of the same connection. In the example Antel fiber 20Mbs connection the maximum unthrottled monthly payload of that connection is 2,592,000 seconds * 2.5 MB/s = 6,480 GB. Thus the maximum utilization percentage of that connection is 783 GB / 6,480 GB = 12%
* '''Throttling percentage:''' This represents how much the maximum monthly payload of an Internet connection gets reduced by the ISP's throttling policy. It is calculated simply as 1 − maximum utilization percentage. In the example Antel fiber 20Mbs connection it is 1 − 12% = 88%
* '''Equivalent connection bandwidth''': This is the bandwidth of an unthrottled Internet connection whose maximum monthly payload is the same as the maximum monthly payload of the throttled connection in question. This can be calculated as unthrottled connection bandwidth * throttling percentage. In the example Antel fiber 20Mbs connection the equivalent connection bandwidth is 20 Mbs * 12% = 2.4 Mbs
* '''Cost per unit payload''': The ultimate metric of throttling's effect on an Internet connection's potential value to a customer is the cost per GB (or TB in the case of fast connections) carried assuming perfect utilization of the connection. It is calculated by dividing the monthly cost of the connection by the maximum monthly payload. In the example Antel fiber 20 Mbs connection it would be US$36 / 0.783 TB = US$46 per TB. By comparison, if the same 20Mbs connection weren't throttled by the ISP it would have a cost per unit payload of US$36 / 6.48 TB = US$5.6 per TB
* '''Unthrottled connection cost:''' This is how much it would cost the customer to offset the effect of throttling by aggregating throttled Internet connections from the ISP. It is calculated by dividing the monthly cost of a throttled connection by the throttling percentage. In the example Antel fiber connection the cost of building an unthrottled 20Mbit/s fiber Internet connection by aggregating 20Mbit/s throttled ones would be US$36 / 12% = US$300 per month

==User responses  ==
Although ISPs may actively throttle bandwidth, there are several known methods to bypass the throttling of a user's bandwidth, if the throttling is focused on a particular protocol. These methods, nicknamed "workarounds", include:<ref>((cite web |url=http://filesharefreak.com/tutorials/workarounds-for-bandwidth-throttling/ |title=Workarounds For Bandwidth Throttling |author=Remisser |access-date=April 26, 2011 |url-status=dead |archive-url=https://web.archive.org/web/20110303193711/http://filesharefreak.com/tutorials/workarounds-for-bandwidth-throttling/ |archive-date=March 3, 2011 ))</ref>
* [[Virtual private network]] (VPN) – Generally costs a monthly fee to rent, but offers users a secure connection where data cannot be intercepted.
* Force Encryption<ref>((cite web |url=https://www.scribd.com/doc/273456/Optimize-BitTorrent-to-outwit-traffic-shaping-ISPs |title=Optimize BitTorrent to outwit traffic shaping ISPs |access-date=April 26, 2011 |url-status=live |archive-url=https://web.archive.org/web/20121107082727/http://www.scribd.com/doc/273456/Optimize-BitTorrent-to-outwit-traffic-shaping-ISPs |archive-date=November 7, 2012 ))</ref> – Free method that works for some users.
* [[Seedbox]] – A dedicated private server, usually hosted offshore, that offers high speed upstream and downstream rates and often storage for a relatively high monthly cost.
* SSH Tunneling – [[Tunneling protocol]]

==See also==
*[[Bandwidth management]]
*[[Rate limiting]]

==References==
((Reflist|2))

[[Category:Broadband]]
[[Category:Data transmission]]
[[Category:Net neutrality]]

Pages transcluded onto the current version of this page (help):

Bandwidth throttling (edit)
Template:Ambox (view source) (template editor protected)
Template:Ambox globe (view source) (template editor protected)
Template:Ambox globe current red (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite conference (view source) (protected)
Template:Cite court (view source) (template editor protected)
Template:Cite journal (view source) (protected)
Template:Cite news (view source) (protected)
Template:Cite web (view source) (protected)
Template:Color (view source) (template editor protected)
Template:Delink (view source) (protected)
Template:Fix (view source) (protected)
Template:Fix/category (view source) (protected)
Template:Hlist/styles.css (view source) (protected)
Template:If all (view source) (template editor protected)
Template:If empty (view source) (protected)
Template:Main (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:More citations needed section (view source) (template editor protected)
Template:Net neutrality (edit)
Template:Network neutrality (edit)
Template:Nowrap (view source) (protected)
Template:Pagetype (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (protected)
Template:SUBJECTSPACE formatted (view source) (template editor protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Sidebar (view source) (template editor protected)
Template:Sp (view source) (template editor protected)
Template:Strong (view source) (template editor protected)
Template:Update (view source) (template editor protected)
Template:Webarchive (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Delink (view source) (protected)
Module:Disambiguation (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Format link (view source) (template editor protected)
Module:Hatnote (view source) (template editor protected)
Module:Hatnote/styles.css (view source) (template editor protected)
Module:Hatnote list (view source) (template editor protected)
Module:If empty (view source) (protected)
Module:Labelled list hatnote (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Redirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:Sidebar (view source) (template editor protected)
Module:Sidebar/configuration (view source) (template editor protected)
Module:Sidebar/styles.css (view source) (template editor protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Webarchive (view source) (template editor protected)
Module:Webarchive/data (view source) (template editor protected)
Module:Yesno (view source) (protected)

Return to Bandwidth throttling.

Retrieved from "https://en.wikipedia.org/wiki/Bandwidth_throttling"