burst.net Miami DC packet lost

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > burst.net Miami DC packet lost

Posted by infracom2005, 02-14-2012, 07:22 PM
anyone know what happen? All vps in this dc have packet lost in all world Location Result min. rrt avg. rrt max. rrt IP Singapore, Singapore: Packets lost (40%) 280.6 281.0 281.6 184.22.122.136 Amsterdam2, Netherlands: Okay 127.6 127.8 128.0 184.22.122.136 Florida, U.S.A.: Packets lost (70%) 15.8 15.9 16.0 184.22.122.136 Amsterdam3, Netherlands: Okay 120.9 121.0 121.3 184.22.122.136 Hong Kong, China: Okay 331.9 332.3 333.4 184.22.122.136 Sydney, Australia: Okay 250.2 256.8 306.5 184.22.122.136 MÃ¼nchen, Germany: Packets lost (50%) 130.3 130.9 131.5 184.22.122.136 Cologne, Germany: Okay 119.6 119.7 119.8 184.22.122.136 New York, U.S.A.: Packets lost (60%) 67.3 67.4 67.5 184.22.122.136 Stockholm, Sweden: Packets lost (50%) 149.3 149.4 149.5 184.22.122.136 Santa Clara, U.S.A.: Okay 79.9 80.5 83.3 184.22.122.136 Vancouver, Canada: Packets lost (60%) 109.2 110.3 111.1 184.22.122.136 London, United Kingdom: Packets lost (80%) 109.9 110.3 110.6 184.22.122.136 Madrid, Spain: Packets lost (60%) 169.8 171.9 174.1 184.22.122.136 Padova, Italy: Okay 153.5 154.2 154.6 184.22.122.136 Austin, U.S.A.: Packets lost (40%) 42.7 43.4 44.6 184.22.122.136 Amsterdam, Netherlands: Packets lost (60%) 126.2 126.7 127.0 184.22.122.136 Paris, France: Okay 203.2 203.7 204.1 184.22.122.136 Shanghai, China: Okay 220.0 220.4 220.8 184.22.122.136 Melbourne, Australia: Okay 235.6 237.2 241.2 184.22.122.136 Copenhagen, Denmark: Packets lost (70%) 161.9 162.0 162.1 184.22.122.136 Lille, France: Packets lost (50%) 110.1 111.5 112.5 184.22.122.136 San Francisco, U.S.A.: Okay 71.3 71.8 72.4 184.22.122.136 Zurich, Switzerland: Packets lost (70%) 133.7 133.8 133.9 184.22.122.136 Mumbai, India: Packets lost (60%) 246.9 248.0 250.8 184.22.122.136 Chicago, U.S.A.: Okay 52.0 52.1 52.1 184.22.122.136 Nagano, Japan: Packets lost (40%) 196.6 207.5 213.1 184.22.122.136 Haifa, Israel: Packets lost (50%) 192.8 194.3 199.9 184.22.122.136 Auckland, New Zealand: Okay 297.1 297.8 298.4 184.22.122.136 Antwerp, Belgium: Packets lost (80%) 144.8 144.8 144.8 184.22.122.136 Groningen, Netherlands: Packets lost (40%) 116.6 116.8 117.2 184.22.122.136 Moscow, Russia: Okay 245.9 246.1 246.4 184.22.122.136 Dublin, Ireland: Okay 105.3 118.8 174.5 184.22.122.136 Oslo, Norway: Okay 140.3 140.7 141.5 184.22.122.136 Kharkov, Ukraine: Okay 184.0 184.0 184.0 184.22.122.136 Manchester, United Kingdom: Packets lost (40%) 130.7 131.0 131.4 184.22.122.136 Vilnius, Lithuania: Packets lost (40%) 143.6 143.7 143.7 184.22.122.136 Bucharest, Romania: Okay 160.9 161.7 162.4 184.22.122.136 Bangkok, Thailand: Packets lost (80%) 296.1 297.6 299.2 184.22.122.136 Kuala Lumpur, Malaysia: Packets lost (40%) 753.5 754.7 757.0 184.22.122.136 Jakarta, Indonesia: Okay 280.8 288.9 302.0 184.22.122.136 Cape Town, South Africa: Okay 266.4 266.6 266.9 184.22.122.136 Glasgow, United Kingdom: Okay 119.8 120.2 121.8 184.22.122.136 Lisbon, Portugal: Okay 141.4 141.5 141.6 184.22.122.136 Chicago, U.S.A.: Packets lost (70%) 38.9 39.5 40.5 184.22.122.136 Dallas, U.S.A.: Okay 31.7 31.8 32.3 184.22.122.136 Cairo, Egypt: Okay 169.3 172.3 174.6 184.22.122.136 Amsterdam1, Netherlands: Okay 126.6 126.8 127.5 184.22.122.136 Buenos Aires, Argentina: Okay 119.3 119.4 119.7 184.22.122.136 Istanbul, Turkey: Packets lost (50%) 153.4 153.4 153.5 184.22.122.136 Gdansk, Poland: Packets lost (60%) 157.2 157.4 157.6 184.22.122.136 Beijing, China: Packets lost (60%) 274.7 300.3 375.9 184.22.122.136 Belgrade, Serbia: Okay 139.7 150.7 154.5 184.22.122.136 Toronto, Canada: Okay 67.1 67.3 67.7 184.22.122.136 Novosibirsk, Russia: Packets lost (60%) 232.4 232.5 232.5 184.22.122.136 Athens, Greece: Okay 173.7 174.3 175.0 184.22.122.136 Frankfurt, Germany: Packets lost (30%) 139.0 139.5 140.3 184.22.122.136 Sofia, Bulgaria: Packets lost (20%) 173.2 173.7 174.3 184.22.122.136 Budapest, Hungary: Packets lost (50%) 141.4 141.5 141.6 184.22.122.136 Sao Paulo, Brazil: Okay 138.1 145.8 148.9 184.22.122.136
Posted by Rens, 02-14-2012, 07:25 PM
Looks like a network problem. A mtr from a node of ours in Miami: Host Loss% Last Avg Best Wrst StDev 1. 46.182.109.1 0.0% 0.3 0.2 0.2 0.3 0.0 2. Port-channel2.487.ar1.MIA2.gblx.net 0.0% 0.4 3.9 0.3 85.7 17.4 3. PCCW.Te9-2.1101.csr1.DCA3.gblx.net 0.0% 29.8 29.9 29.8 30.1 0.1 4. arbinet.ge4-9.br01.mia02.pccwbtn.net 41.7% 29.5 41.9 29.4 203.6 46.5 5. ec0-64.1a0201.mifl01.hostnoc.net 0.0% 30.7 33.6 29.5 43.2 3.9 6. vserver4008.mifl01.hostnoc.net 54.5% 29.3 29.4 29.3 29.5 0.1 7. noc1.saicom.com.ar 39.1% 29.3 29.3 29.3 29.4 0.0 You will have to contact burst about this.
Posted by Postbox, 02-14-2012, 08:30 PM
What? You've tested ALL of them? You must have missed ours as we also have a VPS on vserver4008.mifl01.hostnoc.net and it's been 100% rock solid all day. This sounds specific to your VPS and nothing at all to do with network - Contact BurstNET support if you can't figure it out.
Posted by infracom2005, 02-14-2012, 08:33 PM
i have vps in different nodes and all failed now works fine
Posted by Postbox, 02-14-2012, 09:15 PM
We have VPSs on different nodes and NONE failed. Our monitoring for today (and previous) shows no issues. If there were any network-wide issue this thread would be several pages long by now. I suggest you work with support to find out what's wrong with your VPS(s) because it's certainly not a DC-wide problem.
Posted by nibb, 02-15-2012, 12:46 AM
I do get packet loss to Burst.net, 30% to 66% Exactly at Miami, its going via Cogent and there seems to be a problem with them in Miami. Im getting packet loss for hours to: te4-1.ccr02.mia03.atlas.cogentco.com Almost an average of 60% packet loss. Which is one of the route burst.net is taking from my location. Im just testing this directly with burst.net, I dont have any VPS with them. But im getting packet loss to them at that point.
Posted by HostJedi, 02-15-2012, 12:51 AM
We do not have Cogent in our Miami location, so the issue is probably external to our network, and our own carriers. There are no known network issues in Miami POP recently, and none of the nodes have any load issues either from what I can tell. I suggest you contact your ISP, and have them re-route your traffic. . .
Posted by nibb, 02-15-2012, 12:56 AM
Sure, its a Cogent issue. I just pointed out the exact place where its losing packets. My tests where directly to burst website.
Posted by HostJedi, 02-15-2012, 01:00 AM
So which is it? The burst.net website, or our Miami POP, which you are having issues? Those are two completely separate POPs...the burst.net site is not hosted in Miami. Regardless though, based on the Cogent Miami packetloss, the issue lies there, not with us... . .
Posted by nibb, 02-15-2012, 03:37 AM
I never said it was a burst issue and I never said burst.net is hosted in Miami. But from where im located, the traffic goes first via Miami, then to Atlanta, and finally to where burst.net is hosted. Like I said, I see packets loss directly to burst.net because you are using Cogent in your mix and im connected via Miami, so I do see the loss. I cannot possible tell which carriers or which route other people are seeing when connecting to burst.net. I just informed the one I see. I don´t know which Miami POP you have. I said my tests where directly to burst.net website. Last edited by nibb; 02-15-2012 at 03:41 AM.
Posted by ester_meireles, 02-16-2012, 10:23 AM
I have same problem. My ticket is open for 2 days and not solved yet.... Ticket ID: 3110949 Status: OPEN When Created: 02-14-2012 - 04:40PM Elapsed Time: 2 days Since Last Action: 4 hours See preview of ticket: _____-----_____---- Subject and Description vlinux2 is down Man, my VPS: 184.22.37.96 vlinux2.omeuhost.com.br Not load... is down again... please verif whit urgenci Ester Meireles 02-15-2012 - 09:40PM Brian S., promotionuptime.com monitors thousands of websites and is telling me that our VPSs can not be accessed from 13 places in the world. Why do you insist that the problem is on my network if it is proved that the world can not access? See: i42.tinypic.com/15fg075.png Brian S. 02-15-2012 - 10:43PM I am seeing no issues with the connection to this server at this time: just-ping.com/index.php?vh=184.22.122.154+&c=&s=ping! Brian S. Support Technician BurstNET - A Worldwide Leader in Web Hosting and Internet Rate this reply/followup Ester Meireles 02-16-2012 - 05:02AM still have some packet loss. but see my other server 265636.server1.filehost.com.br : just-ping.com/index.php?vh=184.22.116.174&c=&s=ping%21&vtt=1329386149&vhost=_&c= Ester Meireles 02-16-2012 - 05:07AM still have some packet loss. but see my other server 265636.server1.filehost.com.br : just-ping.com/index.php?vh=184.22.116.174&c=&s=ping%21&vtt=1329386149&vhost=_&c= I facilitate for you to put the ping result here: i39.tinypic.com/dw8ffo.png
Posted by Postbox, 02-16-2012, 10:45 AM
Because he's right. Your server is showing major packet loss from everywhere: http://just-ping.com/index.php?vh=18...7.96&c=&s=ping! But one of BurstNET's servers (another VPS node) is not: http://just-ping.com/index.php?vh=18...2.66&c=&s=ping! You're jumping to (wrong) conclusions - Check your firewall, network config, abusive user hogging all resources etc. EDIT: Even from another datacenter in Miami I'm seeing major packet loss for your server: But from the same server to a BurstNET VPS in Miami: It looks like the problem is with your server. Last edited by Postbox; 02-16-2012 at 10:50 AM.
Posted by SerayaHost, 02-16-2012, 11:29 AM
Maybe because of csf firewall if you have it installed? Make sure your give the icmp a good value on it.. Thanks..
Posted by pdqso, 02-16-2012, 12:13 PM
I have used BurstNET Miami in the past and have experienced packet loss, unstable connection and have decided to leave so that's not unheard of but if there is a firewall enabled, that should be disabled just to see if that's the problem.
Posted by ester_meireles, 02-16-2012, 12:14 PM
Ok, But because it is "right" he do not respond to customers more? The problem Is not in my firewall and this problem occurs on multiple VPSs that have not changed recently or configured. VPSs: 184.22.122.106 184.22.121.86 184.22.122.154 And other too The VPSs go down and come back...go down and come back...
Posted by ester_meireles, 02-16-2012, 12:22 PM
I agree. But the problem is in many VPSs and started without altering anything. If there a firewall blocking is Firewall on burst.net not in my VPSs. Now the VPSs is Ok but I dont now when is go donw again because it is just two days. burst.net does not help anyone or answer tickets...
Posted by BurstJoeM, 02-16-2012, 01:43 PM
What is your ticket number? I'm not aware of any escalated issue.
Posted by ester_meireles, 02-16-2012, 02:07 PM
Are in my first post... Ticket ID: 3110949
Posted by BurstJoeM, 02-16-2012, 02:18 PM
First, I want to apologize for how poorly this ticket was handled. After reviewing it, it appears our tech was not following proper troubleshooting procedures. I've looked into the issue and found the cause of your problem. This should be fixed. In the future, if you have a ticket that you dont believe is being handled properly, you may request that it be escalated.
Posted by ester_meireles, 02-16-2012, 02:45 PM
Thank You Joe but Is what I respond to my clients which are almost three days with the sites off the air? What is escalated? how I ask this if your do not respond to tickets? You do not have an online chat. I can not post messages on your forum why? Appears I a bandit am not a customer who pays their invoice on time.... Earlier this month you are several days off the air saying that the vendors that provides connectivity to our Miami datacenter is performing maintenance on their fiber lines. ******** ... spoke this only for not pay the SLA because there is no news anywhere in the maintenance of miami fiber. When maintenance is made to interrupt occurs for a few minutes and not for several days .... Who guarantees that the service will be stable now?
Posted by jeandanielle, 02-16-2012, 04:04 PM
The packet loss was due to some errors occuring during transmissions involving one of our darkfiber circuits. The vendor has been contacted and we hope for a prompt solution. Escalated tickets are reviewed by the next level of support or by management. Note that replies to escalated tickets may be delayed, since the proper personnel must be contacted and each situation is carefully reviewed. We offer this option for critical cases and incidents not resolved in a timely manner by the first level of support. While we have admitted the ticket could have been better handled and I offer you a sincere apology that the actual source of the packet loss went undetected for so long, I must say that you received several responses -- most within minutes of your last replies. BurstNET has chat available via AOL Instant Messenger (username = BurstNET). You should be able to post to BurstNET forum threads that are not closed. If you are unable to do so, this must be addressed by Customer Service. Please submit a ticket to this department and include your forum username, along with a link to the thread(s). *** Be sure to remember that official staff support is NOT provided via the BurstNET forums. This is not meant to be a mechanism to bypass normal support channels. The problem on 01/22 impacted routes to/from Miami for 27 hours. This was due to an unexpected issue during maintenance being done by Fiberlight (a large wholesale dark fiber carrier). This maintenance was not properly announced and the incident impacted both sides of a redundant/diverse fiber ring. While no one can absolutely guarantee that no problems will occur, we strive to maintain a 99.999% network and service uptime. We guarantee at least 99.5%. As I know you are aware, you may review our SLA for specific details and exceptions.
Posted by ester_meireles, 02-16-2012, 06:22 PM
BurstAbuseDept thank you for you explanations. I only not understand why the answer comes from the abuse department .... I abusing?! So there's something very wrong, Because someone straining to go down the services because you will not let me sleep in months BurstAbuseDept.... see my tickets for the last 3 months: i42.tinypic.com/huhv21.png practically every day have a server down.... And observe each ticket took 2 days to be resolved .... Really is very fiber cable to fix ... Honestly, what you are doing that such problems do not happen anymore?
Posted by BudWay, 02-17-2012, 07:15 PM
You could take some english lesons is very hard to read your message I can't imagine how you post tecnical data/info in a ticket to help solve the problem. The server are not fully-managed, a single user can crash a server if this server is not well-setup (even if it is well setup a user can abuse to make less responsive/loss-package) ------------ <> Either way good luck Last edited by Coolraul; 02-17-2012 at 08:38 PM. Reason: english only please
Posted by BudWay, 02-18-2012, 12:49 AM
Sorry for posting in portugues, but I saw that he posted his domain (.com.br) and from the level of his writing in english I bet he doesn't understand 100% what he/she reads.
Posted by ester_meireles, 03-07-2012, 12:47 AM
Again I'm over to 12 hours with all my VPSs DOWN. Do you believe that a company can let your customers down for more than 12 hours? Yes, burst.net do this .... They do not respond tickets and do not give estimates of when your system goes back. Tickts ID: 3143801 3142907 3142828
Posted by BurstJoeM, 03-07-2012, 12:50 AM
I'll have someone look into your issue. Regards,
Posted by BurstJoeM, 03-07-2012, 12:55 AM
It seems that 2 of your tickets are performance issues related to resource constraints within your VPS. I will have someone look into the issue ASAP, but your VPS is up and running and has not been down for over 12 hours.
Posted by ester_meireles, 03-07-2012, 01:02 AM
I was mistaken really All are down for more than 13 hours see: ------------------------------------------ Ticket ID: 3142828 Status: OPEN When Created: 03-06-2012 - 10:06AM Elapsed Time: 14 hours Since Last Action: 4 hours ------------------------------------------ Ticket Details Ticket ID: 3142907 Status: OPEN When Created: 03-06-2012 - 11:07AM Elapsed Time: 13 hours Since Last Action: 8 hours ------------------------------------------
Posted by BurstJoeM, 03-07-2012, 01:07 AM
Ive asked for your tickets to be reviewed by someone in support, so you should hear back from someone shortly. The all 3 are pingable, so support will need to work with you to isolate and resolve the issue. Hopefully, this is resolved soon for you. Regards,
Posted by ester_meireles, 03-07-2012, 01:11 AM
I opened three tickets but I have my nine VPSs down. Not one or two but nine VPSs that are down. If have a resource problem is on the main server.
Posted by ester_meireles, 03-07-2012, 01:16 AM
Now I have 8 VPSs down for than 14 hours. 1 as go back now.
Posted by ester_meireles, 03-07-2012, 01:34 AM
All servers are up again. I wait to 14 hours to solve the problem .... how many customers lost? do not really understand how this can happen. I could not work the whole day waiting a response from support.... I use Webmin and all VPSs returned with the message: Warning - Your system is actually running CentOS Linux version 6.2. Something has changed on the master server. If I not written here would have to wait another 12 hours for solve the problem. BurstJoeM, why you do not transfer your helpdesk to here? Other thing, there is no refund on burst.net. They always say the problem is the other person, never the problem is theirs ....