Does anyone have telus?
Comments
-
have any of that for bell.ca?
Yes, I can run tests on any network that is reachable by ping/ICMP packets.
My server has the best network provider in the entire USA, so I would be able even to see the slightest issue.
Top of the line fiber optics.
I will need to know where you're from to get an IP nearby you to test to. -
-
JOONLEEEEE wrote: »I'm from Canada, British Columbia. I'm getting them too, and I use Telus as well.
Provide me with the first 3 digits of your IP and I will do some tests to nearby residents.
i.e, if your IP is 1.2.3.4 provide me with 1.2.3
I'll test the last IP range from 1-255 and see if they're spikes across the network.
how to get your IP:
http://www.whatsmyip.org/ -
Provide me with the first 3 digits of your IP and I will do some tests to nearby residents.
i.e, if your IP is 1.2.3.4 provide me with 1.2.3
I'll test the last IP range from 1-255 and see if they're spikes across the network.
how to get your IP:
http://www.whatsmyip.org/
Add me on xfire. joon98228 -
Yes, I can run tests on any network that is reachable by ping/ICMP packets.
My server has the best network provider in the entire USA, so I would be able even to see the slightest issue.
Top of the line fiber optics.
I will need to know where you're from to get an IP nearby you to test to.
no, that isn't the best... -
-
Telus - standard backbone stability test (VANCOUVER, CA)
Joon's diagnostic;
Pinging 207.81.32.2 with 32 bytes of data:
Reply from 207.81.32.2: bytes=32 time=120ms TTL=118
Reply from 207.81.32.2: bytes=32 time=137ms TTL=118
Reply from 207.81.32.2: bytes=32 time=180ms TTL=118
Reply from 207.81.32.2: bytes=32 time=203ms TTL=118
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 203ms, Average = 160ms
Jitter of ~80 (horrible)
2nd test;
Pinging 207.81.32.136 with 32 bytes of data:
Reply from 207.81.32.136: bytes=32 time=113ms TTL=54
Reply from 207.81.32.136: bytes=32 time=113ms TTL=54
Reply from 207.81.32.136: bytes=32 time=114ms TTL=54
Reply from 207.81.32.136: bytes=32 time=115ms TTL=54
Ping statistics for 207.81.32.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 115ms, Average = 113ms
~2 jitter (Good)
--Result--
Some network interruptions occuring, LLC problems on the lines nearby.
--KeLp--
Telus - standard backbone stability test (Thornhill, CA)
Pinging 76.67.101.1 with 32 bytes of data:
Reply from 76.67.101.1: bytes=32 time=43ms TTL=118
Reply from 76.67.101.1: bytes=32 time=43ms TTL=118
Reply from 76.67.101.1: bytes=32 time=43ms TTL=118
Reply from 76.67.101.1: bytes=32 time=43ms TTL=118
Ping statistics for 76.67.101.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 43ms, Average = 43ms
0 jitter, excellent result.
No network interruptions or problems found within ~19 miles.
Kelp, reset your modem.
Joon, contact ISP. -
Standard backbone stability test (Edmonton, CA)Also jon it isnt me 30-40 other people on a isp forum are complaining in my city also.
Pinging 68.151.252.1 with 32 bytes of data:
Reply from 68.151.252.1: bytes=32 time=96ms TTL=246
Reply from 68.151.252.1: bytes=32 time=99ms TTL=246
Reply from 68.151.252.1: bytes=32 time=96ms TTL=246
Reply from 68.151.252.1: bytes=32 time=97ms TTL=246
Ping statistics for 68.151.252.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 99ms, Average = 97ms
~3 jitter, no packet loss.
Give me your IP and I'll do you a favor and talk to their network manager. -
--KeLp--
Telus - standard backbone stability test (Thornhill, CA)
Pinging 76.67.101.1 with 32 bytes of data:
Reply from 76.67.101.1: bytes=32 time=43ms TTL=118
Reply from 76.67.101.1: bytes=32 time=43ms TTL=118
Reply from 76.67.101.1: bytes=32 time=43ms TTL=118
Reply from 76.67.101.1: bytes=32 time=43ms TTL=118
Ping statistics for 76.67.101.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 43ms, Average = 43ms
C:\Users\Administrator>
0 jitter, excellent result.
No network interruptions or problems found within ~19 miles.
Kelp, reset your modem.
KeLP* but it's okay
I have done that multiple times and in 30 minutes my ping goes up and internet goes slow and sometimes my internet crashes, could it be from traffic? or from my neighbour's using my internet? (it's locked so idk)
me and my isp have history of crappy modem's too.
by the way, thanks for the help -
JOONLEEEEE wrote: »I'm from Canada, British Columbia. I'm getting them too, and I use Telus as well.aWptitties wrote: »I have Telus and from BC but I'm not getting these lagg spikes, but my friends on FB are complaining about it.
where in bc? im from bc, i get lag spikes but only like once every 2 hours or so and mostly at night -
KeLP* but it's okay
I have done that multiple times and in 30 minutes my ping goes up and internet goes slow and sometimes my internet crashes, could it be from traffic? or from my neighbour's using my internet? (it's locked so idk)
me and my isp have history of crappy modem's too.
by the way, thanks for the help
To help the situation, try running a pingtest/speedtest and paste the result here. -
yea jon im not going to bicker with you this most likely a problem within the routing of their servers to our connection. It's a ***ing joke to say the least.
I don't see how we are bickering, but if you give me your IP, or atleast the first 3 digits then I'll send a report to your network administrator as a business concern. -
To help the situation, try running a pingtest/speedtest and paste the result here.
hamilton is a neighbour city
I'm on a 16 plan so 13 would make sense (did call my isp for this one).
upload speed is really slow.
and ping that close? disgusting
and I did this test through a cable not wireless -
go with shaw to be honest they are the most reliable even though the service kinda blows.
From my point of view, the routing issue starts with one of the shaw cable routes from my server > edmonton
Can you run a traceroute to;
ns1-auth.q9.com
Go to start > run (or hit WINKEY + R) and type in CMD, on the cmd line type in;
tracert ns1-auth.q9.com
hit enter, right click > select all (hit enter to copy)
then paste here.
Categories
- All Categories
- Z8Games
- 1 Z8 Forum Discussion & Suggestions
- 15 Z8Games Announcements
- Rules & Conduct
- 2.6K CrossFire
- 745 CrossFire Announcements
- 742 Previous Announcements
- 2 Previous Patch Notes
- 333 Community
- 12 Modes
- 400 Suggestions
- 16 Clan Discussion and Recruitment
- 89 CF Competitive Forum
- 1 CFCL
- 17 Looking for a Team?
- 536 CrossFire Support
- 9 Suggestion
- 16 CrossFire Guides
- 38 CrossFire Off Topic