Newspaper article The Canadian Press

CRTC Gets 75 Complaints about Throttling against Internet Providers in 2012

Newspaper article The Canadian Press

CRTC Gets 75 Complaints about Throttling against Internet Providers in 2012

Article excerpt

CRTC gets 75 throttling complaints in 2012

--

The CRTC received 75 complaints of traffic throttling last year against Internet providers large and small, some with multiple complaints.

"There are providers who have had multiple complaints, but it does go the whole gamut of types of service providers," the CRTC's Lynne Fancy said Thursday.

From an Internet user's perspective, the traffic throttling can cause slower download speeds or jerky video streaming.

"It's generally individuals who are complaining," said Fancy, director general of competition, costing and regulatory implementation at the CRTC.

The Canadian Radio-television and Telecommunications Commission, which oversees the providers, didn't provide a list of companies that faced complaints in 2012.

Fancy said 11 of the 75 complaints were still being investigated.

Non-profit advocacy organization OpenMedia.ca said the onus remains on the consumer to report any traffic throttling to the CRTC.

Spokeswoman Lindsey Pinto said that process can be lengthy and complicated.

"The CRTC doesn't really have strong compliance or enforcement on this so it's kind of up to the consumer to report to the CRTC when they see discriminatory practices taking place," Pinto said.

"We're going to continue to see problems until some kind of enforcement regime is put into place."

The CRTC doesn't have the power to fine an Internet service provider for traffic throttling, but Fancy said "nothing stops us from continuing to investigate from our perspective if we would suspect that there was a trend or something's happening."

The CRTC doesn't have comparative statistics for 2011 because it changed the guidelines for complaints that year. …

Search by... Author
Show... All Results Primary Sources Peer-reviewed

Oops!

An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.