Iwayafrica.co.zw
Iwayafrica is ranked 1,319,099 in the United Kingdom. 'iWayAfrica - Broadband Internet Service Provider.'
1,319,099Rank in United Kingdom
2,062,788Worldwide Rank
Monthly pages viewed | 9,526 | |
Monthly visits | 2,334 | |
Value per visitor | -- | |
Estimated worth | £1,094.31 | |
External links | 36 | |
Number of pages | 390 |
Last Updated: 06/04/2018 . Estimated data, read disclaimer.
Visitors
Traffic History 90 Day Average | ||
Worldwide Rank | 1,733,435 | -1,160,615 |
---|---|---|
Daily Visitors | 150 | +80% |
Daily Visitors Rank | 1,675,521 | -1,192,926 |
Daily Pageviews | 300 | +70% |
Daily Pageviews Rank | 2,126,271 | -1,192,689 |
Pageviews Per User | 2.10 | -2.76% |
Content
www.Iwayafrica.co.zw
- Popular pages
- iwayafrica.co.zw iWayAfrica Home
- iwayafrica.co.zw iWayAfrica - Zimbabwe
- iwayafrica.co.zw Online Marketing
- iwayafrica.co.zw iWayAfrica Broadband Solutions
The site has about 164 users daily, viewing on average 2.10 pages each.
Links- Links in
- smszim.com SmS Zimbabwe - Send Free SmS to Econet, Telecel, NetOne - SmS.co.zw
- mwebafrica.com MWEB Nigeria Products
- yellowdirectory.co.zw Home - Zimbabwe's Yellow Directory
- Links out
- bharatinfoservice.com Bharat Info Service
- burujsolutions.com Buruj Solutions
- comradefatso.com Comrade Fatso Home
- al-barr.com AL-Barr
Server Location | |
M-web Cape Town South Africa -33.92, 18.42 |
ns1.iwayafrica.co.zw, and ns2.iwayafrica.net are its DNS Nameservers. Its web server is located at M-web Cape Town. Iwayafrica.co.zw's IP address is 196.2.64.32.
IP: 196.2.64.32
PING www. (196.2.64.145) 56(84) bytes of data. | |
64 bytes from baobab. (196.2.64.145): icmp_seq=1 ttl=49 | 407 ms |
64 bytes from baobab. (196.2.64.145): icmp_seq=2 ttl=49 | 347 ms |
64 bytes from baobab. (196.2.64.145): icmp_seq=3 ttl=49 | 350 ms |
--- www. ping statistics --- | |
3 packets transmitted, 3 received, 0% packet loss, time 2000ms | |
rtt min/avg/max/mdev = 347.930/368.491/407.374/27.513 ms | |
rtt min/avg/max/mdev = 347.930/368.491/407.374/27.513 ms |
Pinging the server, resulted in a 407 ms response.