Request for information: ISPs and P2P throttling

[Honkatonky]

Wide Open West
Detroit Michigan, USA
1:00 - 5:00 PM est. every day but it is the worst during the week.

[kevsarus]

This company is a joke when it comes to technical support.

Been several weeks and they still can't fix this issue nor have they had a follow-up response.

Hope you guys lose all your subscribers.

[Everdark]

Name of ISP: Adam Internet
Residence: Adelaide, Australia
Occurrence: ALL THE TIME.

[Lucre]

Name of ISP: Cox Cable
Residence: San Diego, CA
Occurrence- every night

I dont suppose you guys could get around to fixing this. or telling us steps you're taking to fix it.

[Carnage]

- Cox Communications
- Phoenix, Arizona, USA
- All the time for the past month and a half

Reply from 199.91.189.43: bytes=32 time=122ms TTL=245
Reply from 199.91.189.43: bytes=32 time=121ms TTL=245
Reply from 199.91.189.43: bytes=32 time=121ms TTL=245
Reply from 199.91.189.43: bytes=32 time=121ms TTL=245
Request timed out.
Reply from 199.91.189.43: bytes=32 time=119ms TTL=245
Request timed out.
Reply from 199.91.189.43: bytes=32 time=114ms TTL=245
Reply from 199.91.189.43: bytes=32 time=119ms TTL=245
Reply from 199.91.189.43: bytes=32 time=120ms TTL=245
Reply from 199.91.189.43: bytes=32 time=118ms TTL=245
Reply from 199.91.189.43: bytes=32 time=119ms TTL=245
Reply from 199.91.189.43: bytes=32 time=137ms TTL=245

Ping statistics for 199.91.189.43:
Packets: Sent = 500, Received = 453, Lost = 47 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 145ms, Average = 119ms

-------------------------------------------------------------------

Reply from 199.91.189.43: bytes=32 time=114ms TTL=245
Reply from 199.91.189.43: bytes=32 time=119ms TTL=245
Reply from 199.91.189.43: bytes=32 time=120ms TTL=245
Reply from 199.91.189.43: bytes=32 time=116ms TTL=245
Reply from 199.91.189.43: bytes=32 time=118ms TTL=245
Request timed out.
Reply from 199.91.189.43: bytes=32 time=114ms TTL=245
Reply from 199.91.189.43: bytes=32 time=114ms TTL=245
Reply from 199.91.189.43: bytes=32 time=124ms TTL=245

Ping statistics for 199.91.189.43:
Packets: Sent = 250, Received = 226, Lost = 24 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 114ms, Maximum = 165ms, Average = 120ms

--------------------------------------------------------------------

Reply from 199.91.189.43: bytes=32 time=119ms TTL=245
Request timed out.
Reply from 199.91.189.43: bytes=32 time=118ms TTL=245
Reply from 199.91.189.43: bytes=32 time=122ms TTL=245
Reply from 199.91.189.43: bytes=32 time=114ms TTL=245
Reply from 199.91.189.43: bytes=32 time=115ms TTL=245
Reply from 199.91.189.43: bytes=32 time=124ms TTL=245
Reply from 199.91.189.43: bytes=32 time=114ms TTL=245
Reply from 199.91.189.43: bytes=32 time=116ms TTL=245
Reply from 199.91.189.43: bytes=32 time=115ms TTL=245
Reply from 199.91.189.43: bytes=32 time=128ms TTL=245
Reply from 199.91.189.43: bytes=32 time=117ms TTL=245
Request timed out.
Reply from 199.91.189.43: bytes=32 time=116ms TTL=245
Reply from 199.91.189.43: bytes=32 time=115ms TTL=245
Reply from 199.91.189.43: bytes=32 time=115ms TTL=245
Reply from 199.91.189.43: bytes=32 time=122ms TTL=245
Reply from 199.91.189.43: bytes=32 time=124ms TTL=245

Ping statistics for 199.91.189.43:
Packets: Sent = 100, Received = 89, Lost = 11 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 114ms, Maximum = 128ms, Average = 118ms

----------------------------------------------------------------------

C:\Windows\system32>tracert 199.91.189.43

Tracing route to 199.91.189.43 over a maximum of 30 hops

1 20 ms 9 ms 12 ms
2 4 ms 10 ms 20 ms
3 15 ms 12 ms 7 ms chndcorc01-pos-0-7-0-0.ph.ph.cox.net [70.169.72.
58]
4 10 ms 9 ms 10 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
5 19 ms 18 ms 24 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
6 23 ms 21 ms 21 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
7 104 ms 106 ms 111 ms xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
8 107 ms 108 ms 115 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
9 107 ms 110 ms 106 ms 192.34.76.2
10 116 ms 115 ms 126 ms 199.91.189.234
11 114 ms 117 ms 117 ms 199.91.189.43

Trace complete.

----------------------------------------------------------------------

[BassGhost]

- Cox Communications
- US
- 6-10p PST

[Pygar]

Ah, the sweep it under the rug, look like were doing something thread has yeilded no responses from SE.

Does anybody actually believe with $660 million + in developement costs and additional spending on their backend since launch that they would not have been on the phone with the ISP's demanding it be removed from a P2P throtteling tag.

Seriously doubtful.

[Spoko]

ISP: Vectra
Location: Poland
Time: random days (happend yesterday, on sunday almost none), 7p.m. - 11 p.m. CEST

[Synergist]

Name of ISP: PLDT( Philippine Long Distance Telephone) COmpany
Country: PHilippines
It occurs almost all the time, been getting high ping on JP server which in fact we should only have below 100.. having 240-270ms..

I reported this like for 5 times already and they're always saying there's no problem.

[Kwyjibo]

ISP: Shaw Communications
Country: Alberta, Canada
When does the problem occur: Constantly

Tracert:


Ping:


Internet Connection:


Short Youtube video of my screen in game:
In Game Lag (Rubberbanding)

Thanks,