Vox Telecom Fatpipe

cvanwie · Aug 5, 2015

AfricanTech said:
Thanks.

I don't play BF3 but D3 (especially if you play DH) is also susceptible to erratic gameplay under such conditions.

That said:

a. I haven't played D3 for a while so I don't know if its currently an issue on my line
b. When I was playing a few months ago, it was fine
c. I had problems about a year back, but see b. above.

Good luck - maybe chris can check if there there is something special in the way BF3 traffic is routed.

Or gaming as a whole.

(already did a few minutes ago)

AntiGanda · Aug 5, 2015

Electric said:
Nope, personal use at home.
Not a business at all.
Did you notice I was not the only one that said something?
But please, continue to berate me for ****s n giggles.

If 99% of the feedback is positive then is it wrong of me to mention it?

Yes, because you can't possibly know this or speak for anyone else.

Electric · Aug 5, 2015

AntiGanda said:
Yes, because you can't possibly know this or speak for anyone else.

It was an innocent statement that you have taken to a new level.
Whatever, I'm out.

BigBear · Aug 5, 2015

I can't complain Ping is Rock solid at ~300 ms and Win 10 Pro iso Download Flat Lining at 3.5-3.8 Mbps

VOX FP 100gb for R164 pm Money well Spent !

techead · Aug 5, 2015

BigBear said:
I can't complain Ping is Rock solid at ~300 ms and Win 10 Pro iso Download Flat Lining at 3.5-3.8 Mbps

VOX FP 100gb for R164 pm Money well Spent !

Rock Solid at ~300 ms while you are downloading?

How is that helpful in ANY way whatsoever?

BigBear · Aug 5, 2015

techead said:
Rock Solid at ~300 ms while you are downloading?

How is that helpful in ANY way whatsoever?

lol wrong wording was meant for the DL but anyway..

PING is quite stable even while downloading and other users browsing etc.

Code:

Reply from 87.248.221.221: bytes=32 time=217ms TTL=50
Reply from 87.248.221.221: bytes=32 time=289ms TTL=50
Reply from 87.248.221.221: bytes=32 time=213ms TTL=50
Reply from 87.248.221.221: bytes=32 time=258ms TTL=50
Reply from 87.248.221.221: bytes=32 time=214ms TTL=50
Reply from 87.248.221.221: bytes=32 time=260ms TTL=50
Reply from 87.248.221.221: bytes=32 time=228ms TTL=50
Reply from 87.248.221.221: bytes=32 time=255ms TTL=50
Reply from 87.248.221.221: bytes=32 time=253ms TTL=50
Reply from 87.248.221.221: bytes=32 time=201ms TTL=50
Reply from 87.248.221.221: bytes=32 time=265ms TTL=50
Reply from 87.248.221.221: bytes=32 time=224ms TTL=50
Reply from 87.248.221.221: bytes=32 time=206ms TTL=50
Reply from 87.248.221.221: bytes=32 time=249ms TTL=50
Reply from 87.248.221.221: bytes=32 time=220ms TTL=50
Reply from 87.248.221.221: bytes=32 time=293ms TTL=50
Reply from 87.248.221.221: bytes=32 time=291ms TTL=50
Reply from 87.248.221.221: bytes=32 time=246ms TTL=50
Reply from 87.248.221.221: bytes=32 time=246ms TTL=50
Reply from 87.248.221.221: bytes=32 time=287ms TTL=50
Reply from 87.248.221.221: bytes=32 time=299ms TTL=50
Reply from 87.248.221.221: bytes=32 time=241ms TTL=50
Reply from 87.248.221.221: bytes=32 time=274ms TTL=50
Reply from 87.248.221.221: bytes=32 time=194ms TTL=50
Reply from 87.248.221.221: bytes=32 time=197ms TTL=50
Reply from 87.248.221.221: bytes=32 time=306ms TTL=50
Reply from 87.248.221.221: bytes=32 time=278ms TTL=50
Reply from 87.248.221.221: bytes=32 time=208ms TTL=50
Reply from 87.248.221.221: bytes=32 time=259ms TTL=50
Reply from 87.248.221.221: bytes=32 time=211ms TTL=50
Reply from 87.248.221.221: bytes=32 time=218ms TTL=50
Reply from 87.248.221.221: bytes=32 time=202ms TTL=50
Reply from 87.248.221.221: bytes=32 time=247ms TTL=50
Reply from 87.248.221.221: bytes=32 time=211ms TTL=50
Reply from 87.248.221.221: bytes=32 time=300ms TTL=50
Reply from 87.248.221.221: bytes=32 time=260ms TTL=50
Reply from 87.248.221.221: bytes=32 time=193ms TTL=50
Reply from 87.248.221.221: bytes=32 time=242ms TTL=50
Reply from 87.248.221.221: bytes=32 time=212ms TTL=50
Reply from 87.248.221.221: bytes=32 time=263ms TTL=50
Reply from 87.248.221.221: bytes=32 time=211ms TTL=50
Reply from 87.248.221.221: bytes=32 time=257ms TTL=50
Reply from 87.248.221.221: bytes=32 time=243ms TTL=50
Reply from 87.248.221.221: bytes=32 time=277ms TTL=50
Reply from 87.248.221.221: bytes=32 time=272ms TTL=50
Reply from 87.248.221.221: bytes=32 time=208ms TTL=50
Reply from 87.248.221.221: bytes=32 time=259ms TTL=50
Reply from 87.248.221.221: bytes=32 time=272ms TTL=50
Reply from 87.248.221.221: bytes=32 time=226ms TTL=50
Reply from 87.248.221.221: bytes=32 time=202ms TTL=50
Reply from 87.248.221.221: bytes=32 time=279ms TTL=50
Reply from 87.248.221.221: bytes=32 time=224ms TTL=50
Reply from 87.248.221.221: bytes=32 time=235ms TTL=50
Reply from 87.248.221.221: bytes=32 time=255ms TTL=50

Ping statistics for 87.248.221.221:
    Packets: Sent = 69191, Received = 69142, Lost = 49 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 190ms, Maximum = 3562ms, Average = 237ms

Tracing route to cds503.par.llnw.net [87.248.221.221]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    86 ms    14 ms    81 ms  dsl-197-245-14-1.voxdsl.co.za [197.245.14.1]
  3     *        *        *     Request timed out.
  4    53 ms   106 ms   117 ms  41.193.3.102
  5   100 ms    94 ms    92 ms  196.41.12.0
  6    55 ms   100 ms    20 ms  41.193.32.149
  7   248 ms   200 ms   210 ms  196.41.9.34
  8   218 ms   197 ms   212 ms  196.41.27.114
  9   218 ms   230 ms   211 ms  ldn-b3-link.telia.net [213.248.100.161]
 10   265 ms     *      229 ms  ldn-bb2-link.telia.net [62.115.140.246]
 11   211 ms   220 ms   215 ms  adm-bb4-link.telia.net [213.155.130.84]
 12   296 ms   210 ms   202 ms  adm-b7-link.telia.net [213.155.133.35]
 13   459 ms   348 ms   263 ms  limelight-ic-138923-adm-b7.c.telia.net [213.248.
103.30]
 14   290 ms   237 ms   277 ms  tge7-4.fr4.frf.llnw.net [69.28.171.53]
 15   272 ms   209 ms   207 ms  tge1-3.fr4.par.llnw.net [69.28.172.101]
 16   203 ms   206 ms   250 ms  cds503.par.llnw.net [87.248.221.221]

Trace complete.

techead · Aug 5, 2015

ok that is bloody weird....

during normal ping I've always been ~158ms

My connection just reset and now its ~168ms

dee4dog · Aug 5, 2015

Ok i'm impressed!!!!! Downloading torrent @400kB/s while streaming youtube 720p, no buffering in peak hours. 4meg line. Never ever , ever even seen this on AH!!

BigBear · Aug 5, 2015

techead said:
ok that is bloody weird....

during normal ping I've always been ~158ms

My connection just reset and now its ~168ms

Had a Forced Connection Reset or Interruption aka Load Shedding..

Code:

PING MS WIN 10 Download Servers:

Reply from 87.248.221.221: bytes=32 time=305ms TTL=50
Reply from 87.248.221.221: bytes=32 time=302ms TTL=50
Reply from 87.248.221.221: bytes=32 time=297ms TTL=50
Reply from 87.248.221.221: bytes=32 time=306ms TTL=50
Reply from 87.248.221.221: bytes=32 time=302ms TTL=50
Reply from 87.248.221.221: bytes=32 time=300ms TTL=50
Reply from 87.248.221.221: bytes=32 time=301ms TTL=50
Reply from 87.248.221.221: bytes=32 time=273ms TTL=50
Reply from 87.248.221.221: bytes=32 time=298ms TTL=50
Reply from 87.248.221.221: bytes=32 time=306ms TTL=50
Reply from 87.248.221.221: bytes=32 time=292ms TTL=50
Reply from 87.248.221.221: bytes=32 time=301ms TTL=50
Reply from 87.248.221.221: bytes=32 time=300ms TTL=50
Reply from 87.248.221.221: bytes=32 time=303ms TTL=50
Reply from 87.248.221.221: bytes=32 time=302ms TTL=50
Reply from 87.248.221.221: bytes=32 time=305ms TTL=50
Reply from 87.248.221.221: bytes=32 time=303ms TTL=50
Reply from 87.248.221.221: bytes=32 time=303ms TTL=50
Reply from 87.248.221.221: bytes=32 time=301ms TTL=50
Reply from 87.248.221.221: bytes=32 time=304ms TTL=50
Reply from 87.248.221.221: bytes=32 time=303ms TTL=50
Reply from 87.248.221.221: bytes=32 time=299ms TTL=50
Reply from 87.248.221.221: bytes=32 time=350ms TTL=50
Reply from 87.248.221.221: bytes=32 time=250ms TTL=50
Reply from 87.248.221.221: bytes=32 time=335ms TTL=50
Reply from 87.248.221.221: bytes=32 time=311ms TTL=50
Reply from 87.248.221.221: bytes=32 time=299ms TTL=50
Reply from 87.248.221.221: bytes=32 time=257ms TTL=50
Reply from 87.248.221.221: bytes=32 time=309ms TTL=50
Reply from 87.248.221.221: bytes=32 time=303ms TTL=50
Reply from 87.248.221.221: bytes=32 time=298ms TTL=50
Reply from 87.248.221.221: bytes=32 time=305ms TTL=50
Reply from 87.248.221.221: bytes=32 time=304ms TTL=50
Reply from 87.248.221.221: bytes=32 time=307ms TTL=50
Reply from 87.248.221.221: bytes=32 time=303ms TTL=50
Reply from 87.248.221.221: bytes=32 time=279ms TTL=50
Reply from 87.248.221.221: bytes=32 time=294ms TTL=50
Reply from 87.248.221.221: bytes=32 time=303ms TTL=50
Reply from 87.248.221.221: bytes=32 time=302ms TTL=50
Reply from 87.248.221.221: bytes=32 time=306ms TTL=50
Reply from 87.248.221.221: bytes=32 time=305ms TTL=50
Reply from 87.248.221.221: bytes=32 time=306ms TTL=50
Reply from 87.248.221.221: bytes=32 time=300ms TTL=50
Reply from 87.248.221.221: bytes=32 time=298ms TTL=50
Reply from 87.248.221.221: bytes=32 time=302ms TTL=50
Reply from 87.248.221.221: bytes=32 time=309ms TTL=50
Reply from 87.248.221.221: bytes=32 time=293ms TTL=50
Reply from 87.248.221.221: bytes=32 time=302ms TTL=50
Reply from 87.248.221.221: bytes=32 time=282ms TTL=50
Reply from 87.248.221.221: bytes=32 time=306ms TTL=50
Reply from 87.248.221.221: bytes=32 time=292ms TTL=50
Reply from 87.248.221.221: bytes=32 time=292ms TTL=50
Reply from 87.248.221.221: bytes=32 time=292ms TTL=50
Reply from 87.248.221.221: bytes=32 time=307ms TTL=50

Ping statistics for 87.248.221.221:
    Packets: Sent = 6930, Received = 6850, Lost = 80 (1% loss),
Approximate round trip times in milli-seconds:
    Minimum = 191ms, Maximum = 2090ms, Average = 303ms

Pinging cds503.par.llnw.net [87.248.221.221] with 32 bytes of data:
Reply from 87.248.221.221: bytes=32 time=317ms TTL=50
Reply from 87.248.221.221: bytes=32 time=303ms TTL=50
Reply from 87.248.221.221: bytes=32 time=299ms TTL=50
Reply from 87.248.221.221: bytes=32 time=299ms TTL=50

Ping statistics for 87.248.221.221:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 299ms, Maximum = 317ms, Average = 304ms

Pinging cds544.par.llnw.net [178.79.215.32] with 32 bytes of data
Reply from 178.79.215.32: bytes=32 time=301ms TTL=50
Reply from 178.79.215.32: bytes=32 time=390ms TTL=50
Reply from 178.79.215.32: bytes=32 time=311ms TTL=50
Reply from 178.79.215.32: bytes=32 time=351ms TTL=50

Ping statistics for 178.79.215.32:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 301ms, Maximum = 390ms, Average = 338ms

Trace Routes

Tracing route to cds503.par.llnw.net [87.248.221.221]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.1.1
  2    13 ms     7 ms     8 ms  dsl-197-245-14-1.voxdsl.co.za [197.245.14.1]
  3     *        *        *     Request timed out.
  4    96 ms    96 ms   109 ms  41.193.3.102
  5   121 ms   119 ms   122 ms  196.41.12.0
  6   119 ms   113 ms   132 ms  41.193.32.149
  7   266 ms   289 ms   290 ms  196.41.9.34
  8   290 ms   284 ms   280 ms  196.41.27.114
  9   323 ms   286 ms   301 ms  ldn-b3-link.telia.net [213.248.100.161]
 10   338 ms   299 ms   296 ms  ldn-bb2-link.telia.net [62.115.140.246]
 11   339 ms   265 ms   285 ms  adm-bb4-link.telia.net [62.115.134.26]
 12   295 ms   332 ms   316 ms  adm-b7-link.telia.net [80.91.245.245]
 13   313 ms   291 ms   299 ms  limelight-ic-154704-adm-b7.c.telia.net [80.239.1
94.114]
 14   292 ms   348 ms   293 ms  tge7-4.fr4.frf.llnw.net [69.28.171.53]
 15   301 ms   307 ms   315 ms  tge1-3.fr4.par.llnw.net [69.28.172.101]
 16   295 ms   298 ms   300 ms  cds503.par.llnw.net [87.248.221.221]

Trace complete.

Tracing route to cds544.par.llnw.net [178.79.215.32]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2   112 ms   109 ms   112 ms  dsl-197-245-14-1.voxdsl.co.za [197.245.14.1]
  3   220 ms   139 ms   129 ms  41.193.3.101
  4   123 ms   119 ms   119 ms  41.193.3.102
  5   122 ms   119 ms   121 ms  196.41.12.0
  6   137 ms   132 ms   142 ms  41.193.32.137
  7   123 ms   122 ms   119 ms  41.193.32.198
  8   296 ms   291 ms   287 ms  196.41.27.54
  9   289 ms   291 ms   287 ms  196.41.27.114
 10   295 ms   297 ms   295 ms  ldn-b3-link.telia.net [213.248.100.161]
 11   294 ms   288 ms   283 ms  ldn-bb3-link.telia.net [62.115.134.130]
 12   295 ms   297 ms   303 ms  adm-bb3-link.telia.net [62.115.136.146]
 13   291 ms   303 ms   303 ms  adm-b7-link.telia.net [80.91.245.135]
 14   298 ms   309 ms   306 ms  limelight-ic-154704-adm-b7.c.telia.net [80.239.1
94.114]
 15   305 ms   306 ms   303 ms  tge7-4.fr4.frf.llnw.net [69.28.171.53]
 16   302 ms   329 ms   318 ms  tge1-3.fr4.par.llnw.net [69.28.172.101]
 17   305 ms   311 ms   306 ms  cds544.par.llnw.net [178.79.215.32]

Trace complete.

Download from cds503.par.llnw.net [87.248.221.221] was Interrupted at 75% ..
Resumed now at 80 % from cds544.par.llnw.net [178.79.215.32] ...

Bashley · Aug 5, 2015

Hi there,
Is it possible to get a test account? I would like to sign up as soon as possible. I would prefer if I could test the latency first.

Thanks

techead · Aug 5, 2015

inactive line.

ajan · Aug 5, 2015

Bashley said:
Hi there,
Is it possible to get a test account? I would like to sign up as soon as possible. I would prefer if I could test the latency first.

Thanks

Sadly the latency, during peak on weekdays, is not great.

DrJohnZoidberg · Aug 5, 2015

^ Rock solid here again tonight.

Code:

PING 46.23.67.190 (46.23.67.190) 56(84) bytes of data.
64 bytes from 46.23.67.190: icmp_seq=1 ttl=53 time=158 ms
64 bytes from 46.23.67.190: icmp_seq=2 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=3 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=4 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=5 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=6 ttl=53 time=158 ms
64 bytes from 46.23.67.190: icmp_seq=7 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=8 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=9 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=10 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=11 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=12 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=13 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=14 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=15 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=16 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=17 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=18 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=19 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=20 ttl=53 time=157 ms
^C
--- 46.23.67.190 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19568ms
rtt min/avg/max/mdev = 156.505/157.222/158.213/0.516 ms

ajan · Aug 5, 2015

DrJohnZoidberg said:

^ Rock solid here again tonight.

Code:

PING 46.23.67.190 (46.23.67.190) 56(84) bytes of data.
64 bytes from 46.23.67.190: icmp_seq=1 ttl=53 time=158 ms
64 bytes from 46.23.67.190: icmp_seq=2 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=3 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=4 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=5 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=6 ttl=53 time=158 ms
64 bytes from 46.23.67.190: icmp_seq=7 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=8 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=9 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=10 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=11 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=12 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=13 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=14 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=15 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=16 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=17 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=18 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=19 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=20 ttl=53 time=157 ms
^C
--- 46.23.67.190 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19568ms
rtt min/avg/max/mdev = 156.505/157.222/158.213/0.516 ms

Code:

Pinging 46.23.67.190 with 32 bytes of data:
Reply from 46.23.67.190: bytes=32 time=226ms TTL=53
Reply from 46.23.67.190: bytes=32 time=211ms TTL=53
Reply from 46.23.67.190: bytes=32 time=215ms TTL=53
Reply from 46.23.67.190: bytes=32 time=229ms TTL=53
Reply from 46.23.67.190: bytes=32 time=230ms TTL=53
Reply from 46.23.67.190: bytes=32 time=220ms TTL=53
Reply from 46.23.67.190: bytes=32 time=222ms TTL=53
Reply from 46.23.67.190: bytes=32 time=211ms TTL=53
Reply from 46.23.67.190: bytes=32 time=213ms TTL=53

forgot to state: pings from cape town.

mstaylor · Aug 5, 2015

ajan said:

Code:

Pinging 46.23.67.190 with 32 bytes of data:
Reply from 46.23.67.190: bytes=32 time=226ms TTL=53
Reply from 46.23.67.190: bytes=32 time=211ms TTL=53
Reply from 46.23.67.190: bytes=32 time=215ms TTL=53
Reply from 46.23.67.190: bytes=32 time=229ms TTL=53
Reply from 46.23.67.190: bytes=32 time=230ms TTL=53
Reply from 46.23.67.190: bytes=32 time=220ms TTL=53
Reply from 46.23.67.190: bytes=32 time=222ms TTL=53
Reply from 46.23.67.190: bytes=32 time=211ms TTL=53
Reply from 46.23.67.190: bytes=32 time=213ms TTL=53

Pinging 46.23.67.190 with 32 bytes of data:
Reply from 46.23.67.190: bytes=32 time=184ms TTL=54
Reply from 46.23.67.190: bytes=32 time=183ms TTL=54
Reply from 46.23.67.190: bytes=32 time=179ms TTL=54
Reply from 46.23.67.190: bytes=32 time=184ms TTL=54

JHB->LND

AntiGanda · Aug 5, 2015

techead said:
inactive line.

View attachment 241072

Looks just like my axxess account.

Kayoss · Aug 5, 2015

Orbiter said:
smtp.datapro.co.za

Thanks, but unfortunately this didn't work for me either.

I have now tried the following servers:

smtp.voxtelecom.co.za
smtp.lantic.net
smtp.datapro.co.za

I have tried each of them on ports 25 and 587, without any luck.

The emails will show as sent, but they are never received on the other end. I keep having to swap back to my axxess account every time I have to send an email.

Anyone have any idea?

JonesY · Aug 6, 2015

"Upgraded" my 100GB Fatpipe to the new 300GB promo today. Turns out I had to add the package and then request to cancel my older packages thereafter (includes 25GB -Gig4gig replacement- package+Bolt-on). Only problem with this is, rep scheduled my cancellations for 1 September - following their calendar month notice period.

First ISP I've come across, besides for MTN, that can't upgrade packages without unnecessarily pocketing a few extra rand.

PS Voxy recommended that I email cancellations rep. :|

EDIT: Account 9023296

sand_man · Aug 6, 2015

I wanted to grab 1 x 300gb and cancel 3 x 100gb. Was also told the 3 x 100gb would run until the end of September.

I'll decide closer to the end of the month if I'm going to absorb the cost for the convenience. That's if there any 300gb promos left by the end of the month.

ajan · Aug 6, 2015

sand_man said:
I wanted to grab 1 x 300gb and cancel 3 x 100gb. Was also told the 3 x 100gb would run until the end of September.

I'll decide closer to the end of the month if I'm going to absorb the cost for the convenience. That's if there any 300gb promos left by the end of the month.

Where did you hear about the 100gb accounts coming to an end in September? The promotion specifically stated, until 100gb package was no longer a thing unless they planning to end it in September.

Join the MyBroadband community

Get started

Vox Telecom Fatpipe

Senior Member

Banned

Honorary Master

Expert Member

Honorary Master

Expert Member

Honorary Master

Well-Known Member

Expert Member

Well-Known Member

Honorary Master

Senior Member

Honorary Master

Senior Member

Banned

Banned

Expert Member

Well-Known Member

Honorary Master

Senior Member