Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > burst.net Miami DC packet lost
Posted by infracom2005, 11-06-2012, 12:24 AM anyone know what happen?
all their nodes in Miami have packet lost
example
184.22.112.2 or 184.22.112.50
test with just-ping.com
Location Result min. rrt avg. rrt max. rrt IP
Amsterdam2, Netherlands: Packets lost (100%) 184.22.112.2
Florida, U.S.A.: Okay 17.0 17.4 18.6 184.22.112.2
Amsterdam3, Netherlands: Packets lost (100%) 184.22.112.2
New York, U.S.A.: Packets lost (100%) 184.22.112.2
Stockholm, Sweden: Packets lost (90%) 172.4 172.4 172.4 184.22.112.2
Santa Clara, U.S.A.: Packets lost (80%) 79.8 79.9 80.0 184.22.112.2
Vancouver, Canada: Packets lost (80%) 86.2 86.2 86.3 184.22.112.2
London, United Kingdom: Packets lost (70%) 125.5 125.8 126.3 184.22.112.2
Madrid, Spain: Packets lost (100%) 184.22.112.2
Padova, Italy: Okay 149.0 149.6 150.8 184.22.112.2
Singapore, Singapore: Packets lost (90%) 296.3 296.3 296.3 184.22.112.2
Austin, U.S.A.: Packets lost (80%) 35.9 35.9 35.9 184.22.112.2
Cologne, Germany: Packets lost (70%) 123.8 123.9 123.9 184.22.112.2
München, Germany: Okay 149.0 149.3 150.0 184.22.112.2
Amsterdam, Netherlands: Okay 134.5 134.7 135.5 184.22.112.2
Shanghai, China: Packets lost (70%) 304.1 305.0 306.5 184.22.112.2
Hong Kong, China: Packets lost (80%) 272.0 272.2 272.4 184.22.112.2
Melbourne, Australia: Packets lost (100%) 184.22.112.2
Copenhagen, Denmark: Okay 154.4 154.6 155.0 184.22.112.2
Lille, France: Packets lost (80%) 117.6 122.1 126.6 184.22.112.2
San Francisco, U.S.A.: Checkpoint temporarily not available - - - -
Zurich, Switzerland: Packets lost (70%) 139.6 139.8 139.9 184.22.112.2
Mumbai, India: Packets lost (100%) 184.22.112.2
Auckland, New Zealand: Okay 222.6 223.0 224.2 184.22.112.2
Groningen, Netherlands: Packets lost (90%) 138.2 138.2 138.2 184.22.112.2
Antwerp, Belgium: Packets lost (80%) 144.0 144.8 145.6 184.22.112.2
Dublin, Ireland: Packets lost (60%) 124.3 124.5 124.9 184.22.112.2
Kharkov, Ukraine: Packets lost (30%) 180.0 180.6 184.0 184.22.112.2
Manchester, United Kingdom: Packets lost (80%) 165.0 165.5 165.9 184.22.112.2
Vilnius, Lithuania: Packets lost (70%) 145.8 145.9 146.0 184.22.112.2
Bucharest, Romania: Packets lost (70%) 174.9 175.9 177.4 184.22.112.2
Bangkok, Thailand: Packets lost (80%) 285.4 295.0 304.6 184.22.112.2
Kuala Lumpur, Malaysia: Packets lost (80%) 273.9 274.1 274.2 184.22.112.2
Jakarta, Indonesia: Packets lost (90%) 308.0 308.0 308.0 184.22.112.2
Cape Town, South Africa: Packets lost (80%) 282.1 282.2 282.2 184.22.112.2
Glasgow, United Kingdom: Packets lost (10%) 147.8 147.9 148.3 184.22.112.2
Lisbon, Portugal: Packets lost (80%) 185.8 185.9 186.1 184.22.112.2
Chicago, U.S.A.: Okay 89.7 90.0 90.4 184.22.112.2
Dallas, U.S.A.: Packets lost (70%) 32.5 32.6 32.6 184.22.112.2
Istanbul, Turkey: Packets lost (10%) 154.6 154.7 155.0 184.22.112.2
Gdansk, Poland: Okay 154.9 155.3 156.8 184.22.112.2
Cairo, Egypt: Packets lost (70%) 171.0 171.3 171.5 184.22.112.2
Beijing, China: Packets lost (90%) 1,884.9 1,884.9 1,884.9 184.22.112.2
Buenos Aires, Argentina: Packets lost (100%) 184.22.112.2
Belgrade, Serbia: Packets lost (90%) 142.4 142.4 142.4 184.22.112.2
Toronto, Canada: Packets lost (80%) 55.3 55.5 55.6 184.22.112.2
Athens, Greece: Packets lost (90%) 172.0 172.0 172.0 184.22.112.2
Frankfurt, Germany: Packets lost (20%) 178.0 178.3 178.9 184.22.112.2
Sofia, Bulgaria: Okay 173.2 173.5 174.0 184.22.112.2
Budapest, Hungary: Packets lost (70%) 136.6 136.8 136.9 184.22.112.2
Sao Paulo, Brazil: Okay 109.0 109.3 110.0 184.22.112.2
Paris, France: Packets lost (80%) 182.2 182.4 182.5 184.22.112.2
Mumbai, India: Okay 293.1 293.8 296.5 184.22.112.2
New Delhi, India: Packets lost (80%) 284.8 289.7 294.6 184.22.112.2
Chicago, U.S.A.: Packets lost (50%) 57.8 58.0 58.1 184.22.112.2
Bangalore, India: Packets lost (70%) 308.6 308.8 308.9 184.22.112.2
Montreal, Canada: Packets lost (10%) 64.5 64.8 65.6 184.22.112.2
Tokyo, Japan: Packets lost (90%) 178.2 178.2 178.2 184.22.112.2
_____________________________________
184.22.112.50
Location Result min. rrt avg. rrt max. rrt IP
Amsterdam2, Netherlands: Okay 117.1 117.8 123.3 184.22.112.50
Florida, U.S.A.: Okay 17.1 17.1 17.2 184.22.112.50
Amsterdam3, Netherlands: Okay 122.7 122.9 123.0 184.22.112.50
New York, U.S.A.: Packets lost (90%) 63.8 63.8 63.8 184.22.112.50
Stockholm, Sweden: Okay 146.9 147.0 147.1 184.22.112.50
Santa Clara, U.S.A.: Packets lost (90%) 79.8 79.8 79.8 184.22.112.50
Vancouver, Canada: Packets lost (100%) 184.22.112.50
London, United Kingdom: Packets lost (100%) 184.22.112.50
Madrid, Spain: Okay 171.5 172.6 174.4 184.22.112.50
Padova, Italy: Packets lost (100%) 184.22.112.50
Singapore, Singapore: Packets lost (100%) 184.22.112.50
Austin, U.S.A.: Packets lost (90%) 36.6 36.6 36.6 184.22.112.50
Cologne, Germany: Packets lost (90%) 121.0 121.0 121.0 184.22.112.50
München, Germany: Okay 157.2 157.3 157.8 184.22.112.50
Amsterdam, Netherlands: Okay 143.2 143.4 143.5 184.22.112.50
Shanghai, China: Checkpoint temporarily not available - - - -
Hong Kong, China: Packets lost (100%) 184.22.112.50
Melbourne, Australia: Packets lost (100%) 184.22.112.50
Copenhagen, Denmark: Packets lost (100%) 184.22.112.50
Lille, France: Packets lost (90%) 116.6 116.6 116.6 184.22.112.50
San Francisco, U.S.A.: Checkpoint temporarily not available - - - -
Zurich, Switzerland: Packets lost (80%) 139.3 139.6 139.8 184.22.112.50
Mumbai, India: Okay 257.0 261.8 277.6 184.22.112.50
Auckland, New Zealand: Okay 222.8 223.4 226.2 184.22.112.50
Groningen, Netherlands: Okay 110.6 111.0 111.7 184.22.112.50
Antwerp, Belgium: Packets lost (100%) 184.22.112.50
Dublin, Ireland: checking...
Kharkov, Ukraine: Packets lost (100%) 184.22.112.50
Manchester, United Kingdom: checking...
Vilnius, Lithuania: Packets lost (100%) 184.22.112.50
Bucharest, Romania: Okay 156.6 159.8 169.7 184.22.112.50
Bangkok, Thailand: Packets lost (80%) 275.9 275.9 276.0 184.22.112.50
Kuala Lumpur, Malaysia: Packets lost (90%) 261.7 261.7 261.7 184.22.112.50
Jakarta, Indonesia: checking...
Cape Town, South Africa: Packets lost (100%) 184.22.112.50
Glasgow, United Kingdom: Okay 141.3 141.3 141.3 184.22.112.50
Lisbon, Portugal: Packets lost (80%) 143.1 143.3 143.4 184.22.112.50
Chicago, U.S.A.: Packets lost (100%) 184.22.112.50
Dallas, U.S.A.: Packets lost (90%) 32.6 32.6 32.6 184.22.112.50
Istanbul, Turkey: Packets lost (100%) 184.22.112.50
Gdansk, Poland: Okay 149.7 150.3 153.7 184.22.112.50
Cairo, Egypt: Packets lost (90%) 174.8 174.8 174.8 184.22.112.50
Beijing, China: Checkpoint temporarily not available - - - -
Buenos Aires, Argentina: Packets lost (100%) 184.22.112.50
Belgrade, Serbia: Packets lost (90%) 141.9 141.9 141.9 184.22.112.50
Toronto, Canada: checking...
Athens, Greece: Packets lost (100%) 184.22.112.50
Frankfurt, Germany: Okay 136.6 136.9 137.1 184.22.112.50
Sofia, Bulgaria: Packets lost (100%) 184.22.112.50
Budapest, Hungary: Packets lost (90%) 142.0 142.0 142.0 184.22.112.50
Sao Paulo, Brazil: Okay 108.5 108.7 108.9 184.22.112.50
Paris, France: Packets lost (100%) 184.22.112.50
Mumbai, India: Okay 289.5 289.8 291.4 184.22.112.50
New Delhi, India: checking...
Chicago, U.S.A.: Packets lost (100%) 184.22.112.50
Bangalore, India: Okay 295.1 296.6 299.6 184.22.112.50
Montreal, Canada: Packets lost (100%) 184.22.112.50
Tokyo, Japan: Packets lost (70%) 179.3 185.0 188.4 184.22.112.50
Posted by BurstNET CSR, 11-06-2012, 12:48 AM Hello.
I apologize for the inconvenience this issue has caused. Our staff is currently working diligently to resolve this matter as soon as possible. Please submit a ticket if you are experiencing any packet loss and our technicians will update you as soon as this is remedied.
Posted by BurstNET CSR, 11-06-2012, 01:21 AM Our technicians are still closely monitoring each node in Miami, however it seems this has been resolved.
If anyone experiences any connection issues or packet loss, we urge you to submit a ticket via our support system.
Thank you.
Posted by infracom2005, 11-18-2012, 08:05 AM again, packet lost in all vps of Miami DC
http://just-ping.com/index.php?vh=18...887&vhost=_&c=
Location Result min. rrt avg. rrt max. rrt IP
Amsterdam2, Netherlands: Okay 126.1 126.4 126.6 184.22.112.2
Florida, U.S.A.: Packets lost (20%) 15.2 15.3 15.3 184.22.112.2
Amsterdam3, Netherlands: Okay 120.1 120.4 121.1 184.22.112.2
Sydney, Australia: Okay 246.4 247.3 248.6 184.22.112.2
New York, U.S.A.: Okay 45.4 45.5 45.5 184.22.112.2
Stockholm, Sweden: Packets lost (10%) 150.9 151.2 151.4 184.22.112.2
Santa Clara, U.S.A.: Packets lost (20%) 76.3 76.5 76.7 184.22.112.2
Vancouver, Canada: Okay 82.2 82.2 82.5 184.22.112.2
London, United Kingdom: Packets lost (30%) 123.8 124.2 124.5 184.22.112.2
Madrid, Spain: Okay 143.1 143.6 146.3 184.22.112.2
Padova, Italy: Okay 156.6 156.8 157.3 184.22.112.2
Singapore, Singapore: Okay 262.1 279.8 369.7 184.22.112.2
Austin, U.S.A.: Okay 34.2 34.2 34.3 184.22.112.2
Cologne, Germany: Okay 122.0 122.1 122.2 184.22.112.2
München, Germany: Packets lost (20%) 155.6 156.0 156.4 184.22.112.2
Amsterdam, Netherlands: Packets lost (40%) 141.2 141.5 141.6 184.22.112.2
Shanghai, China: Okay 277.9 284.6 290.8 184.22.112.2
Hong Kong, China: Okay 327.2 327.9 328.4 184.22.112.2
Melbourne, Australia: Okay 265.7 265.8 266.4 184.22.112.2
Copenhagen, Denmark: Packets lost (10%) 154.4 154.5 154.6 184.22.112.2
Lille, France: Packets lost (30%) 113.3 119.3 125.0 184.22.112.2
San Francisco, U.S.A.: Checkpoint temporarily not available - - - -
Zurich, Switzerland: Okay 139.3 139.6 139.8 184.22.112.2
Mumbai, India: Packets lost (40%) 252.5 254.9 256.7 184.22.112.2
Auckland, New Zealand: Okay 222.6 223.0 223.4 184.22.112.2
Groningen, Netherlands: Packets lost (50%) 116.7 117.1 117.7 184.22.112.2
Antwerp, Belgium: Okay 122.8 123.0 123.3 184.22.112.2
Dublin, Ireland: Packets lost (40%) 120.4 120.5 120.6 184.22.112.2
Kharkov, Ukraine: Okay 236.0 236.4 240.0 184.22.112.2
Manchester, United Kingdom: Okay 119.8 120.0 120.2 184.22.112.2
Vilnius, Lithuania: Okay 144.5 144.7 145.0 184.22.112.2
Bucharest, Romania: Okay 154.1 155.1 157.0 184.22.112.2
Bangkok, Thailand: Okay 269.0 274.0 293.0 184.22.112.2
Kuala Lumpur, Malaysia: Packets lost (20%) 275.2 275.5 276.4 184.22.112.2
Jakarta, Indonesia: Packets lost (10%) 291.7 297.8 303.6 184.22.112.2
Cape Town, South Africa: Okay 260.5 260.6 260.8 184.22.112.2
Glasgow, United Kingdom: Okay 113.5 113.5 113.6 184.22.112.2
Lisbon, Portugal: Okay 159.8 160.4 160.9 184.22.112.2
Chicago, U.S.A.: Okay 65.2 65.7 67.0 184.22.112.2
Dallas, U.S.A.: Okay 31.6 31.7 31.8 184.22.112.2
Istanbul, Turkey: Packets lost (40%) 155.3 156.7 160.2 184.22.112.2
Gdansk, Poland: Okay 155.0 155.4 156.1 184.22.112.2
Cairo, Egypt: Packets lost (20%) 187.5 197.4 226.1 184.22.112.2
Buenos Aires, Argentina: Okay 157.9 158.0 158.2 184.22.112.2
Belgrade, Serbia: Packets lost (50%) 141.0 141.0 141.1 184.22.112.2
Toronto, Canada: Okay 53.6 53.6 53.7 184.22.112.2
Athens, Greece: Okay 179.4 179.5 180.1 184.22.112.2
Frankfurt, Germany: Okay 131.3 131.7 132.2 184.22.112.2
Sofia, Bulgaria: Okay 223.0 223.9 225.5 184.22.112.2
Budapest, Hungary: Packets lost (30%) 135.0 139.9 168.1 184.22.112.2
Sao Paulo, Brazil: Okay 108.4 108.5 108.7 184.22.112.2
Paris, France: Okay 153.4 153.6 153.7 184.22.112.2
Mumbai, India: Okay 292.3 292.4 292.6 184.22.112.2
New Delhi, India: Okay 276.6 276.7 276.9 184.22.112.2
Chicago, U.S.A.: Okay 53.8 54.7 58.5 184.22.112.2
Bangalore, India: Okay 277.6 278.0 278.6 184.22.112.2
Tokyo, Japan: Okay 173.7 173.9 174.2 184.22.112.2
Posted by BurstNET, 11-18-2012, 09:04 PM Should be fine now.
There was an abusive user flooding the VPS switching equipment with a huge amount of traffic.
Posting this to WHT does not get you anywhere or accomplish anything.
WHT is NOT our support system.
Please follow proper support procedures and contact us directly by appropriate means.
.
.
Posted by infracom2005, 11-18-2012, 11:41 PM again, packet lost
nobody reply tickets
Posted by BurstNET CS, 11-19-2012, 09:25 AM I tried to search for a ticket, based on the information provided here, and found no matches. Please provide your ticket number(s) so that I can ensure we have received your request(s).
Also, for future reference, you should provide traceroutes -- including source IPs -- with any network troubleshooting requests. Results from "just-ping.com" show limited information.
Posted by infracom2005, 11-19-2012, 10:22 AM one more time packet lost
more than 30 hs with this problem and nobody fix it
ticket 3456404
Posted by BurstNET CS, 11-19-2012, 10:55 AM As our staff informed you yesterday in that ticket, there appeared to be an issue outside of our network that was impacting your connections. This was not something that could have been fixed by our staff.
Our technicians will be taking another look but, if problems are still occurring, you should provide an updated traceroute in the ticket.
Posted by infracom2005, 11-19-2012, 10:58 AM my connection? you have packet lost in
ARGENTINA
SPAIN
ENGLAND
GERMANY
FRANCE
DENMARK
IRELAND
BELGIUM
MALAYSIA
I SENT THE TRACERT 30 hours ago in the ticket
ocation Result min. rrt avg. rrt max. rrt IP
Amsterdam2, Netherlands: Okay 125.3 125.8 126.4 184.22.121.118
Florida, U.S.A.: Packets lost (40%) 15.4 15.5 15.5 184.22.121.118
Amsterdam3, Netherlands: Okay 119.1 119.5 120.5 184.22.121.118
Sydney, Australia: Okay 245.5 246.0 246.9 184.22.121.118
New York, U.S.A.: Packets lost (20%) 60.4 60.6 60.8 184.22.121.118
Stockholm, Sweden: Packets lost (40%) 148.7 148.8 148.9 184.22.121.118
Santa Clara, U.S.A.: Okay 77.9 78.1 78.7 184.22.121.118
Vancouver, Canada: Okay 85.9 88.2 93.7 184.22.121.118
London, United Kingdom: Packets lost (20%) 123.7 124.0 124.4 184.22.121.118
Madrid, Spain: Packets lost (50%) 162.0 162.6 164.5 184.22.121.118
Padova, Italy: Okay 156.7 157.0 157.5 184.22.121.118
Singapore, Singapore: Okay 255.4 262.2 267.7 184.22.121.118
Austin, U.S.A.: Okay 34.7 34.7 34.7 184.22.121.118
Cologne, Germany: Okay 121.1 121.8 122.9 184.22.121.118
München, Germany: Packets lost (20%) 143.7 144.2 145.6 184.22.121.118
Amsterdam, Netherlands: Packets lost (40%) 137.4 137.7 138.7 184.22.121.118
Shanghai, China: Checkpoint temporarily not available - - - -
Hong Kong, China: Okay 370.6 371.5 372.7 184.22.121.118
Melbourne, Australia: Okay 265.5 265.7 266.0 184.22.121.118
Copenhagen, Denmark: Packets lost (30%) 154.5 154.7 154.8 184.22.121.118
Lille, France: Packets lost (60%) 122.8 126.7 133.8 184.22.121.118
San Francisco, U.S.A.: Checkpoint temporarily not available - - - -
Zurich, Switzerland: Packets lost (30%) 155.7 157.4 158.9 184.22.121.118
Mumbai, India: Packets lost (50%) 262.7 264.2 265.6 184.22.121.118
Auckland, New Zealand: Okay 222.2 222.4 222.6 184.22.121.118
Groningen, Netherlands: Packets lost (30%) 116.7 117.0 117.7 184.22.121.118
Antwerp, Belgium: Okay 121.7 122.0 122.7 184.22.121.118
Dublin, Ireland: Packets lost (10%) 117.3 117.7 118.9 184.22.121.118
Kharkov, Ukraine: Okay 180.0 180.4 184.0 184.22.121.118
Manchester, United Kingdom: Packets lost (40%) 137.7 141.0 148.5 184.22.121.118
Vilnius, Lithuania: Okay 143.5 143.9 144.3 184.22.121.118
Bucharest, Romania: Okay 158.3 160.1 170.6 184.22.121.118
Bangkok, Thailand: Okay 350.0 350.4 351.1 184.22.121.118
Kuala Lumpur, Malaysia: Packets lost (40%) 275.6 276.2 276.8 184.22.121.118
Jakarta, Indonesia: Packets lost (40%) 282.3 290.2 296.0 184.22.121.118
Cape Town, South Africa: Okay 260.1 260.4 260.8 184.22.121.118
Glasgow, United Kingdom: Okay 118.5 118.6 118.8 184.22.121.118
Lisbon, Portugal: Okay 141.7 142.4 142.7 184.22.121.118
Chicago, U.S.A.: Okay 65.4 65.9 67.3 184.22.121.118
Dallas, U.S.A.: Okay 31.7 31.9 32.1 184.22.121.118
Istanbul, Turkey: Packets lost (50%) 153.4 154.0 155.2 184.22.121.118
Gdansk, Poland: Okay 154.1 154.5 154.8 184.22.121.118
Cairo, Egypt: Packets lost (40%) 179.9 180.5 181.6 184.22.121.118
Buenos Aires, Argentina: Okay 146.2 147.3 149.7 184.22.121.118
Belgrade, Serbia: Packets lost (50%) 141.3 142.0 142.8 184.22.121.118
Toronto, Canada: Okay 51.5 51.6 51.7 184.22.121.118
Athens, Greece: Okay 178.9 180.0 181.8 184.22.121.118
Frankfurt, Germany: Okay 130.9 131.2 131.6 184.22.121.118
Sofia, Bulgaria: Okay 160.4 160.8 161.2 184.22.121.118
Budapest, Hungary: Packets lost (30%) 141.4 141.5 141.7 184.22.121.118
Sao Paulo, Brazil: Okay 108.4 108.6 108.8 184.22.121.118
Paris, France: Okay 207.2 207.7 208.3 184.22.121.118
Mumbai, India: Okay 292.3 293.0 295.2 184.22.121.118
New Delhi, India: Okay 285.6 285.6 285.8 184.22.121.118
Chicago, U.S.A.: Okay 52.4 52.6 52.7 184.22.121.118
Bangalore, India: Okay 277.6 278.2 278.6 184.22.121.118
Tokyo, Japan: Packets lost (40%) 206.6 211.2 216.3 184.22.121.118
Posted by BurstNET CS, 11-19-2012, 11:34 AM It is entirely possible for problems outside of our network to impact connections from many geographic locations. It all depends on the hop(s) most affected by the issue.
Again, this is not our helpdesk. Our staff with continue to correspond with you in the ticket.
Posted by infracom2005, 11-19-2012, 11:37 AM so, if the problem is external, why one tech reply
"It looks like there may be an issues with PCCWs network that is causing connection issues to our Miami location, such as the packet loss you're describing"
and then you reply
"There was an abusive user flooding the VPS switching equipment with a huge amount of traffic."
Posted by HostHatch_AR, 11-19-2012, 11:47 AM They could be two different issues. You should contact them through their support channels, not WHT. They have told you a few times, but you don't seem to want to do it.Quote:
Originally Posted by infracom2005so, if the problem is external, why one tech reply
"It looks like there may be an issues with PCCWs network that is causing connection issues to our Miami location, such as the packet loss you're describing"
and then you reply
"There was an abusive user flooding the VPS switching equipment with a huge amount of traffic."
Posted by BurstNET CS, 11-19-2012, 11:48 AM From the look of it, you were impacted by two entirely separate incidents.
In your ticket, you included 5 different IPs, spanning 2 different datacenters/locations. Not all of those IPs were impacted by either of the incidents we detected. In some cases, we could not replicate the issue you reported.
I will not be addressing any additional responses in this thread. Please direct all future correspondence with our staff in the ticket system.
Posted by infracom2005, 11-19-2012, 11:48 AM i sent a ticket 40 hours ago and they didnt replyQuote:
Originally Posted by abdullahrafiqThey could be two different issues. You should contact them through their support channels, not WHT. They have told you a few times, but you don't seem to want to do it.
Posted by F-DNS, 11-19-2012, 12:51 PM No they don't. It's the network(s) just-ping uses from those locations that's causing the problem. BurstNET don't have any control over that.Quote:
Originally Posted by infracom2005you have packet lost in
ARGENTINA
SPAIN
ENGLAND
GERMANY
FRANCE
DENMARK
IRELAND
BELGIUM
MALAYSIA
I think you'll find that one of the most likely issues is with Highwind's network around New York. Just-Ping's test node in England is on AS34270 and uses Highwinds to cross the Atlantic. Everything is fine until it gets to 1-3.r1.ny.hwng.net [69.16.191.49] (Highwinds New York) which is also where other routes to BurstNET Miami jump from Cogent to Highwinds, so you see the same problem especially from Europe (and a lot of your list above is from European connections).
Tests from Europe to BurstNET Scranton don't show the same issue because the route stays on Cogent to Philly and misses out Highwinds completely.
Instead of trying to lump all the blame onto BurstNET (who have no control over the external networks bringing traffic towards them) understand that this is the result of various external issues outside of their control (like PCCWBTN which got fixed within a few hours). A lot of traffic from the west of BurstNET Miami comes in via PCCWBTN in Dallas Fort Worth and is now fine.
So they fixed the PCCWBTN issue (or PCCWBTN did).
They killed an abusive user on one of the nodes you're on.
There's still a problem (since last Thursday) with Highwinds over which BurstNET have zero control - All they can do is report it to Highwinds who aren't exactly the fastest people in the world at fixing things
Add to Favourites Print this Article