Request for information: ISPs and P2P throttling

Printable View

Show 40 post(s) from this thread on one page

10-19-2013, 06:47 AM
Xanatos

ISP - O2 Broadband (Soon to be Sky)
Location - England, UK
Time - Always. All day, every day.
10-19-2013, 07:19 AM
LeetFade

ISP - Time Warner Cable
Location - Cincinnati, OH
Time - Constant
10-19-2013, 08:34 AM
Firestar

- Cox Communications
- Virginia
- Random, some days are fine others it takes 2 minutes to pull up the exit menu and leave the game
10-19-2013, 09:13 AM
Bolvaga

-GVT
-Juiz de Fora-Brazil
-Time - Always!
-Spells are slow, moving out of aoe is impossible.
-Ran several speed test, connection is great. Every other online game is ok.
10-19-2013, 07:10 PM
LucianLunar

Quote:

Originally Posted by Aethingie

Hi all,

As posted elsewhere before, we are investigating issues that might be caused by ISPs classifying FINAL FANTASY XIV: A Realm Reborn as P2P software.

To give us a clearer view on how widespread this issue is, it would be much appreciated if everyone who experienced such issues could post the following information as a reply to this thread:
- Name of ISP
- Country of Residence
- When does the problem occur (always, only during specific times?)
- Reference number from your ISP, if you raised this matter with them

Again, my apologies for the trouble this is causing and thank you for your cooperation!
- Aethingie

-Verizon
-United States
-approximately 4:30AM and 5:AM Eastern Standard Time
10-19-2013, 07:15 PM
LucianLunar

Extreme Lag on late night plays

-Verizon
-United States
-approximately 4:30AM and 5:AM Eastern Standard Time

-Throughout the day the game works perfectly fine, but then at the time listed a live things get extreme and unplayable. My friends are also experiencing it when I do as well. Heavy Lag
10-19-2013, 11:59 PM
DeathScythe86

Please Do Something

ISP: SaudiTelecomCompany (STC)
Country: Saudi Arabia
Lag Occurrence: Always

I tried to to ping this IP address 199.91.189.60 as it is Ragnarok's according to this site and the average was 200ms and the EU datacenter (IP: 209.130.141.243) averaged at 169ms :(
I can't finish end game content like this, please help.
http://www.speedtest.net/result/3043671970.png
10-20-2013, 02:38 AM
C-croft

Quote:

Originally Posted by C-croft

This is what is happening to Californians below. Once we get routed to San Jose, we take a shit all the way to the Data Center. I am on AT&T, and I have seen other posts stating this happens on TWC in SoCal. It gets worse during prime time.

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 3 ms 2 ms 2 ms homeportal [192.168]
2 29 ms 46 ms 24 ms 108-192-172-2.lightspeed.frokca.sbcglobal.net [1
08.192.172.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 27 ms 23 ms 25 ms 12.83.77.145
7 26 ms 26 ms 26 ms ggr4.sffca.ip.att.net [12.122.86.197]
8 28 ms 28 ms 28 ms 192.205.37.66
9 101 ms 100 ms 100 ms if-1-2.tcore2.SQN-SanJose.as6453.net [63.243.205
.2]
10 118 ms 101 ms 107 ms if-5-2.tcore2.PDI-PaloAlto.as6453.net [64.86.21.
2]
11 122 ms 102 ms 100 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.14
4.58]
12 145 ms 106 ms 103 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
13 101 ms 101 ms 100 ms 66.198.96.58
14 101 ms 100 ms 102 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
15 102 ms 101 ms 101 ms 72.55.128.44
16 100 ms 101 ms 101 ms 184.107.107.176

Trace complete.

- AT&T U-verse
- Sacramento, CA, USA
- Persistent issue, gets worse during prime time

Trace route to ip according to arrstatus.com

Tracing route to 199.91.189.26 over a maximum of 30 hops

1 3 ms 3 ms 2 ms homeportal [192.168.1.254]
2 29 ms 23 ms 43 ms 108-192-172-2.lightspeed.frokca.sbcglobal.net [1
08.192.172.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 27 ms 22 ms 23 ms 12.83.77.145
7 27 ms 26 ms 26 ms ggr4.sffca.ip.att.net [12.122.86.197]
8 28 ms 28 ms 41 ms 192.205.37.66
9 130 ms 100 ms 100 ms if-1-2.tcore2.SQN-SanJose.as6453.net [63.243.205
.2]
10 101 ms 101 ms 104 ms if-5-2.tcore2.PDI-PaloAlto.as6453.net [64.86.21.
2]
11 101 ms 101 ms 100 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.14
4.58]
12 114 ms 99 ms 100 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
13 101 ms 100 ms 101 ms 66.198.96.50
14 101 ms 101 ms 101 ms 192.34.76.2
15 100 ms 100 ms 100 ms 199.91.189.234
16 100 ms 100 ms 100 ms 199.91.189.26

Trace complete.
10-20-2013, 07:13 AM
sateenropinaa

ISP: TeliaSonera Finland Oyj
Country: Finland
When: Always.
Details: I have to overextend my every dodge waaaaayy out of the red zone to properly avoid damage. Also during primetime, 18-22 GMT+3, it is worse and every pc stutters/rubberbands as they move.

http://www.speedtest.net/result/3044420935.png
10-20-2013, 03:25 PM
javanoam

- Time Warner Cable
- USA
- I play in the evening, so that's the only time I can speak about.
- Had a bizarre conversation with support. I repeatedly posed the question "I understand a game I play may be mistaken for p2p software am I being throttled." I was then asked, so I understand your having trouble with your modem, my modem was reset, etc. I said no actually my connection is fine, my modem is fine, this one particular game is giving me high latency, are you throttling me because of this game? My question was ignored and he talked about port forwarding and DMZ...I asked again..After a long pause he said "so...what do you mainly do with p2p software?" I said um "nothing, since I don't have a single piece of p2p software." He asked what devices I have, then said we never throttle and I was just assuming that, since I guess a question means I assume it? So yeah, no clue guys.
10-20-2013, 09:33 PM
Helban

-Toya
-Poland
-Always, takes forever for the NPC's to appear, the abilities are going off, but the sound effects/everything else comes late etc.
10-20-2013, 10:33 PM
OrangeChaffinch

-Neostrada
-Poland
-Always, not a problem when not doing something that needs quick reaction time. But every time there is a need to dodge fast i always get hit by something i ran out of 1-3 seconds ago.
Sometimes also stuff freezes and resumes after 5-10 seconds.
10-21-2013, 03:04 AM
SoulEcho

Throttling during evenings hours

- Axxess/Afrihost
- South Africa
- 18:00 to 21:00 GMT+2 ( get cosntant lag spikes and delay)
10-21-2013, 08:26 AM
WindDaburr

-Optimun Online (Subsidiary of Time Warner Cable)
-United States
-Recently 24 hours a day, was only on weekends before.
-Have not
10-21-2013, 08:44 AM
Ashdam

- Name of ISP: Jazztel
- Country of Residence: Spain
- When does the problem occur (always, only during specific times?): Always
- Reference number from your ISP, if you raised this matter with them
10-21-2013, 11:38 AM
Brannigan

Time Warner Cable (Desert Cities)
United States
Used to be intermittently, now getting rubberbanding 24/7

When I use the program Pingzapper and go through Los Angeles, this problem disappears. Unfortunately, with a trial account I can only stay connected for an hour before having to relog, and I don't really want to use their service for just FFXIV.
10-21-2013, 04:25 PM
AnAntiSocialCat

-Entanet
-England, UK
-Randomly all day, constantly during peak hours. Freezes, takes 3-5secs and all catches up. AoE impossible. (Only started on 10th October, was perfect before then)
10-21-2013, 09:50 PM
Bloodwillow

- Name of ISP - Comcast
- Country of Residence - United States - Pennsylvania
- When does the problem occur (always, only during specific times?) - Always on weekends. Weekdays ususally after 5pm EST
- Reference number from your ISP, if you raised this matter with them - Pffft they say nothing is wrong. No matter what I bring up

I've done tracert to even the Lodestone or a server in Japan and I constantly time out or the ping is off the charts. Totally unacceptable.
10-22-2013, 03:50 AM
LordRakirian

- T3
- Sweden
- Sometimes during the day. Every evening and night, as peak time comes closer so does the latency/lag spikes 3-5 sec to 10-20 sec.
10-22-2013, 05:04 AM
sirbranedamuj

Xfinity/Comcast
DC, USA
Always occurs.

It's usually very brief instances of extreme lag during which everything int he world stops moving, then quickly resumes once the connection is re-established. The IP I'm using is one of the server IPs as listed on the unofficial ARR server status page.

C:\Users\Zach>ping -t 199.91.189.39

Pinging 199.91.189.39 with 32 bytes of data:
Reply from 199.91.189.39: bytes=32 time=117ms TTL=243
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=102ms TTL=243
Reply from 199.91.189.39: bytes=32 time=105ms TTL=243
Reply from 199.91.189.39: bytes=32 time=94ms TTL=243
Reply from 199.91.189.39: bytes=32 time=110ms TTL=243
Reply from 199.91.189.39: bytes=32 time=104ms TTL=243
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=112ms TTL=243
Reply from 199.91.189.39: bytes=32 time=90ms TTL=243
Reply from 199.91.189.39: bytes=32 time=101ms TTL=243
Reply from 199.91.189.39: bytes=32 time=108ms TTL=243
Reply from 199.91.189.39: bytes=32 time=98ms TTL=243
Reply from 199.91.189.39: bytes=32 time=105ms TTL=243
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=108ms TTL=243
Reply from 199.91.189.39: bytes=32 time=106ms TTL=243
Reply from 199.91.189.39: bytes=32 time=98ms TTL=243
Reply from 199.91.189.39: bytes=32 time=105ms TTL=243
Request timed out.
Request timed out.
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=94ms TTL=243
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=107ms TTL=243
Reply from 199.91.189.39: bytes=32 time=116ms TTL=243
Reply from 199.91.189.39: bytes=32 time=96ms TTL=243
Reply from 199.91.189.39: bytes=32 time=108ms TTL=243
Reply from 199.91.189.39: bytes=32 time=102ms TTL=243
Reply from 199.91.189.39: bytes=32 time=101ms TTL=243
Reply from 199.91.189.39: bytes=32 time=106ms TTL=243
Reply from 199.91.189.39: bytes=32 time=100ms TTL=243

Ping statistics for 199.91.189.39:
Packets: Sent = 32, Received = 30, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 117ms, Average = 103ms

C:\Users\Zach>tracert 199.91.189.39

Tracing route to 199.91.189.39 over a maximum of 30 hops

1 3 ms 3 ms 2 ms 10.0.0.1
2 38 ms 30 ms 15 ms c-69-143-232-1.hsd1.md.comcast.net [69.143.232.1
]
3 12 ms 12 ms 12 ms xe-4-1-0-32767-sur01.hyattsville.md.bad.comcast.
net [68.85.147.37]
4 12 ms 26 ms 10 ms ae-23-0-ar04.capitolhghts.md.bad.comcast.net [68
.85.114.113]
5 16 ms 12 ms 16 ms he-5-2-0-0-10-cr01.ashburn.va.ibone.comcast.net
[68.86.90.241]
6 14 ms 14 ms 31 ms be-16-pe04.ashburn.va.ibone.comcast.net [68.86.8
4.226]
7 11 ms 13 ms 14 ms xe-7-0-2.was10.ip4.tinet.net [77.67.71.193]
8 116 ms 97 ms 107 ms xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
9 104 ms 104 ms 102 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 106 ms 94 ms 96 ms 192.34.76.2
11 107 ms 106 ms 110 ms 199.91.189.234
12 105 ms 106 ms 108 ms 199.91.189.39

Trace complete.
10-22-2013, 05:38 AM
Honkatonky

Wide Open West
Detroit Michigan, USA
1:00 - 5:00 PM est. every day but it is the worst during the week.
10-22-2013, 07:35 AM
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.
10-22-2013, 11:02 AM
Everdark

Name of ISP: Adam Internet
Residence: Adelaide, Australia
Occurrence: ALL THE TIME.
10-22-2013, 11:51 AM
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.
10-22-2013, 12:05 PM
Carnage

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

Quote:

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.

----------------------------------------------------------------------
10-22-2013, 12:07 PM
BassGhost

- Cox Communications
- US
- 6-10p PST
10-22-2013, 01:04 PM
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.
10-22-2013, 04:36 PM
Spoko

lag fest

ISP: Vectra
Location: Poland
Time: random days (happend yesterday, on sunday almost none), 7p.m. - 11 p.m. CEST
10-22-2013, 06:59 PM
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.

http://i277.photobucket.com/albums/k...13/tracert.png
10-23-2013, 02:56 AM
Kwyjibo

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

Tracert:
http://i.imgur.com/ZKjWpk8.jpg

Ping:
http://i.imgur.com/B7vHdwc.jpg

Internet Connection:
http://i.imgur.com/sY5Ovbs.jpg

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

Thanks,
10-23-2013, 03:17 AM
Ervin

Still having issues.

Location: Sweden
ISP: Bredbandsbolaget
Time: 18.00-21.00CET or 19.00-22.00CET, it's a bit random. Was kinda decent for a few weeks until the last patch hit.

This is far from acceptable since it's a sub-to play game. I'ts the first game since I started MMO gaming where I've had this issue and I started back in DaoC years and years ago when you would expect issues since MMOs was kinda new. They really need to fix this, either by changing something within their servers/the game or contacting and straightening it out with all effected ISPs. Otherwise they wont have my money for long.
10-23-2013, 04:20 AM
Klingsan

Problems here too.

Location: Sweden
ISP: Telia
Time: from around 6-7PM till midnight
10-23-2013, 04:46 AM
Rohirrim

-Otenet Hellas
-Greece
-Always

tracert
http://i.imgur.com/SdgKDJ7.png

ping
http://i.imgur.com/BoLyjrs.png
10-23-2013, 05:17 AM
Golom

i have the same problems, rubberbanding to 3-7sec lag

Location: Sweden
ISP: bahnhof (i know they allow p2p)
Time: from around 6-7PM till midnight (GMT +1
10-23-2013, 05:42 AM
Mikolan

- Telia
- Sweden
- I've experienced severe lagspikes (10+ seconds) twice before, tonight marked the third time. Started around 21:00CET when I was in Coil.

I've identified the problem node in my route and it's 66.198.96.50, apparently owned by Tata Communications. Up until this node I have a consistent ~120ms connection, but when I hit that node I'm getting upwards of 30% packet loss at times.

Traceroute:

Code:

Tracing route to 199.91.189.19 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms unknown [192.168.1.1] 2 13 ms <1 ms <1 ms gw-n1-ekg-a12.ias.bredband.telia.com [90.225.79.193] 3 15 ms 2 ms 2 ms s-b1-link.telia.net [213.155.136.7] 4 15 ms 2 ms 2 ms s-b3-link.telia.net [80.91.249.250] 5 57 ms 4 ms 199 ms vsnl-ic-124239-s-b1.c.telia.net [213.248.104.162] 6 21 ms 9 ms 9 ms if-2-1-0.core2.OS1-Oslo.as6453.net [80.231.89.1] 7 108 ms 108 ms 108 ms if-1-3-1-0.tcore2.AV2-Amsterdam.as6453.net [80.231.152.41] 8 142 ms 136 ms 145 ms if-8-2.tcore2.L78-London.as6453.net [80.231.131.5] 9 122 ms 111 ms 109 ms if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13] 10 124 ms 116 ms 111 ms if-2-2.tcore2.MTT-Montreal.as6453.net [64.86.226.13] 11 124 ms 127 ms 130 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89] 12 111 ms 135 ms 111 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6] 13 169 ms 169 ms 169 ms 66.198.96.50 14 237 ms 175 ms 181 ms 192.34.76.2 15 172 ms 172 ms 167 ms 199.91.189.234 16 177 ms 159 ms 171 ms 199.91.189.19 Trace complete.

Up to here it's fine:

Code:

Ping statistics for 64.86.31.6: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 113ms, Maximum = 156ms, Average = 126ms

Problem node:

Code:

Ping statistics for 66.198.96.50: Packets: Sent = 100, Received = 92, Lost = 8 (8% loss), Approximate round trip times in milli-seconds: Minimum = 110ms, Maximum = 193ms, Average = 149ms
10-23-2013, 05:54 AM
Alixandir

I just wanted to say my problem is still ongoing now for several weeks.

Location: Sweden
ISP: Telia
Time: Rubberbanding all the time. Lag in instances progressively getting worse from 4:00 PM GMT up until midnight.

I have talked to myu ISP that assure me no throttling is being done on their part.
10-23-2013, 06:29 AM
Bokuhn

Same problem as the rest. . Horrible lag, rubberband effect, 5-15sec lag spikes

Location: United States, Florida
ISP: Comcast Xfinity
When does problem occur: Started on most recent patch, been having lag ever since. The game is unplayable.

Fix it.
Please.
10-23-2013, 09:52 AM
Kaori_Nisharu

Same problem.

Location: California, USA
ISP: Time Warner Cable
When does problem occur: All day long since last patch

Confirmed with TWC there is 5% intermittent packet loss to 184.107.107.176
10-23-2013, 10:29 AM
Cadger

As stated by a few other's PlusNET in the UK is definitely having issues. They do also have a thread open on their own forum, that is publicly accessible, and are looking into it. If a dev or rep could get involved with it, maybe it could speed things along. Link: http://community.plus.net/forum/inde...,118895.0.html

Although according to the thread it seems to be more a problem with their uplink suppliers than the routing within PlusNET themselves. There are a LOT of traceroutes within that thread that may help.
10-23-2013, 12:18 PM
Hannia

Experanceing huge spikes on Cactuar today
Location: VA
ISP: Comcast

heres the traceroute

Code:

Tracing route to 199.91.189.48 over a maximum of 30 hops 1 9 ms <1 ms <1 ms 192.168.1.1 2 7 ms 7 ms 7 ms 96.120.80.69 3 7 ms 7 ms 7 ms te-9-3-ur01.danville.va.richmond.comcast.net [68 .86.200.33] 4 15 ms 13 ms 12 ms xe-5-1-0-0-ar02.staplesmllrd.va.richmond.comcast .net [68.86.172.161] 5 24 ms 24 ms 22 ms pos-0-7-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.91.153] 6 30 ms 28 ms 27 ms pos-3-11-0-0-cr01.56marietta.ga.ibone.comcast.ne t [68.86.85.225] 7 * 36 ms * pos-0-3-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.87.134] 8 44 ms 44 ms 40 ms ix-0-2-0-0.tcore1.A56-Atlanta.as6453.net [209.58 .44.1] 9 68 ms 75 ms 74 ms if-25-2.tcore1.AEQ-Ashburn.as6453.net [64.86.113 .2] 10 70 ms 73 ms 63 ms 64.86.85.1 11 70 ms 73 ms 78 ms if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86 .32.33] 12 64 ms 66 ms 77 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.2 5] 13 68 ms 64 ms 64 ms if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96 .61] 14 67 ms 55 ms 53 ms 66.198.96.50 15 49 ms 49 ms 53 ms 192.34.76.2 16 56 ms 56 ms 51 ms 199.91.189.234 17 66 ms 61 ms 60 ms 199.91.189.48 Trace complete.

And here is another

Code:

Tracing route to 199.91.189.48 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 8 ms 7 ms 7 ms 96.120.80.69 3 7 ms 7 ms 15 ms te-9-3-ur01.danville.va.richmond.comcast.net [68 .86.200.33] 4 14 ms 15 ms 12 ms xe-5-1-0-0-ar02.staplesmllrd.va.richmond.comcast .net [68.86.172.161] 5 21 ms 24 ms 22 ms pos-0-9-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.95.65] 6 28 ms 29 ms 29 ms pos-3-11-0-0-cr01.56marietta.ga.ibone.comcast.ne t [68.86.85.225] 7 35 ms 30 ms 30 ms pos-0-3-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.87.134] 8 43 ms 43 ms 43 ms ix-0-2-0-0.tcore1.A56-Atlanta.as6453.net [209.58 .44.1] 9 69 ms 70 ms 66 ms if-25-2.tcore1.AEQ-Ashburn.as6453.net [64.86.113 .2] 10 82 ms 74 ms 64 ms 64.86.85.1 11 72 ms 79 ms 68 ms if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86 .32.33] 12 68 ms 77 ms 71 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.2 5] 13 70 ms 65 ms 67 ms if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96 .61] 14 55 ms 57 ms 69 ms 66.198.96.50 15 53 ms 49 ms 51 ms 192.34.76.2 16 50 ms 56 ms 54 ms 199.91.189.234 17 77 ms 62 ms 59 ms 199.91.189.48 Trace complete.

It seems that this one is my problem i need to know if i need to call my isp up and chew them out or what?

Code:

7 * 36 ms * pos-0-3-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.87.134]

Show 40 post(s) from this thread on one page