darylnunn123
Member
I get around the same during the day. I'll do some tests after 7:30pm and post them
-
- News
-
Categories
- 5G
- ADSL
- AI
- Banking
- Black Friday
- Broadband
- Broadcasting
- Business
- Business Telecoms
- Cellular
- Cloud and Hosting
- Columns
- Cryptocurrency
- Energy
- Enterprise
- Fibre
- Gadgets
- Gaming
- Government
- Hardware
- Industry News
- Internet
- Internet of Things
- Investing
- IT Services
- Motoring
- Reviews
- Science
- Security
- Smartphones
- Software
- Technology
- Telecoms
- Trending
- Wireless
- Press Office
- Forum
- Industry News
- What's Next
- Company hub
- Speed Test
- About us
- Advertise with us
- Contact
- Careers
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Will you be subscribing to the new Disney+ R49 streaming package?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Neotel Wimax Latency Test requests
- Thread starter Mr.Jax
- Start date
darylnunn123
Member
No I'm on Neotel Wimax...read the beginning of this post. I posted all kinds of tests before!
here's a test:
Pinging 196.38.180.45 with 32 bytes of data:
Reply from 196.38.180.45: bytes=32 time=40ms TTL=56
Reply from 196.38.180.45: bytes=32 time=48ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=40ms TTL=56
Reply from 196.38.180.45: bytes=32 time=38ms TTL=56
Reply from 196.38.180.45: bytes=32 time=36ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=47ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=37ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=37ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=47ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=40ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=48ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=40ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=37ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=37ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=38ms TTL=56
Reply from 196.38.180.45: bytes=32 time=36ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Ping statistics for 196.38.180.45:
Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 48ms, Average = 42ms
this was tested at 21:34
here's a test:
Pinging 196.38.180.45 with 32 bytes of data:
Reply from 196.38.180.45: bytes=32 time=40ms TTL=56
Reply from 196.38.180.45: bytes=32 time=48ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=40ms TTL=56
Reply from 196.38.180.45: bytes=32 time=38ms TTL=56
Reply from 196.38.180.45: bytes=32 time=36ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=47ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=37ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=37ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=47ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=40ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=48ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=40ms TTL=56
Reply from 196.38.180.45: bytes=32 time=46ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=37ms TTL=56
Reply from 196.38.180.45: bytes=32 time=45ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=42ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Reply from 196.38.180.45: bytes=32 time=37ms TTL=56
Reply from 196.38.180.45: bytes=32 time=44ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=38ms TTL=56
Reply from 196.38.180.45: bytes=32 time=36ms TTL=56
Reply from 196.38.180.45: bytes=32 time=43ms TTL=56
Reply from 196.38.180.45: bytes=32 time=41ms TTL=56
Reply from 196.38.180.45: bytes=32 time=39ms TTL=56
Ping statistics for 196.38.180.45:
Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 48ms, Average = 42ms
this was tested at 21:34
This is what I am experiencing everyday after 7pm on My 4mb. Thnx alot dude.really appreciate it
Pinging 196.38.180.45 with 32 bytes of data:
Reply from 196.38.180.45: bytes=32 time=184ms TTL=56
Reply from 196.38.180.45: bytes=32 time=180ms TTL=56
Reply from 196.38.180.45: bytes=32 time=150ms TTL=56
Reply from 196.38.180.45: bytes=32 time=151ms TTL=56
Pinging 196.38.180.45 with 32 bytes of data:
Reply from 196.38.180.45: bytes=32 time=184ms TTL=56
Reply from 196.38.180.45: bytes=32 time=180ms TTL=56
Reply from 196.38.180.45: bytes=32 time=150ms TTL=56
Reply from 196.38.180.45: bytes=32 time=151ms TTL=56
Mr.Jax
Expert Member
I'm very keen.
Just a few questions to the existing users. Whats the reliability like in terms of service availability ? Have you dealt with technical support regarding issues lately and if so, how quickly were it resolved ?
Thanks in advance!
Just a few questions to the existing users. Whats the reliability like in terms of service availability ? Have you dealt with technical support regarding issues lately and if so, how quickly were it resolved ?
Thanks in advance!
Spoke to Neotel WiMaX department. Pricing on website is inclusive of VAT, they made a mistake
1mb - R1299 Inc VAT and Installation is R1500 Inc VAT
etc etc
Interesting, I received a quote from them last week and the amounts was 1299 ex VAT and 1500 ex VAT. The total quoted was 1710 for install and 1480.86/month... Also note that the standard quote is for a 24 month contract - I pushed them on this but they would not budge lower than 12 months. This put me off as we do not know a.) what will happen to bandwidth prices over the next 12 months (still need to see EASSY's impact and SEACOM directly selling connections to ISP's bypassing Neotel's ridiculous datacentre charges) and also do not want to be locked into a service that degrades over time as more and more customers get on board and it gets congested...
Confirmed the amount is R1299 Inc VAT and R1500 Inc for install, subjected to a 12 month contract
If any service is going to degrade over time it will be telkom, they are using Copper lines and have made it clear that they are staying on it. The entire world are using Fibre which is what Neotel has put in all the Cities. If there is any way forward Neotel would have to be it with the Fibre lines.
Neotels Offering is also Unshaped and i doubt that any ISP in the near future will give Unshaped Pure BW for under R60per/gb. The more the Wimax gets used the more the need for neotel to give all its customers Fibre links to there house, similarly how they started changing there NeoFlex users to WiMax.
The closest offering to Neobroadband Fibre/Wimax is Vox Fishbone bonding, which costs per rental of the lines/the rental of the bonding router and R80 per gb directly to SAT3.
If any service is going to degrade over time it will be telkom, they are using Copper lines and have made it clear that they are staying on it. The entire world are using Fibre which is what Neotel has put in all the Cities. If there is any way forward Neotel would have to be it with the Fibre lines.
Neotels Offering is also Unshaped and i doubt that any ISP in the near future will give Unshaped Pure BW for under R60per/gb. The more the Wimax gets used the more the need for neotel to give all its customers Fibre links to there house, similarly how they started changing there NeoFlex users to WiMax.
The closest offering to Neobroadband Fibre/Wimax is Vox Fishbone bonding, which costs per rental of the lines/the rental of the bonding router and R80 per gb directly to SAT3.
Mr.Jax
Expert Member
I'll email the dude I was in contact with previously...a key accounts manager @ neotel...to get some clarity regarding the pricing.
Mr.Jax
Expert Member
Does anyone know if this product goes via the same routing as telkom/ ? Does it use the same Exchanges/
I think they have their own infrastructure as far as possible.
My WiMax was installed on Friday. Quite a procedure, but all was done well. I went with the 1mb offering and from Saturday to Sunday, I uploaded 12gb and downloaded 16gb, this was off and on as well as I was gaming in between. I am getting 1.4mbps down and 0.90mbs up and latency of 25ms on average to the Local CT speedtest server. My latency to IS gaming this weekend was very stable between 50-60ms. Pretty impressed so far with the solution.
Mr.Jax
Expert Member
Cool. Please keep us updated with your experiences with it.