Burst.net [MERGED]

Portal Home > Knowledgebase > Articles Database > Burst.net [MERGED]

Posted by John[H4Y], 02-17-2007, 10:17 PM
Lots of packetloss?
Posted by WhiteBear, 02-17-2007, 10:18 PM
Hello friends, Nocster/Burst downtime? Thank you,
Posted by Odd Fact, 02-17-2007, 10:21 PM
Yes it does appear to be an issue.
Posted by HostJedi, 02-17-2007, 10:39 PM
Some kind of attack or issue with the Top Layer units again. It's being worked on and should be resolved very shortly. . .
Posted by John[H4Y], 02-17-2007, 10:54 PM
Very strange.. when the pings come through, they come through with no extra delay, but then there are periods when pings timeout. Good, then nothing, then good, then nothing, etc. Never seen one of these with this type of pattern yet.
Posted by John[H4Y], 02-17-2007, 10:58 PM
Things are looking better now.. resolved?
Posted by HostJedi, 02-17-2007, 10:59 PM
OK, should be alright now. Top Layers were acting flakey again... For all the good they do protecting the network they cause issues of their own unfortunately :-( Better of two evils I guess though... . .
Posted by HostJedi, 02-17-2007, 11:04 PM
might see a few sporadic things while we work on this still... . .
Posted by Xandrios, 02-17-2007, 11:04 PM
It looks like its fixed, but I really do hope that this was the last time.
Posted by HostJedi, 02-17-2007, 11:10 PM
<< It looks like its fixed, but I really do hope that this was the last time. >> I can assure you that it will not be. Network attacks will not mysteriously disappear from the Internet all of a sudden. ...and you cannot block/protect against attacks that do not even exist yet. . .
Posted by Xandrios, 02-17-2007, 11:14 PM
Off course. But isn't that toplayer hardware meant to minimalise the damage? It looks like it now only makes things worse... But I have no complete overview over the actual problem, so I cant say anything for sure here. Its just looks like the packetloss should not have been caused. Also depending on the fix that you guys just applied....
Posted by HostJedi, 02-17-2007, 11:34 PM
It does minimize the damage. Our nework is under constant attack 24/7/365---but that goes completely unnoticed by our client base because 99.9% of the attacks get blocked by the Top Layer or other methods in place. Once in awhile though the Top Layers don't respond well to certain new attacks or things they are not yet configured to block against, and that can cause issues such as latency and packet loss. We have to get Top Layer to update configurations and/or their system code in such cases. . .
Posted by juju, 02-18-2007, 12:27 AM
Hi, It looks like it's down again
Posted by Alex, 02-18-2007, 12:37 AM
Looks fine to me. Perhaps it's just your server, and you should contact them? Alex
Posted by juju, 02-18-2007, 01:15 AM
2 hours ago they said "We are currently experiencing an internal networking issue and our network administrators are currently working to fix this problem. I apologize for the inconvience"
Posted by juju, 02-18-2007, 01:23 AM
it's okay now