Original Post — Direct link

Myself and a couple of other guys in my FC are having some crazy rubberbanding, random lagging out and high pings.

I'd like to know, are any of you guys having a similar problem recently?

Is this something we need to tell SE?

EDIT: Just ran a ping for a run of weeping city and this is a normal sample from the output lol!

Request timed out.

Reply from 195.82.50.47: bytes=32 time=33ms TTL=48

Reply from 195.82.50.47: bytes=32 time=28ms TTL=48

Reply from 195.82.50.47: bytes=32 time=33ms TTL=48

Reply from 195.82.50.47: bytes=32 time=29ms TTL=48

Reply from 195.82.50.47: bytes=32 time=29ms TTL=48

Reply from 195.82.50.47: bytes=32 time=30ms TTL=48

Reply from 195.82.50.47: bytes=32 time=31ms TTL=48

Reply from 195.82.50.47: bytes=32 time=28ms TTL=48

Request timed out.

Reply from 195.82.50.47: bytes=32 time=30ms TTL=48

Reply from 195.82.50.47: bytes=32 time=27ms TTL=48

Reply from 195.82.50.47: bytes=32 time=30ms TTL=48

Request timed out.

Reply from 195.82.50.47: bytes=32 time=28ms TTL=48

Request timed out.

Reply from 195.82.50.47: bytes=32 time=29ms TTL=48

Reply from 195.82.50.47: bytes=32 time=39ms TTL=48

Reply from 195.82.50.47: bytes=32 time=28ms TTL=48

Request timed out.

Reply from 195.82.50.47: bytes=32 time=30ms TTL=48

Reply from 195.82.50.47: bytes=32 time=32ms TTL=48

Reply from 195.82.50.47: bytes=32 time=29ms TTL=48

Request timed out.

Reply from 195.82.50.47: bytes=32 time=31ms TTL=48

Reply from 195.82.50.47: bytes=32 time=35ms TTL=48

Reply from 195.82.50.47: bytes=32 time=27ms TTL=48

Reply from 195.82.50.47: bytes=32 time=28ms TTL=48

External link →
over 8 years ago - /u/SE_Kahuna - Direct link

Hey there,

Ran a couple quick tests and they ran flawlessly, zero jitter as well. Might have been a temporary issue with the carrier. If you see similar problems regularly, feel free to tag me in posts using /u/SE_Kahuna - if I'm around I usually react to it.