Slow CellC Internet

sajunky · Jul 13, 2016

It came back to normal after midnight (when restarted router for midnight downloads), also now Cell C is flying again...

?Anonymous?

Fareed86 · Jul 13, 2016

Mine has been slow for the last 2 days... Tried moving the router around but still the same. Don't know what to do

Contacted Cell C and they just told me to manually register the router on the network, which I did, but nothing changed. Before Monday I was getting proper 3G speeds and now it's like I'm on a 1mbps ADSL line...

RichardG · Jul 14, 2016

Park@82 said:
was very unstable earlier.

Still a few hiccups with routing by the looks of things, unsure if this has to do with the undersea cable. Websites taken over 4 minutes to load with frequent F5

sajunky · Jul 14, 2016

Fareed86 said:
Mine has been slow for the last 2 days... Tried moving the router around but still the same. Don't know what to do

Contacted Cell C and they just told me to manually register the router on the network, which I did, but nothing changed. Before Monday I was getting proper 3G speeds and now it's like I'm on a 1mbps ADSL line...

If it is B315s router, I found that NVRAM is corrupting at times. By example I haven't been able to access secondary SIP server settings, selecting this option was doing nothing. Hardware reset fixed a problem.

Regarding Cell C, was having some slow down - twice a day, generally was acceptable.

Park@82 · Jul 14, 2016

Dear cell c please fix your *** already!

Park@82 · Jul 14, 2016

Pinging google.co.za:

Reply from 216.58.223.3: bytes=32 time=63ms TTL=55
Reply from 216.58.223.3: bytes=32 time=57ms TTL=55
Request timed out.
Reply from 216.58.223.3: bytes=32 time=103ms TTL=55
Request timed out.
Reply from 216.58.223.3: bytes=32 time=118ms TTL=55
Reply from 216.58.223.3: bytes=32 time=91ms TTL=55
Request timed out.
Reply from 216.58.223.3: bytes=32 time=75ms TTL=55
Reply from 216.58.223.3: bytes=32 time=94ms TTL=55
Reply from 216.58.223.3: bytes=32 time=78ms TTL=55
Reply from 216.58.223.3: bytes=32 time=70ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.223.3: bytes=32 time=110ms TTL=55
Reply from 216.58.223.3: bytes=32 time=65ms TTL=55
Reply from 216.58.223.3: bytes=32 time=78ms TTL=55
Reply from 216.58.223.3: bytes=32 time=61ms TTL=55
Request timed out.
Request timed out.
Reply from 216.58.223.3: bytes=32 time=128ms TTL=55
Request timed out.
Request timed out.
Reply from 216.58.223.3: bytes=32 time=119ms TTL=55
Reply from 216.58.223.3: bytes=32 time=103ms TTL=55
Request timed out.
Reply from 216.58.223.3: bytes=32 time=132ms TTL=55
Reply from 216.58.223.3: bytes=32 time=102ms TTL=55

Park@82 · Jul 14, 2016

Tracing route to www.mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 * 47 ms 23 ms 41.50.7.230
4 * * 28 ms 10.220.232.193
5 30 ms 32 ms 39 ms 41.50.16.1
6 25 ms * * 41.50.0.2
7 26 ms 25 ms 25 ms 41.50.1.1
8 27 ms 25 ms 28 ms eoh-ns.jb1.napafrica.net [196.46.25.157]
9 * 26 ms * 41-66-181-63-3f.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.63]
10 27 ms 22 ms 29 ms 104.20.72.110

Trace complete.

...

Park@82 · Jul 14, 2016

pinging mybroadband.co.za

Reply from 104.20.72.110: bytes=32 time=26ms TTL=56
Reply from 104.20.72.110: bytes=32 time=23ms TTL=56
Reply from 104.20.72.110: bytes=32 time=24ms TTL=56
Reply from 104.20.72.110: bytes=32 time=21ms TTL=56
Reply from 104.20.72.110: bytes=32 time=17ms TTL=56
Reply from 104.20.72.110: bytes=32 time=20ms TTL=56
Reply from 104.20.72.110: bytes=32 time=30ms TTL=56
Reply from 104.20.72.110: bytes=32 time=21ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 104.20.72.110: bytes=32 time=203ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 104.20.72.110: bytes=32 time=186ms TTL=56
Request timed out.
Request timed out.

sajunky · Jul 14, 2016

Not sure it is all the time like that, but it is as it should.

Code:

C:\>ping google.co.za

Pinging google.co.za [216.58.223.3] with 32 bytes of data:

Reply from 216.58.223.3: bytes=32 time=22ms TTL=55
Reply from 216.58.223.3: bytes=32 time=22ms TTL=55
Reply from 216.58.223.3: bytes=32 time=15ms TTL=55
Reply from 216.58.223.3: bytes=32 time=22ms TTL=55

Ping statistics for 216.58.223.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 22ms, Average = 20ms

C:\>ping mybroadband.co.za

Pinging mybroadband.co.za [104.20.72.110] with 32 bytes of data:

Reply from 104.20.72.110: bytes=32 time=26ms TTL=56
Reply from 104.20.72.110: bytes=32 time=15ms TTL=56
Reply from 104.20.72.110: bytes=32 time=19ms TTL=56
Reply from 104.20.72.110: bytes=32 time=14ms TTL=56

Ping statistics for 104.20.72.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 26ms, Average = 18ms

Cell_C · Jul 15, 2016

Fareed86 said:
Mine has been slow for the last 2 days... Tried moving the router around but still the same. Don't know what to do

Contacted Cell C and they just told me to manually register the router on the network, which I did, but nothing changed. Before Monday I was getting proper 3G speeds and now it's like I'm on a 1mbps ADSL line...

Hi Fareed86

Thank you for posting to us.

Please PM your Cell C number + address, we will be in touch to assist.

^BM

Park@82 · Jul 16, 2016

same ****, different day

Reply from 212.58.244.70: bytes=32 time=287ms TTL=47
Reply from 212.58.244.70: bytes=32 time=305ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=212ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=253ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=274ms TTL=47
Reply from 212.58.244.70: bytes=32 time=232ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=232ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=262ms TTL=47
Reply from 212.58.244.70: bytes=32 time=318ms TTL=47
Reply from 212.58.244.70: bytes=32 time=257ms TTL=47
Reply from 212.58.244.70: bytes=32 time=233ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=275ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=281ms TTL=47
Reply from 212.58.244.70: bytes=32 time=257ms TTL=47
Reply from 212.58.244.70: bytes=32 time=250ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=262ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=284ms TTL=47
Reply from 212.58.244.70: bytes=32 time=302ms TTL=47
Reply from 212.58.244.70: bytes=32 time=232ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=250ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=211ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=219ms TTL=47
Reply from 212.58.244.70: bytes=32 time=268ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=209ms TTL=47
Reply from 212.58.244.70: bytes=32 time=231ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=249ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=288ms TTL=47
Reply from 212.58.244.70: bytes=32 time=264ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=251ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=225ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=267ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=250ms TTL=47
Reply from 212.58.244.70: bytes=32 time=259ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=256ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=244ms TTL=47
Reply from 212.58.244.70: bytes=32 time=227ms TTL=47
Reply from 212.58.244.70: bytes=32 time=319ms TTL=47
Reply from 212.58.244.70: bytes=32 time=258ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=238ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=229ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=224ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=225ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=254ms TTL=47
Reply from 212.58.244.70: bytes=32 time=235ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=274ms TTL=47
Reply from 212.58.244.70: bytes=32 time=242ms TTL=47
Reply from 212.58.244.70: bytes=32 time=228ms TTL=47
Reply from 212.58.244.70: bytes=32 time=297ms TTL=47
Reply from 212.58.244.70: bytes=32 time=215ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=301ms TTL=47
Reply from 212.58.244.70: bytes=32 time=233ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=234ms TTL=47
Reply from 212.58.244.70: bytes=32 time=221ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=303ms TTL=47
Reply from 212.58.244.70: bytes=32 time=224ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=311ms TTL=47
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=293ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=324ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=339ms TTL=47
Reply from 212.58.244.70: bytes=32 time=292ms TTL=47
Request timed out.
Reply from 212.58.244.70: bytes=32 time=290ms TTL=47
Reply from 212.58.244.70: bytes=32 time=269ms TTL=47
Reply from 212.58.244.70: bytes=32 time=284ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.70: bytes=32 time=289ms TTL=47
Request timed out.

Park@82 · Jul 16, 2016

/goes to look for my telkom sim *sigh

Park@82 · Jul 16, 2016

extremely unstable and very frustrating. pinging mybroadband:

Reply from 104.20.71.110: bytes=32 time=478ms TTL=55
Request timed out.
Reply from 104.20.71.110: bytes=32 time=373ms TTL=55
Reply from 104.20.71.110: bytes=32 time=160ms TTL=55
Reply from 104.20.71.110: bytes=32 time=77ms TTL=55
Reply from 104.20.71.110: bytes=32 time=83ms TTL=55
Reply from 104.20.71.110: bytes=32 time=85ms TTL=55
Reply from 104.20.71.110: bytes=32 time=75ms TTL=55
Reply from 104.20.71.110: bytes=32 time=88ms TTL=55
Reply from 104.20.71.110: bytes=32 time=91ms TTL=55
Reply from 104.20.71.110: bytes=32 time=531ms TTL=55
Reply from 104.20.71.110: bytes=32 time=1597ms TTL=55
Request timed out.
Reply from 104.20.71.110: bytes=32 time=426ms TTL=55
Reply from 104.20.71.110: bytes=32 time=472ms TTL=55
Reply from 104.20.71.110: bytes=32 time=327ms TTL=55
Reply from 104.20.71.110: bytes=32 time=133ms TTL=55
Reply from 104.20.71.110: bytes=32 time=321ms TTL=55
Reply from 104.20.71.110: bytes=32 time=468ms TTL=55
Reply from 104.20.71.110: bytes=32 time=303ms TTL=55
Reply from 104.20.71.110: bytes=32 time=377ms TTL=55
Reply from 104.20.71.110: bytes=32 time=462ms TTL=55
Reply from 104.20.71.110: bytes=32 time=202ms TTL=55
Reply from 104.20.71.110: bytes=32 time=212ms TTL=55
Reply from 104.20.71.110: bytes=32 time=190ms TTL=55
Reply from 104.20.71.110: bytes=32 time=372ms TTL=55
Reply from 104.20.71.110: bytes=32 time=547ms TTL=55
Reply from 104.20.71.110: bytes=32 time=300ms TTL=55
Request timed out.
Reply from 104.20.71.110: bytes=32 time=236ms TTL=55
Reply from 104.20.71.110: bytes=32 time=406ms TTL=55
Reply from 104.20.71.110: bytes=32 time=181ms TTL=55
Reply from 104.20.71.110: bytes=32 time=424ms TTL=55
Reply from 104.20.71.110: bytes=32 time=299ms TTL=55
Reply from 104.20.71.110: bytes=32 time=422ms TTL=55
Reply from 104.20.71.110: bytes=32 time=215ms TTL=55
Reply from 104.20.71.110: bytes=32 time=350ms TTL=55
Reply from 104.20.71.110: bytes=32 time=468ms TTL=55
Reply from 104.20.71.110: bytes=32 time=237ms TTL=55
Reply from 104.20.71.110: bytes=32 time=162ms TTL=55
Reply from 104.20.71.110: bytes=32 time=56ms TTL=55
Reply from 104.20.71.110: bytes=32 time=283ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 104.20.71.110: bytes=32 time=209ms TTL=56
Reply from 104.20.71.110: bytes=32 time=128ms TTL=56
Reply from 104.20.71.110: bytes=32 time=228ms TTL=56
Request timed out.
Reply from 104.20.71.110: bytes=32 time=99ms TTL=56
Reply from 104.20.71.110: bytes=32 time=212ms TTL=56
Request timed out.
Request timed out.
Reply from 104.20.71.110: bytes=32 time=161ms TTL=56
Request timed out.
Reply from 104.20.71.110: bytes=32 time=70ms TTL=56
Request timed out.
Reply from 104.20.71.110: bytes=32 time=205ms TTL=56
Reply from 104.20.71.110: bytes=32 time=163ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 104.20.71.110: bytes=32 time=186ms TTL=56
Reply from 104.20.71.110: bytes=32 time=575ms TTL=56
Reply from 104.20.71.110: bytes=32 time=485ms TTL=56
Reply from 104.20.71.110: bytes=32 time=396ms TTL=56
Reply from 104.20.71.110: bytes=32 time=123ms TTL=56
Request timed out.
Request timed out.
Reply from 104.20.71.110: bytes=32 time=95ms TTL=56
Reply from 104.20.71.110: bytes=32 time=154ms TTL=56
Reply from 104.20.71.110: bytes=32 time=168ms TTL=56
Request timed out.
Reply from 104.20.71.110: bytes=32 time=150ms TTL=56
Request timed out.
Reply from 104.20.71.110: bytes=32 time=121ms TTL=56
Reply from 104.20.71.110: bytes=32 time=121ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 104.20.71.110: bytes=32 time=219ms TTL=56
Reply from 104.20.71.110: bytes=32 time=168ms TTL=56
Reply from 104.20.71.110: bytes=32 time=109ms TTL=56
Reply from 104.20.71.110: bytes=32 time=126ms TTL=56
Request timed out.
Reply from 104.20.71.110: bytes=32 time=191ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 104.20.71.110: bytes=32 time=197ms TTL=56
Reply from 104.20.71.110: bytes=32 time=91ms TTL=56
Reply from 104.20.71.110: bytes=32 time=120ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 104.20.71.110: bytes=32 time=107ms TTL=56
Reply from 104.20.71.110: bytes=32 time=97ms TTL=56

Kenryuu · Jul 16, 2016

when will cellc (or neotel hardware) finishing repairing their network?
this is getting very frustrating its getting harder just to browse, let alone trying to play games. gah!

cr@zydude · Jul 18, 2016

Some days I wish that I had taken a Telkom Mobile contract:

Internet was completely down for me earlier today, and now I have this.

Cell_C · Jul 19, 2016

cr@zydude said:
Some days I wish that I had taken a Telkom Mobile contract:

View attachment 376192

Internet was completely down for me earlier today, and now I have this.

Hi there,

Are you situated in Cape Town?

^SM

dyl13 · Jul 19, 2016

I have the same issue!! I'm sitting with full 4G (LTE), yet I can't seem to get a download speed faster than 100kb.

I'm on the 5GB-15GB data bundle, and the Cell c speeds are shocking

sajunky · Jul 19, 2016

There was slow down yestearday in Gauteng, Midrand area. Even after midnight it was losing packets. Today is fine.

chubster · Jul 19, 2016

I'm using Cell C's ZTE MiFi device (R99 for 5GB + 15GB midnight), and I'm quite happy with it, I sometimes have to restart the device once a day.

Did this ping to show in Cape town area on LTE

Code:

# ping www.google.co.za -c 20 -I usb0
PING www.google.co.za (216.58.223.35) from 192.168.0.153 usb0: 56(84) bytes of data.
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=1 ttl=55 time=49.3 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=2 ttl=55 time=41.2 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=3 ttl=55 time=41.2 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=4 ttl=55 time=41.3 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=5 ttl=55 time=44.5 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=6 ttl=55 time=40.9 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=7 ttl=55 time=41.1 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=8 ttl=55 time=42.6 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=9 ttl=55 time=41.0 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=10 ttl=55 time=41.6 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=11 ttl=55 time=40.8 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=12 ttl=55 time=41.4 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=13 ttl=55 time=40.7 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=14 ttl=55 time=41.2 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=15 ttl=55 time=40.7 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=16 ttl=55 time=41.5 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=17 ttl=55 time=40.4 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=18 ttl=55 time=40.7 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=19 ttl=55 time=42.2 ms
64 bytes from jnb01s08-in-f35.1e100.net (216.58.223.35): icmp_seq=20 ttl=55 time=40.8 ms

--- www.google.co.za ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19029ms
rtt min/avg/max/mdev = 40.474/41.812/49.358/1.961 ms

I recall also buying a 100GB from Cell C a while ago using Cell C's Nokia 3G modem I bought at the same time. It worked fine for a short while and went south from there and recall the same hideous ping times. I'm tempted to try the 100GB on my MiFi device. The APN seems to have the same name called "internet". So with LTE in Cape Town it seems good.

screenshot of web interface:

I'm connecting to my MiFi device via the usb cable that acts like an Ethernet connection.

Cell_C · Jul 19, 2016

dyl13 said:
I have the same issue!! I'm sitting with full 4G (LTE), yet I can't seem to get a download speed faster than 100kb.

I'm on the 5GB-15GB data bundle, and the Cell c speeds are shocking

Hi dyl13

Kindly PM us the location and your contact details.

^SM

Join the MyBroadband community

Get started

Slow CellC Internet

Honorary Master

Active Member

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Cell C Representative

Honorary Master

Honorary Master

Honorary Master

Member

Honorary Master

Cell C Representative

New Member

Honorary Master

Senior Member

Cell C Representative