Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
Ive been with afrihost now for a week or so
I had heard good things from friends in the past ( switched from telkom because of their excessive throttling)
First 2 days were great and now im thinking of cancelling , the speeds are horrendous.

http://speedtest.ookla.com/result/2611401404.png
http://speedtest.ookla.com/result/2611402266.png
http://speedtest.ookla.com/result/2611403679.png

PS im on a 4mb uncapped ?

doubt ill survive another week with afrihost if this isn't sorted out

#edit , tried the app aswell

Ping to 197.242.144.102
# Latency
0 338 ms
1 356 ms
2 349 ms
3 Request timeout
4 316 ms
Ping to 8.8.8.8
# Latency
0 Request timeout
1 421 ms
2 421 ms
3 407 ms
4 Request timeout

Hop IP Address Latency
1 10.0.0.2 5 ms
Trace to 8.8.8.8
Hop IP Address Latency
1 10.0.0.2 4 ms
1 Request timed out *
2 105.236.5.1 200 ms
3 Request timed out *


Please would you run my second app (in the link below) :)

Something doesn't seem right about those tracerts?

Z
 
Please would you run my second app (in the link below) :)

Something doesn't seem right about those tracerts?

Z


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 147ms
Your maximum ping was 229ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.5.129 with 32 bytes of data:
Reply from 105.236.5.129: bytes=32 time=211ms TTL=254
Reply from 105.236.5.129: bytes=32 time=204ms TTL=254
Reply from 105.236.5.129: bytes=32 time=229ms TTL=254
Reply from 105.236.5.129: bytes=32 time=166ms TTL=254
Reply from 105.236.5.129: bytes=32 time=179ms TTL=254
Reply from 105.236.5.129: bytes=32 time=189ms TTL=254
Reply from 105.236.5.129: bytes=32 time=146ms TTL=254
Reply from 105.236.5.129: bytes=32 time=170ms TTL=254
Reply from 105.236.5.129: bytes=32 time=186ms TTL=254
Reply from 105.236.5.129: bytes=32 time=199ms TTL=254
Reply from 105.236.5.129: bytes=32 time=218ms TTL=254
Reply from 105.236.5.129: bytes=32 time=161ms TTL=254
Reply from 105.236.5.129: bytes=32 time=181ms TTL=254
Reply from 105.236.5.129: bytes=32 time=140ms TTL=254
Reply from 105.236.5.129: bytes=32 time=184ms TTL=254
Reply from 105.236.5.129: bytes=32 time=181ms TTL=254
Reply from 105.236.5.129: bytes=32 time=135ms TTL=254
Reply from 105.236.5.129: bytes=32 time=160ms TTL=254
Reply from 105.236.5.129: bytes=32 time=132ms TTL=254
Reply from 105.236.5.129: bytes=32 time=26ms TTL=254
Reply from 105.236.5.129: bytes=32 time=12ms TTL=254
Reply from 105.236.5.129: bytes=32 time=17ms TTL=254
Reply from 105.236.5.129: bytes=32 time=38ms TTL=254
Reply from 105.236.5.129: bytes=32 time=74ms TTL=254
Reply from 105.236.5.129: bytes=32 time=96ms TTL=254
Reply from 105.236.5.129: bytes=32 time=120ms TTL=254
Reply from 105.236.5.129: bytes=32 time=148ms TTL=254
Reply from 105.236.5.129: bytes=32 time=157ms TTL=254
Reply from 105.236.5.129: bytes=32 time=170ms TTL=254
Reply from 105.236.5.129: bytes=32 time=201ms TTL=254

Ping statistics for 105.236.5.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 229ms, Average = 147ms
 
2014/05/29 20:12:50.42


i have no clue what it could be ? Line ? maybe router ? i do have a second router to try
 

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 147ms
Your maximum ping was 229ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.5.129 with 32 bytes of data:
Reply from 105.236.5.129: bytes=32 time=211ms TTL=254
Reply from 105.236.5.129: bytes=32 time=204ms TTL=254
Reply from 105.236.5.129: bytes=32 time=229ms TTL=254
Reply from 105.236.5.129: bytes=32 time=166ms TTL=254
Reply from 105.236.5.129: bytes=32 time=179ms TTL=254
Reply from 105.236.5.129: bytes=32 time=189ms TTL=254
Reply from 105.236.5.129: bytes=32 time=146ms TTL=254
Reply from 105.236.5.129: bytes=32 time=170ms TTL=254
Reply from 105.236.5.129: bytes=32 time=186ms TTL=254
Reply from 105.236.5.129: bytes=32 time=199ms TTL=254
Reply from 105.236.5.129: bytes=32 time=218ms TTL=254
Reply from 105.236.5.129: bytes=32 time=161ms TTL=254
Reply from 105.236.5.129: bytes=32 time=181ms TTL=254
Reply from 105.236.5.129: bytes=32 time=140ms TTL=254
Reply from 105.236.5.129: bytes=32 time=184ms TTL=254
Reply from 105.236.5.129: bytes=32 time=181ms TTL=254
Reply from 105.236.5.129: bytes=32 time=135ms TTL=254
Reply from 105.236.5.129: bytes=32 time=160ms TTL=254
Reply from 105.236.5.129: bytes=32 time=132ms TTL=254
Reply from 105.236.5.129: bytes=32 time=26ms TTL=254
Reply from 105.236.5.129: bytes=32 time=12ms TTL=254
Reply from 105.236.5.129: bytes=32 time=17ms TTL=254
Reply from 105.236.5.129: bytes=32 time=38ms TTL=254
Reply from 105.236.5.129: bytes=32 time=74ms TTL=254
Reply from 105.236.5.129: bytes=32 time=96ms TTL=254
Reply from 105.236.5.129: bytes=32 time=120ms TTL=254
Reply from 105.236.5.129: bytes=32 time=148ms TTL=254
Reply from 105.236.5.129: bytes=32 time=157ms TTL=254
Reply from 105.236.5.129: bytes=32 time=170ms TTL=254
Reply from 105.236.5.129: bytes=32 time=201ms TTL=254

Ping statistics for 105.236.5.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 229ms, Average = 147ms
 
2014/05/29 20:12:50.42


i have no clue what it could be ? Line ? maybe router ? i do have a second router to try

Wow, that doesn't look great at all!

Sorry to do this :D But please would you run the first tool and post the results :P

Z
 
here ya go

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 2 ms 2 ms 4 ms Billion.400G [10.0.0.2]
2 230 ms 243 ms 241 ms 105-236-5-129-esr-lo.mtnbusiness.co.za [105.236.5.129]
3 256 ms 252 ms 239 ms 41.181.201.94
4 173 ms 179 ms 188 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 180 ms 185 ms 201 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 167 ms 133 ms 122 ms 196.44.31.106
7 88 ms 140 ms 107 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 110 ms 110 ms 105 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 119 ms 117 ms 112 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 27 ms 26 ms 42 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 31 ms 27 ms 49 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 20 ms 20 ms 19 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 72 ms 79 ms 70 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 50 ms 62 ms 40 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 32 ms 31 ms 31 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 2 ms 2 ms 3 ms Billion.400G [10.0.0.2]
2 44 ms 11 ms 9 ms 105-236-5-129-esr-lo.mtnbusiness.co.za [105.236.5.129]
3 12 ms 13 ms 13 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 29 ms 30 ms 28 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 15 ms 16 ms 18 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 28 ms 24 ms 45 ms 196.44.31.106
7 205 ms 209 ms 230 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 261 ms 246 ms 256 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 293 ms 305 ms 309 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 329 ms 362 ms 292 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
11 301 ms 307 ms 314 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
12 314 ms 338 ms 359 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 3:31 seconds. (96.77 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 1:07 seconds. (237.97 KB/s)




Test End Timestamp
2014/05/29 20:22:59.35
 
here ya go

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 2 ms 2 ms 4 ms Billion.400G [10.0.0.2]
2 230 ms 243 ms 241 ms 105-236-5-129-esr-lo.mtnbusiness.co.za [105.236.5.129]
3 256 ms 252 ms 239 ms 41.181.201.94
4 173 ms 179 ms 188 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 180 ms 185 ms 201 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 167 ms 133 ms 122 ms 196.44.31.106
7 88 ms 140 ms 107 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 110 ms 110 ms 105 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 119 ms 117 ms 112 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 27 ms 26 ms 42 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 31 ms 27 ms 49 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 20 ms 20 ms 19 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 72 ms 79 ms 70 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 50 ms 62 ms 40 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 32 ms 31 ms 31 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 2 ms 2 ms 3 ms Billion.400G [10.0.0.2]
2 44 ms 11 ms 9 ms 105-236-5-129-esr-lo.mtnbusiness.co.za [105.236.5.129]
3 12 ms 13 ms 13 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 29 ms 30 ms 28 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 15 ms 16 ms 18 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 28 ms 24 ms 45 ms 196.44.31.106
7 205 ms 209 ms 230 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 261 ms 246 ms 256 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 293 ms 305 ms 309 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 329 ms 362 ms 292 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
11 301 ms 307 ms 314 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
12 314 ms 338 ms 359 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 3:31 seconds. (96.77 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 1:07 seconds. (237.97 KB/s)




Test End Timestamp
2014/05/29 20:22:59.35

Very very weird!

Your second hop should ALWAYS be under 25ms :P But your's seem to go up to 250ms, which would affect gaming/streaming/downloads and performance :(

While this usually shows a line problem, there may be other factors in play. Could you possibly try with another accounts trial (WebAfrica?), and run the test again :)

Also - it looks as if you are on WiFi. It shouldn't change much, but if you could connect via ethernet - that would help :)

Z
 
connecting via Ethernet may prove to be an issue unfortunately lol
i shall try a different router too probably tomorrow

thanks for your help thus far , this is very frustrating because it was fine days ago ;/
 
connecting via Ethernet may prove to be an issue unfortunately lol
i shall try a different router too probably tomorrow

thanks for your help thus far , this is very frustrating because it was fine days ago ;/

I can imagine! It's just that sometimes line issues can popup at any time. However, it may not even be a line issue at all... so that's why these types of tests are so important :P

Always ready to help!

Z
 
Evening has come, and speeds are in the crapper AGAIN.
Only 3.5MB speed on 10MB line.... and unstable at that.
What is going on???? Is this now the norm for Uncapped????
AH accounts are the only ones that suffer like this every evening.... all other ISP accounts are flying.

I sent a pm late last night to ALL 3 AH reps, and have not had one response :wtf:
 
Still no luck in steaming twitch.tv even on low use to be able to easily do medium.
 
pretty funny , its running perfect all of a sudden . Really think it may be the router
 
pretty funny , its running perfect all of a sudden . Really think it may be the router

If its intermittent like this - it sounds like it could be exchange congestion (which would show during busy times - evening - and disappear during the day and night - now)

Maybe PM AfriGuy/AfriMan :)

Z
 
Please let me know. I don't see any increases in general latency on my monitoring, but it could be specific to the LOL server. The more tests you can run, the better :(


I ran a trace root to the server I was connected to:

C:\Users\Dan>tracert 162.249.72.123

Tracing route to 162.249.72.123 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 10.0.0.2
2 8 ms 7 ms 7 ms 105-236-1-193-esr-lo.mtnbusiness.co.za [105.236.1.193]
3 38 ms 11 ms 9 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 9 ms 9 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 10 ms 10 ms 10 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.180.4]
6 206 ms 204 ms 267 ms 41.181.180.10
7 205 ms 206 ms 235 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 205 ms 207 ms 205 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 206 ms 205 ms 208 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
10 198 ms 191 ms 192 ms 195.50.122.181
11 220 ms 218 ms 220 ms vl-3605-ve-229.csw2.London1.Level3.net [4.69.166.18]
12 203 ms 202 ms 202 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
13 203 ms 203 ms 203 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
14 202 ms 203 ms 202 ms ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]
15 205 ms 202 ms * ae-4-90.edge3.Frankfurt1.Level3.net [4.69.154.199]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Any other things I should check?
 
Last edited:
here ya go

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 2 ms 2 ms 4 ms Billion.400G [10.0.0.2]
2 230 ms 243 ms 241 ms 105-236-5-129-esr-lo.mtnbusiness.co.za [105.236.5.129]
3 256 ms 252 ms 239 ms 41.181.201.94
4 173 ms 179 ms 188 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 180 ms 185 ms 201 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 167 ms 133 ms 122 ms 196.44.31.106
7 88 ms 140 ms 107 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 110 ms 110 ms 105 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 119 ms 117 ms 112 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 27 ms 26 ms 42 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 31 ms 27 ms 49 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 20 ms 20 ms 19 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 72 ms 79 ms 70 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 50 ms 62 ms 40 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 32 ms 31 ms 31 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 2 ms 2 ms 3 ms Billion.400G [10.0.0.2]
2 44 ms 11 ms 9 ms 105-236-5-129-esr-lo.mtnbusiness.co.za [105.236.5.129]
3 12 ms 13 ms 13 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 29 ms 30 ms 28 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 15 ms 16 ms 18 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 28 ms 24 ms 45 ms 196.44.31.106
7 205 ms 209 ms 230 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 261 ms 246 ms 256 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 293 ms 305 ms 309 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 329 ms 362 ms 292 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
11 301 ms 307 ms 314 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
12 314 ms 338 ms 359 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 3:31 seconds. (96.77 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 1:07 seconds. (237.97 KB/s)




Test End Timestamp
2014/05/29 20:22:59.35

Hello exchange congestion my old friend...
 
Ive been with afrihost now for a week or so
I had heard good things from friends in the past ( switched from telkom because of their excessive throttling)
First 2 days were great and now im thinking of cancelling , the speeds are horrendous.

http://speedtest.ookla.com/result/2611401404.png
http://speedtest.ookla.com/result/2611402266.png
http://speedtest.ookla.com/result/2611403679.png

PS im on a 4mb uncapped ?

doubt ill survive another week with afrihost if this isn't sorted out

#edit , tried the app aswell

Ping to 197.242.144.102
# Latency
0 338 ms
1 356 ms
2 349 ms
3 Request timeout
4 316 ms
Ping to 8.8.8.8
# Latency
0 Request timeout
1 421 ms
2 421 ms
3 407 ms
4 Request timeout

Hop IP Address Latency
1 10.0.0.2 5 ms
Trace to 8.8.8.8
Hop IP Address Latency
1 10.0.0.2 4 ms
1 Request timed out *
2 105.236.5.1 200 ms
3 Request timed out *

Going by this and the results posted later, I would say this is a congestion issue, or a line fault. However, Telkom are busy rolling out upgrades on exchanges, they could have been busy working on the exchange.

My home connection is currently out of order - I'm hoping this is because VDSL is on it's way to my face!! :)
 
Still no luck in steaming twitch.tv even on low use to be able to easily do medium.

I saw a few posts saying Twitch was working for some people, so it's pretty intermittent. I think until we get the full upgrade it will be difficult to say it's one or the other, but I know that even with available we've had a problem or two with Twitch.
 
pretty funny , its running perfect all of a sudden . Really think it may be the router

Definitely would lead me to believe it's congestion. A line fault wouldn't normally bounce back to life, unless it was a fault being addressed on the exchange already.
 
I ran a trace root to the server I was connected to:

C:\Users\Dan>tracert 162.249.72.123

Tracing route to 162.249.72.123 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 10.0.0.2
2 8 ms 7 ms 7 ms 105-236-1-193-esr-lo.mtnbusiness.co.za [105.236.1.193]
3 38 ms 11 ms 9 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 9 ms 9 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 10 ms 10 ms 10 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.180.4]
6 206 ms 204 ms 267 ms 41.181.180.10
7 205 ms 206 ms 235 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 205 ms 207 ms 205 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 206 ms 205 ms 208 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
10 198 ms 191 ms 192 ms 195.50.122.181
11 220 ms 218 ms 220 ms vl-3605-ve-229.csw2.London1.Level3.net [4.69.166.18]
12 203 ms 202 ms 202 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
13 203 ms 203 ms 203 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
14 202 ms 203 ms 202 ms ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]
15 205 ms 202 ms * ae-4-90.edge3.Frankfurt1.Level3.net [4.69.154.199]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Any other things I should check?

Everything seems pretty normal up to the server, so I would guess any additional latency is in game or on the server :(
 
Is it just me or are others also having a veeeery slow internet day, youtube wants to bufffer on 240p on a 4mb.
 
Is it just me or are others also having a veeeery slow internet day, youtube wants to bufffer on 240p on a 4mb.

Its not just you
i can barely even run a 140p video lol and im also supposed to be on 4mb
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X