| Posted by Arsalan, 09-12-2005, 03:59 PM | |
It seems that burst.net has been down for about 60 min now ? I cant seem to reach any of their servers....
|
| Posted by mpjetta, 09-12-2005, 04:04 PM | |
It seems to be their DNS servers are down.
Our colo rack is up and online after a 5-10 minute downtime around 2pm EST. Although a few things are messed up b/c of the lack of DNS queries resolving.
|
| Posted by Arsalan, 09-12-2005, 04:06 PM | |
From what I can see, their network has packet loss as well;
http://www.space.net/cgi-bin/webtrac....96.193.2&ns=y
traceroute to 66.96.193.2 (66.96.193.2), 30 hops max, 38 byte packets
1 Cisco-M-XI-Vlan8.Space.Net (193.149.44.157) 0.947 ms 1.063 ms 0.948 ms
2 Cisco-M-XII-GE0-1.Space.Net (193.149.44.115) 0.964 ms 0.927 ms 0.846 ms
3 Cisco-M-Fe0-1.Space.Net (195.30.3.209) 2.912 ms 1.219 ms 1.244 ms
4 Cisco-INXS-P6-0.Space.Net (195.30.3.205) 1.198 ms 1.648 ms 1.706 ms
5 fe0-0.INXS1.de.gatel.net (194.59.190.33) 2.115 ms 1.587 ms 1.513 ms
6 p14-0.core01.fra03.atlas.cogentco.com (130.117.1.198) 8.084 ms 8.574 ms 7.248 ms
7 p15-0.core02.par02.atlas.cogentco.com (130.117.0.18) 175.715 ms 200.780 ms 214.266 ms
8 p12-0.core01.par01.atlas.cogentco.com (130.117.1.230) 19.445 ms 18.698 ms 19.237 ms
9 p14-0.core02.dca01.atlas.cogentco.com (66.28.4.206) 98.900 ms 168.052 ms 98.911 ms
10 p15-0.core01.dca01.atlas.cogentco.com (66.28.4.21) 99.365 ms 99.077 ms 98.916 ms
11 p4-0.core01.phl01.atlas.cogentco.com (66.28.4.18) 102.303 ms 102.822 ms 103.985 ms
12 g0-1.na22.b003003-1.phl01.atlas.cogentco.com (66.250.8.86) 103.127 ms 103.241 ms 102.901 ms
13 hostnoc.demarc.cogentco.com (38.112.240.34) 102.939 ms 104.540 ms 102.563 ms
14 ge1-oc48-1-0-ctsi.rtr0.scr1.hostnoc.net (66.197.191.1) 107.035 ms 107.207 ms 107.217 ms
15 * * *
|
| Posted by RealRoxy, 09-12-2005, 04:09 PM | |
Same here; down for an hour at least. Are you able to contact someone there?
|
| Posted by Arsalan, 09-12-2005, 04:10 PM | |
gona try AOL, no responce to tickets yet..
|
| Posted by Cirtex, 09-12-2005, 04:12 PM | |
We got response and was told there were some power outages in few switches, ours are up now though.
|
| Posted by Arsalan, 09-12-2005, 04:13 PM | |
Got info over AOL that this should not last more then 30 sec... lets hope its fixed soon..
|
| Posted by AlexAT, 09-12-2005, 04:38 PM | |
I can't acces one of my servers there for near a hour.
Their Help Desk and Forums are not accessible also.
Anybody knows what happen?
|
| Posted by Arsalan, 09-12-2005, 04:48 PM | |
Taking a bit more time then I expected.......
|
| Posted by ceridius, 09-12-2005, 04:49 PM | |
I am also unable to access the site.
|
| Posted by bloodyman, 09-12-2005, 04:51 PM | |
Do you have any alternative configuration for /etc/resolv.conf?
BurstNet name servers not respond, so e-mail on my server doesn't work. I have to setup any additional nameserver entries in /etc/resolv.com, help
|
| Posted by VapoRub, 09-12-2005, 04:56 PM | |
Nocster is up.
|
| Posted by AQORN-Adam, 09-12-2005, 04:57 PM | |
Apparently it is only a portion of their network. If it was the whole thing, the hyperspin.com external monitor would show downtime. And apparently it is the same segment that went down on 8/17 since that one doesn't register either.
http://www.hyperspin.com/ranking.php?type=3
Curious what the problem is. (Hyperspin is so cool )
Last edited by AQORN-Adam; 09-12-2005 at 05:03 PM.
|
| Posted by sirius, 09-12-2005, 04:58 PM | |
Probably best to post this in the correct forum....
http://www.webhostingtalk.com/forumd...php?forumid=59
|
| Posted by RealRoxy, 09-12-2005, 05:00 PM | |
Any updates? BurstNET @ AIM ignores my inquiries.
|
| Posted by AlexAT, 09-12-2005, 05:01 PM | |
Yes, sorry.
|
| Posted by djblamire, 09-12-2005, 05:02 PM | |
Problems here still
Daniel
|
| Posted by ceridius, 09-12-2005, 05:02 PM | |
looks like a DNS issue to me , when I did a tracert to an IP on their network it went through no problem.
|
| Posted by AlexAT, 09-12-2005, 05:05 PM | |
One of my servers still down (near 1 hour).
Their support is down (that is why you Arsalan don't get answer for ticket), forums are down also.
bloodyman, seems there is nothing with your config, it is network outage issue.
|
| Posted by djblamire, 09-12-2005, 05:05 PM | |
I tried a tracert to an IP, and get stuck
12 90 ms 91 ms 90 ms 4.78.144.6
13 * * * Request timed out.
BTW. I've been unable to access for nearly 2hours 30 mins...
Daniel
|
| Posted by AlexAT, 09-12-2005, 05:06 PM | |
HiVelocity, seems it is not DNS issue but rather different network parts issue - since I have 2 servers with them and 1 is down but another one is up all this time.
|
| Posted by RealRoxy, 09-12-2005, 05:08 PM | |
seems restored now... total downtime 2 hrs min.
|
| Posted by RealRoxy, 09-12-2005, 05:12 PM | |
Great support btw... "BurstNET signed off at 16:58:14." (AIM)
|
| Posted by GordonH, 09-12-2005, 05:13 PM | |
That would be their connection going down.
|
| Posted by AlexAT, 09-12-2005, 05:15 PM | |
Still down
|
| Posted by ceridius, 09-12-2005, 05:16 PM | |
maybe they are getting hit with a DDOS attack
|
| Posted by AQORN-Adam, 09-12-2005, 05:23 PM | |
That seems more likely.
|
| Posted by bhaputi, 09-12-2005, 05:41 PM | |
Nope - actually, that was when I rebooted our office firewall to clear up some dead connections.
|
| Posted by bhaputi, 09-12-2005, 05:43 PM | |
http://forums.burst.net/showthread.p...2862#post22862
|
| Posted by bhaputi, 09-12-2005, 05:45 PM | |
We did not experience any sort of DDoS during this time. It was basically a case of cascading causes - most people who said they were down were actually up and running, but exclusively using BurstNET nameservers, which were down for a good chunk of the afternoon unfortunately.
|
| Posted by RealRoxy, 09-12-2005, 05:52 PM | |
Most but not all I suppose? my IPs didn't work during downtime.
|
| Posted by AlexAT, 09-12-2005, 05:52 PM | |
Thank you, Dan.
However I'm not sure I understand nameserver issue. I can't ping my main server IP at all - is this even can be nameserver issue?
|
| Posted by Arsalan, 09-12-2005, 06:30 PM | |
There was a core swith involved mostprobably..
|
| Posted by bhaputi, 09-13-2005, 10:11 AM | |
We had some individual machines that also had lingering problems. Unfortunately, until we got our nameservers squared away, our monitoring system could not point them out to us.
|
| Posted by AlexAT, 09-13-2005, 10:30 AM | |
Thank you!
As it turned out additional downtime of my server was initiated because of broken (non/bootable) HDD.
Singular coincidences happens!
Your support was kindly helpfull and even copy all my broken HDD content to the new one and my server online w/o any data loss!
One who at least 1 time prepare new machine because of broken HDD knows what I'm feeling right now
Thanks God!
And thank you for your business.
|
| Posted by Arsalan, 09-13-2005, 12:45 PM | |
I am glad that this issue was resolved well in time. I must say their support is superb!
|
|
 Add to Favourites
 Print this Article
|
