Portal Home > Knowledgebase > Articles Database > Burst.net - 3/16/04
Burst.net - 3/16/04
Posted by RealRoxy, 03-16-2004, 05:08 AM |
Well, I'm not an expert on connectivity, but the following online tools still show packet loss up to 60%, "no response", "timed out" etc. on my 66.197.143.40 from various locations.
ops.sprint-canada.net
centralops.net/co
network-tools.com
dnsstuff.com
|
Posted by bhaputi, 03-16-2004, 05:20 AM |
All earlier problems with Verio are fixed, and have been for 8 hours now. We are currently seeing some Cogent related problems, but I shut off their connection to us, so it should no longer be service affecting. If it is, the best thing to do is to open a ticket within our system including full traceroutes.
|
Posted by bhaputi, 03-16-2004, 06:07 AM |
All of our connections are currently fully operational.
|
Posted by aleck, 03-16-2004, 06:45 AM |
yep, i had it up & down from ev1 server, but nothing deadly, haven't even switched the traffic.
|
Posted by Spider210, 03-16-2004, 07:57 PM |
Getting major packetloss and high pings anyone else?
|
Posted by Dacsoft, 03-16-2004, 07:58 PM |
Dan,
There is some sort of problem. Pings to your site even time out.
|
Posted by Spider210, 03-16-2004, 07:59 PM |
wow awesome!
|
Posted by Spider210, 03-16-2004, 08:02 PM |
its packetloss city ... yet again
|
Posted by mainarea, 03-16-2004, 08:05 PM |
Yes, something is going crazy. No details yet...
- Matt
|
Posted by mainarea, 03-16-2004, 08:13 PM |
Fixed at around 7:10. Awaiting a status report, not sure if this affected all lines or the cause.
- Matt
|
Posted by Spider210, 03-16-2004, 08:35 PM |
here we go again...
|
Posted by Flammable, 03-16-2004, 08:43 PM |
Down from the UK. Extremely slow speeds, but still getting there...
|
Posted by isalh, 03-16-2004, 08:43 PM |
It's down from here
Problems are back...
|
Posted by phactor, 03-16-2004, 08:43 PM |
down here!
|
Posted by smartboyinuk, 03-16-2004, 08:44 PM |
down from UK - totally down
|
Posted by Flammable, 03-16-2004, 08:46 PM |
Time (US/Eastern) Checked From Result Size Secs
03/16/2004 19:45:33 Frankfurt GERMANY Unable to resolve na N/A 20.06
03/16/2004 19:45:22 Los Angeles USA Unable to resolve na N/A 10.04
03/16/2004 19:45:32 Detroit USA Unable to resolve na N/A 20.06
|
Posted by bizantium, 03-16-2004, 08:48 PM |
Down
|
Posted by Cirtex, 03-16-2004, 08:49 PM |
Down
|
Posted by Xshare, 03-16-2004, 08:50 PM |
Down from here as well... the problems with these guys just never end do they??
|
Posted by Clark2, 03-16-2004, 08:57 PM |
C:\Documents and Settings\Administrator>ping burst.net
Pinging burst.net [66.96.192.201] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 66.96.192.201: bytes=32 time=641ms TTL=48
Reply from 66.96.192.201: bytes=32 time=641ms TTL=48
Ping statistics for 66.96.192.201:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 641ms, Maximum = 641ms, Average = 320ms
C:\Documents and Settings\Administrator>
|
Posted by IceCell, 03-16-2004, 08:57 PM |
not down for me but.. lots of packet - loss:
Tracing route to nocster.com [66.96.192.220]
over a maximum of 30 hops:
1 14 ms 69 ms 27 ms 10.225.160.1
2 * * * Request timed out.
3 18 ms 15 ms 15 ms so-7-0.ipcolo1.LosAngeles1.Level3.net [63.208.23
1.109]
4 16 ms 37 ms 19 ms so-3-2-0.bbr1.LosAngeles1.Level3.net [4.68.113.1
53]
5 17 ms 17 ms 18 ms so-10-0.core1.LosAngeles1.Level3.net [4.68.113.1
66]
6 17 ms 16 ms 49 ms p16-1-1-3.r21.lsanca01.us.bb.verio.net [129.250.
9.33]
7 25 ms 40 ms 31 ms p16-1-1-0.r21.snjsca04.us.bb.verio.net [129.250.
2.187]
8 26 ms 25 ms 27 ms xe-0-2-0.r20.snjsca04.us.bb.verio.net [129.250.2
.72]
9 16 ms 51 ms 16 ms so-10-0.core1.LosAngeles1.Level3.net [4.68.113.1
66]
10 17 ms 16 ms 39 ms so-4-1-0.bbr1.LosAngeles1.Level3.net [4.68.113.1
65]
11 17 ms 17 ms 17 ms so-10-0.core1.LosAngeles1.Level3.net [4.68.113.1
66]
12 * * * Request timed out.
13 * * * Request timed out.
14 93 ms 148 ms 89 ms ge-1-2.a01.phlapa04.us.ce.verio.net [130.94.0.16
6]
15 * 100 ms 93 ms 66.197.191.45
16 132 ms 123 ms 93 ms p14-0.core01.phl01.atlas.cogentco.com [66.28.4.2
]
17 134 ms 93 ms 96 ms g7.ba21.b003003-1.phl01.atlas.cogentco.com [38.1
12.34.138]
18 94 ms 94 ms 93 ms BurstNet.demarc.cogentco.com [38.112.11.122]
19 706 ms 737 ms 701 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.4
5]
20 752 ms 705 ms 710 ms 6696192220.hostnoc.net [66.96.192.220]
Trace complete.
|
Posted by midnightz, 03-16-2004, 08:57 PM |
10 packets transmitted, 0 packets received, 100% packet loss
650.00 to 700.00 ms with H! and * raining at the last hops
|
Posted by Cirtex, 03-16-2004, 08:57 PM |
Seems to be back up, or at least for now.
|
Posted by Xshare, 03-16-2004, 08:59 PM |
Not from here in Atlanta it isn't.
|
Posted by IIIBradIII, 03-16-2004, 09:03 PM |
Back up for me here in Virginia.
Pkts r/t: 317/318 0% loss
|
Posted by bizantium, 03-16-2004, 09:07 PM |
Still down
|
Posted by phactor, 03-16-2004, 09:08 PM |
back up here!
|
Posted by ISNNETCEO, 03-16-2004, 09:09 PM |
No problems from the UK now but is rerouted via another route to normal.
|
Posted by smartboyinuk, 03-16-2004, 09:12 PM |
up in uk
|
Posted by Clark2, 03-16-2004, 09:13 PM |
C:\Documents and Settings\Administrator>ping burst.net
Pinging burst.net [66.96.192.201] with 32 bytes of data:
Reply from 66.96.192.201: bytes=32 time=40ms TTL=48
Reply from 66.96.192.201: bytes=32 time=30ms TTL=48
Reply from 66.96.192.201: bytes=32 time=30ms TTL=48
Reply from 66.96.192.201: bytes=32 time=30ms TTL=48
Ping statistics for 66.96.192.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 40ms, Average = 32ms
C:\Documents and Settings\Administrator>
|
Posted by Xshare, 03-16-2004, 09:17 PM |
C:\Documents and Settings\Royi>ping burst.net
Ping request could not find host burst.net. Please check the name and try again.
C:\Documents and Settings\Royi>tracert burst.net
Unable to resolve target system name burst.net.
Dunno...
|
Posted by Cirtex, 03-16-2004, 09:18 PM |
Alertra shows it up, working here as well.
Might want to try pinging an IP from Burstnet..could be your ISP maybe.
|
Posted by hostace, 03-16-2004, 09:20 PM |
03/16/2004 20:19:32 Frankfurt GERMANY OK 14148 0.85
03/16/2004 20:19:31 Los Angeles USA OK 14148 0.61
03/16/2004 20:19:31 London UK OK 14148 0.63
03/16/2004 20:19:30 Detroit USA Unable to connect N/A 0.04
Complete.
|
Posted by thedavid, 03-16-2004, 09:29 PM |
Moved all the posts from today over to this thread, split off from the old one. Looks like a combination of routing issues and cogent today.
|
Posted by Xshare, 03-16-2004, 09:46 PM |
k, now it's back up.
|
Posted by hostbox, 03-17-2004, 02:56 PM |
Back up
BTW; this seems like a Game, Up, Down, Up, Down
|
Posted by THW-Dave, 03-17-2004, 04:07 PM |
well it cant go down down.. or up up.. so...
|
Posted by NickRac, 03-17-2004, 04:07 PM |
why don't we all stop talking about it and get a new host?
|
Posted by BikeForums, 03-19-2004, 12:00 AM |
I'm down again today, anyone else?
|
Posted by mainarea, 03-19-2004, 12:04 AM |
It's just your server, email or call for a reboot. It seems that a few servers may have been knocked offline, mine was about 30 minutes ago. I'm currently having a network issue between Comcast to ATT to Cogent which is causing issues for me, but the network is perfectly fine at this time.
Trace:
1 ge-6-0-core.scr1.hostnoc.net (66.96.192.1) 0.462 ms 0.390 ms 0.236 ms
2 * * *
I can't get to your server from inside the network. Not sure if it's a power issue or just a conincidence...
- Matt
|
Posted by BikeForums, 03-19-2004, 12:10 AM |
Hmm, just got a reply back... looks like there moving my server to another datacenter... downtime of 10 - 20 more minutes, not sure how long i have been off line.
|
Posted by HostJedi, 03-19-2004, 12:38 AM |
We've been moving a rack or two of servers a night to the newly renovated portion of our data center, from the old side - to make room for renovations on the old side. This has been an ongoing project for about a month now, and we are about 75% done with the moves.
We're updating kernels on the machines as they move as well.
Should be about 10 min per box downtime on average.
|
Add to Favourites Print this Article
Also Read