Please do an article on Uniforum

w1z4rd

Karmic Sangoma
Joined
Jan 17, 2005
Messages
52,146
Reaction score
8,340
Location
127.0.0.1
Yup.. http://co.za and http://www.co.za are down... again. Great coming from our ONLY suppliers of .co.za.

My next step is to start a petition to raise awareness for the terrible quality of service offered by Uniforum.

Could a staff writer please ask Uniform the following questions:

1) Why do their systems fall over a lot?
2) Why do they have almost the same terrible system they had 10 years ago?
3) Why do they not have a proper whois server? (that web query is pathetic)
4) Why does their registration server often fail to find international DNS servers when it does a registration check?
5) When are their staff going to learn how to be more polite?
6) When are they going to upgrade their systems to what ISP`s in South Africa need? (Web based DNS management)
7) When are they going to engage us more publicly instead of running from our cries for a better service.

Also, dont only speak to Uniform, speak to ISPs like Web Africa, OpenWeb and Afrihost... voice their concerns and ours please.
 
Last edited:
Define "down", cause it loads fine for me on this side.

Well from a normal saix account I can not load those sites? :confused:
Ive also sent through a registration and have got nothing back from uniform? :confused:

Edit: Also cant access it on IS.
 
Last edited:
Well from a normal saix account I can not load those sites? :confused:
Edit: Also cant access it on IS.

Not loading on Vodascum, not loading via intl proxy, not loading via opera mini proxy....Loading fine on TENET though.
 
Seems down from quite a few locations, up from MTN though.. Looks more like a network issue @ POSIX

WebNX USA
root@gemini [~]# ping co.za -c 10
PING co.za (206.223.136.173) 56(84) bytes of data.

--- co.za ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

----------

root@gemini [~]# traceroute co.za
traceroute to co.za (206.223.136.173), 30 hops max, 40 byte packets
1 216-18-214-233.hosted.static.webnx.com (216.18.214.233) 0.395 ms 0.406 ms 0.505 ms
2 cr3-lax01.webnx.com (67.220.192.102) 0.368 ms 0.374 ms 0.475 ms
3 67.199.135.233 (67.199.135.233) 0.466 ms 0.741 ms 0.750 ms
4 te0-1.cr01.phx01.us.mzima.net (69.174.120.34) 17.974 ms 18.226 ms 18.220 ms
5 te0-0.cr01.dfw01.us.mzima.net (69.174.120.38) 38.542 ms 38.546 ms 38.539 ms
6 te1-0.cr01.ord01.us.mzima.net (69.174.120.13) 55.342 ms 61.275 ms 62.799 ms
7 te4-5.cr01.lga01.us.mzima.net (69.174.120.73) 86.929 ms 86.909 ms 86.897 ms
8 xe1-1.cr01.lga01.us.mzima.net (216.193.255.86) 77.281 ms 77.288 ms 77.282 ms
9 nyiix.is.co.za (198.32.160.26) 147.625 ms 147.594 ms 147.595 ms
10 core2a-ny-gi1-0-10-8.ip.isnet.net (168.209.245.4) 145.847 ms 145.817 ms 146.055 ms
11 mi-us-25b-p2-gi0-1-304.ip.isnet.net (168.209.164.127) 348.672 ms 348.430 ms 348.655 ms
12 mi-za-rba-p6-gi2-0-4.ip.isnet.net (168.209.160.218) 348.386 ms 351.140 ms 351.128 ms
13 core2b-rba-gi1-0-3-304.ip.isnet.net (168.209.164.174) 351.079 ms 346.314 ms *
14 196.26.0.3 (196.26.0.3) 334.591 ms 333.150 ms 333.466 ms
15 * * *
16 cisrb1.posix.co.za (160.124.2.1) 333.898 ms 333.397 ms 333.393 ms
17 * * *
18 * * *

Server @ IS.

[[email protected]:~ ] > ping co.za -c 10
PING co.za (206.223.136.173) 56(84) bytes of data.

--- co.za ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

--------------

[[email protected]:~ ] > traceroute co.za
traceroute to co.za (206.223.136.173), 30 hops max, 40 byte packets
1 196.34.136.97 (196.34.136.97) 0.251 ms 0.264 ms 0.244 ms
2 csw1-b-jup-bry-vl2616.ip.isnet.net (196.34.134.253) 0.642 ms 0.770 ms 0.851 ms
3 core2a-bry-gi0-0-0.ip.isnet.net (168.209.217.2) 0.561 ms 0.537 ms 0.514 ms
4 core6a-rba-gi0-0-1.ip.isnet.net (168.209.100.202) 0.951 ms 0.858 ms 0.920 ms
5 196.26.0.3 (196.26.0.3) 1.770 ms 1.748 ms 1.728 ms
6 168.209.69.241 (168.209.69.241) 1.423 ms 1.403 ms 1.383 ms
7 cisrb1.posix.co.za (160.124.2.1) 4.601 ms 4.939 ms 4.914 ms
8 cispos2-cisrb1.posix.co.za (160.124.1.54) 98.960 ms 99.894 ms 101.230 ms
9 * * *
10 * * *

MTN DC JHB
root@jupiter [~]# ping co.za -c 10
PING co.za (206.223.136.173) 56(84) bytes of data.
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=1 ttl=55 time=5.45 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=2 ttl=55 time=5.27 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=3 ttl=55 time=5.58 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=4 ttl=55 time=4.99 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=5 ttl=55 time=6.48 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=6 ttl=55 time=6.30 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=7 ttl=55 time=5.42 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=8 ttl=55 time=5.44 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=9 ttl=55 time=5.26 ms
64 bytes from www.coza.net.za (206.223.136.173): icmp_seq=10 ttl=55 time=5.17 ms

--- co.za ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9001ms
rtt min/avg/max/mdev = 4.995/5.541/6.485/0.462 ms

-------

root@jupiter [~]# traceroute co.za
traceroute to co.za (206.223.136.173), 30 hops max, 40 byte packets
1 vz1-jnb.za-dns.com (41.203.22.76) 0.051 ms 0.031 ms 0.014 ms
2 (41.72.136.3) 0.476 ms 0.620 ms 0.712 ms
3 (196.30.213.105) 0.561 ms 0.557 ms 0.634 ms
4 ge4-0-0.gw1.jnb6.za.mtnbusiness.net (196.30.156.130) 0.761 ms 0.739 ms 0.708 ms
5 ge0-2.cr1.jnb7.za.mtnbusiness.net (196.30.121.101) 1.545 ms 1.701 ms 1.676 ms
6 ge0-2.br1.jnb7.za.mtnbusiness.net (196.30.228.121) 1.648 ms 1.858 ms 1.972 ms
7 uniforum.jinx.net.za (198.32.142.29) 2.208 ms 4.642 ms 2.586 ms
8 cisufrm2-cisufrmjnx.coza.net.za (206.223.136.25) 5.334 ms 5.598 ms 6.152 ms
9 www.coza.net.za (206.223.136.173) 6.766 ms 7.095 ms 7.547 ms
 
/me waits for registration to go through.

My co-worker has requested a new server, installed the OS, installed panels, plugins, bells and whistles and finished configuration faster than its taking to register a .co.za :(
 
Just got this:

The CO.ZA Telkom lines have gone down.

This means that those who do not peer with us at JINX are unable to reach the CO.ZA systems.

Apologies for the inconvenience.

If you can't get to us - you may want to get your network guys to chat with us to set up correct peering @ JINX going forward.

regards

--The CO.ZA team

Looks like IS made some changes in their routing to COZA...

[[email protected]:~ ] > traceroute co.za
traceroute to co.za (206.223.136.173), 30 hops max, 40 byte packets
1 196.34.136.97 (196.34.136.97) 0.263 ms 0.234 ms 0.216 ms
2 csw1-b-jup-bry-vl2616.ip.isnet.net (196.34.134.253) 0.640 ms 0.775 ms 0.760 ms
3 core2a-bry-gi0-0-0.ip.isnet.net (168.209.217.2) 0.581 ms 0.563 ms *
4 core2a-pkl-gi0-0-3-0.ip.isnet.net (168.209.100.197) 2.847 ms 2.826 ms 2.810 ms
5 ch8-rba-gi0-2.ip.isnet.net (168.209.1.157) 2.340 ms 2.304 ms 2.424 ms
6 168.209.126.46 (168.209.126.46) 76.530 ms 77.343 ms 81.591 ms
7 www.coza.net.za (206.223.136.173) 80.607 ms 78.951 ms 86.335 ms
 
Last edited:
Its unbelievable that its the 21st century and they still use a text based application for new domains and modifications
 
Its unbelievable that its the 21st century and they still use a text based application for new domains and modifications

Can you imagine. Thought this was long sorted. Funding for this most likely went into the new E-Class !!
 
Uniform definately needs a swift boot into the 21st century, a few things they should definately fix.

1) Web based management
2) Central management for multiple domain owners (I just want a list with renew dates in a nice table)
3) Whois... I mean honestly the web query idea is terrible
4) Kill the voting idea for changes (have not made a change for ages but I assume you still need to "vote")
5) Instant domain registrations and changes, somedays you can wait several hours before you get the "OKAY" mail
6) Secure credit card payments, honestly everytime I see the credit card page I get a pain in a place uniform should be kicked.
7) Point 6 meet point 2 as well please, tick boxes next to a list of domains and a pay now button.

Some information to be considered available here although considering they took over in 2004 ZADNA also needs kick for dragging their feet.
 
Last edited:
Uniform definately needs a swift boot into the 21st century, a few things they should definately fix.

1) Web based management
2) Central management for multiple domain owners (I just want a list with renew dates in a nice table)
3) Whois... I mean honestly the web query idea is terrible
4) Kill the voting idea for changes (have not made a change for ages but I assume you still need to "vote")
5) Instant domain registrations and changes, somedays you can wait several hours before you get the "OKAY" mail
6) Secure credit card payments, honestly everytime I see the credit card page I get a pain in a place uniform should be kicked.
7) Point 6 meet point 2 as well please, tick boxes next to a list of domains and a pay now button.

Some information to be considered available here although considering they took over in 2004 ZADNA also needs kick for dragging their feet.

Hey Alchemy,

It seems like Uniforum are at last heading towards the 21st century.

http://mybroadband.co.za/vb/showthread.php?236059-Uniforum-SA-revamps-.co.za-system

Seems they finally have gotten around their "well if this worked for the voortrekkers it will work for us" mentality.

Regards,
w1z
 
Top
Sign up to the MyBroadband newsletter
X