NightShift
Expert Member
- Joined
- Oct 8, 2009
- Messages
- 1,952
- Reaction score
- 1,404
please sort this **** out...
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
long term issue with iBurst sharing IP's
Low to zero international capability, Timeouts etc. in Cape Town.
please sort this **** out...
Yes. ****
We pay for a service and it's not being provided.
sort this **** out...
The yellow submarine has national issues and as such local national IP transit has failed.
We apologize for the inconvenience.
long term issue with iBurst sharing IP's
http://mybroadband.co.za/vb/showthread.php/182168-Transparent-Proxy-Issues
original posts appear to have been join and labled under a more friendly title, original was "iBurst IP blocked as leaching bot". This was said to be scheduled for fixing in January. Safe to assume iBurst uses this connection method because it is cheaper for them and they don't really care.
check out www.whatismyip.com
then go to www.projecthoneypot.com and search your IP there.
Mine is "The Project Honey Pot system has detected behavior from the IP address consistent with that of a spam harvester and comment spammer."
Filesonic will most likely tell you they can't do anything about it and refer you to your ISP, good luck.
Thanks for the info. It's strange, been using Filesonic for 2 months without any issues, now suddenly I get this.
r00i, can I PM you my IP address, can you sort this out from iBurst's side?
Don't apologise. Fix it. (I know it's not your fault so don't take this personally)
I and thousands of other PAYING users are seriously P*ssed off at the moment.
ETA on fix and exact nature of the national IP transit failure? (B.t.w. does it affect other ISP's as well?)
Let me try this on 3G and see if they have problems as well...
Sorry, that you are pissed off. The feedback from is that they are investigating.
Do you have a static?
So you don't know what the problem is in other words...
ETA on fix ?
Can't check my 3G because the modem is @ work.
No,
But it's working now... Looks like the "Report Here" from Filesonic sorted out the problem. Thanks anyway
EDIT: Spoke too soon... getting the same message again.