Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > burst.net Miami offline one more time
burst.net Miami offline one more time
| Posted by infracom2005, 02-24-2012, 08:18 AM |
my 2 vps of burst.net in Miami fail one one more time
anyone know what happen? Miami location is a dissaster, every week fail
it was tested with
http://just-ping.com/index.php?vh=18....136&c=&s=ping!
ocation Result min. rrt avg. rrt max. rrt IP
Singapore, Singapore: Packets lost (100%) 184.22.122.136
Amsterdam2, Netherlands: Packets lost (100%) 184.22.122.136
Florida, U.S.A.: Packets lost (100%) 184.22.122.136
Amsterdam3, Netherlands: Packets lost (100%) 184.22.122.136
Hong Kong, China: Packets lost (100%) 184.22.122.136
Sydney, Australia: Packets lost (100%) 184.22.122.136 |
| Posted by Aquamarina, 02-24-2012, 08:53 AM |
|
I second that... Miami sucks... Horatio plz help us! |
| Posted by jackpx, 02-24-2012, 09:35 AM |
|
yes ... 10 days, uptime: 97%.7 |
| Posted by infracom2005, 02-24-2012, 09:38 AM |
|
back up, but this network fail every week |
| Posted by jackpx, 02-24-2012, 09:45 AM |
|
still down |
| Posted by Aquamarina, 02-24-2012, 09:56 AM |
|
I'm up again... I've chosen Miami for this server cause Scranton had some issues in the past, but now I'm thinking of moving to Scranton again, or maybe Manchester in the UK... |
| Posted by F-DNS, 02-24-2012, 10:22 AM |
|
Don't be too quick to rush to judgement and say it's BurstNET exclusively - We're seeing another provider in Miami with a flappy connection too. It may be a wider issue. |
| Posted by BurstNET, 02-24-2012, 11:39 AM |
Colohouse facility just lost power this morning.
Service was restored some time ago already.
.
. |
| Posted by infracom2005, 03-06-2012, 04:35 PM |
one more time, burstnet Miami offline
1 75.125.232.57 (75.125.232.57) 0.736 ms 0.560 ms 0.336 ms
2 te1-4.dsr02.hstntx1.networklayer.com (207.218.245.5) 0.651 ms 0.364 ms 0.365 ms
3 po16.dsr01.hstntx2.networklayer.com (70.87.253.101) 0.634 ms 0.775 ms 0.799 ms
4 ae17.bbr02.sr02.hou02.networklayer.com (173.192.18.238) 0.804 ms 0.753 ms 0.811 ms
5 ae3.bbr01.eq01.dal03.networklayer.com (173.192.18.218) 5.824 ms ae3.bbr02.eq01.dal03.networklayer.com (173.192.18.220) 10.263 ms 10.475 ms
6 ae1.bbr01.tl01.atl01.networklayer.com (173.192.18.135) 31.898 ms 31.983 ms 31.894 ms
7 ae1.bbr01.tl01.atl01.networklayer.com (173.192.18.135) 31.151 ms 30.978 ms 29.441 ms
8 * * *
9 * * *
10 * * *
time out |
| Posted by BurstNET, 03-06-2012, 04:39 PM |
Quote:
|
Originally Posted by infracom2005
one more time, burstnet Miami offline
1 75.125.232.57 (75.125.232.57) 0.736 ms 0.560 ms 0.336 ms
2 te1-4.dsr02.hstntx1.networklayer.com (207.218.245.5) 0.651 ms 0.364 ms 0.365 ms
3 po16.dsr01.hstntx2.networklayer.com (70.87.253.101) 0.634 ms 0.775 ms 0.799 ms
4 ae17.bbr02.sr02.hou02.networklayer.com (173.192.18.238) 0.804 ms 0.753 ms 0.811 ms
5 ae3.bbr01.eq01.dal03.networklayer.com (173.192.18.218) 5.824 ms ae3.bbr02.eq01.dal03.networklayer.com (173.192.18.220) 10.263 ms 10.475 ms
6 ae1.bbr01.tl01.atl01.networklayer.com (173.192.18.135) 31.898 ms 31.983 ms 31.894 ms
7 ae1.bbr01.tl01.atl01.networklayer.com (173.192.18.135) 31.151 ms 30.978 ms 29.441 ms
8 * * *
9 * * *
10 * * *
time out
|
Untrue...we were not offline.
Your information is inaccurate/false.
Most likely this was an issue with a specific node, or possibly even unique to your or your ISP.
Heck, even your traceroute info is useless, as it shows nothing about our network in the traceroute whatsoever.
That traceroute could have been to anywhere.
.
. |
| Posted by infracom2005, 03-06-2012, 04:41 PM |
it is NOT FALSE, servers were offline. . I have 2 vps in differents node both fails. It was tested with just-ping.com
Now back up and you reply
"Hello,
Our engineering team is performing maintenance on our Miami data decent, the connection should be restored shortly.
Thank You,
Al K.
Technical Support" |
| Posted by dooogen, 03-06-2012, 04:43 PM |
|
It was definitely down. I can confirm that. |
| Posted by Smeagle, 03-06-2012, 05:42 PM |
I've been watching them closely lately and things are indeed not going very well in their Miami facility. I used to like their services when I had a VPS with them, but it seems like they went downhill over the past few months.
I guess this was some sort of planned outage as that old routing issue have been fixed since it came back up (picture #3), even though I have no idea why they would do that during the daytime. |
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
