Today (19:28 Spain hour), we have a speed problem for connect with our burst server. All services (except HTTP, excelent speed) go very slow.

There are 10 minutes, the conect with our server is down. Not telnet, not ftp, not email, not http...

There are any more with this problem?
Any person can inform me what is happenig?

Excuse me for me English and thank you.

Now, only HTTP service it´s running, but very very slow.

I think there is a Sprint problem accross the east coast (so im told) that affect Burst I think...

I tried accessing the Cpanel site earlier and noticed it was extremely slow...

If burst write in your page:

Verizon™ OC192 Fiber (RBOC/TELCO)
CTSI™ OC192 Fiber - 2nd Qtr 2002
PPL Telcom™ 2GBPS Fiber - 4th Qtr 2002
Redundant BGP Routing on Cisco™ 7206VXR
DS3 Connectivity thru Sprint™, AT&T™, & MCI™
Sprint™ OC3 Connectivity - 2nd Qtr 2002

and Sprint is down.... where is AT&T?, and MCI?.

Text in Burst page (About your data center):
The Network Operations Center is connected via a OC192 fiber connection to Verizon™ (Formerly Bell Atlantic PA). BurstNET™ utilizes redundant DS3 (45mbps) connections thru Sprint™ (http://www.sprint.com), AT&T™ (http://www.att.com), and MCI/UUNet/Worldcom™ (http://www.worldcom.com).

Tipical Spanish expression: "Que coño pasa?"

I think the problem has returned...

Trying our server at burst:

root@web2 [/home]# ping 66.96.208.10
PING 66.96.208.10 (66.96.208.10) from 216.12.211.202 : 56(84) bytes of data.

--- 66.96.208.10 ping statistics ---
31 packets transmitted, 0 packets received, 100% packet loss


Trying burst itself:

root@web2 [/home]# ping burst.net
PING burst.net (66.96.192.201) from 216.12.211.202 : 56(84) bytes of data.
64 bytes from burst.net (66.96.192.201): icmp_seq=0 ttl=241 time=88.409 msec
64 bytes from burst.net (66.96.192.201): icmp_seq=1 ttl=241 time=89.927 msec
64 bytes from burst.net (66.96.192.201): icmp_seq=2 ttl=241 time=89.941 msec
64 bytes from burst.net (66.96.192.201): icmp_seq=3 ttl=241 time=89.949 msec
64 bytes from burst.net (66.96.192.201): icmp_seq=4 ttl=241 time=89.953 msec

--- burst.net ping statistics ---
30 packets transmitted, 6 packets received, 80% packet loss
round-trip min/avg/max/mdev = 88.409/91.351/99.930/3.888 ms


Does anyone know what's going on??

Take care,

Brian

Then.
what is going on is that YOUR server cannot be reached.
I ran a traceroute on both IPs and it doesn't look like a router problem; so either your server is down or a switch is...

-Chris,

Originally posted by cyansmoker
Then.
what is going on is that YOUR server cannot be reached.
I ran a traceroute on both IPs and it doesn't look like a router problem; so either your server is down or a switch is...

-Chris,

Nope. It was the network - my box has been running the whole time. I can get to the box now, the network seems back up. (Take a look at my post again, and note the 80% packet loss to burst.net)

No word on what the problem was yet...

Take care,

Brian

This is even worse: http://www.webhostingtalk.com/showthread.php?s=&threadid=44706&highlight=burst.net