| Posted by Trek, 12-04-2004, 02:30 AM | |
Their own website is not responding, down as of 10:28pm PST.
|
| Posted by coski, 12-04-2004, 02:49 AM | |
I'm down as well
|
| Posted by DeltaAnime, 12-04-2004, 03:03 AM | |
Website replies, IRC is fried for me
~Francisco
|
| Posted by coski, 12-04-2004, 03:09 AM | |
it appears that i'm back online now. Still on the slow side.
Edit. Down again
|
| Posted by DeltaAnime, 12-04-2004, 03:12 AM | |
Web is full speed for me, no drop out's or anything.
But IRC seems to be dropping, with 180ms pings (around 3x higher than it should be).
All i can figure is, is that it's a attack of sorts
|
| Posted by Trek, 12-04-2004, 03:19 AM | |
Well, I'd hope that my server is nowhere near any of the IRC servers... since I don't have IRC anything with them... Kinda why I host my IRC server elsewhere from my other hosts... ugh...
|
| Posted by DeltaAnime, 12-04-2004, 03:23 AM | |
a guy's saying that it looks like another Level3 routing issue, since it's not just on the IRC side for him
~Francisco
|
| Posted by HostTheNet, 12-04-2004, 03:29 AM | |
Level 3 is having problems,
I know a pop is having a problem, and rumor has it that an oc192 is down.
-HTN
|
| Posted by HostTheNet, 12-04-2004, 03:33 AM | |
(01:30:50) Rack Masters - Systems Administrator - New Backup Service In Place: you can post, as my box 66.90.104.xxx is 200ms
Just thought i'd post that
|
| Posted by DeltaAnime, 12-04-2004, 03:33 AM | |
Why don't they just click it all over to cogent or whatever their fall over is :\
~Francisco
|
| Posted by HostTheNet, 12-04-2004, 03:35 AM | |
Not sure, i guess because that is the logical thing to do
|
| Posted by bummer6666, 12-04-2004, 03:41 AM | |
yes it`s L3 and they are working to fix the issue. There is about %60 % packet loss and they are saying it will be fixed shortly
the COgent is unaffected
|
| Posted by DeltaAnime, 12-04-2004, 03:42 AM | |
Keep everyone posted Petr =\
Is this only a issue between fdc <--> l3 ? or is there other people affected too?
~Francisco
|
| Posted by bummer6666, 12-04-2004, 03:46 AM | |
not sure..but if you`ll do the traceroute you`ll see the problem starts L3 network.
To be totaly honest we`ve had so many problems with them in last 2 months that we`re seriously thinking about ditching them. Their uptime has been 100 times crappier than Cogent`s
|
| Posted by DeltaAnime, 12-04-2004, 03:48 AM | |
TO be honest, while YIPES was a whore about reporting in, they were SOLID for me and others too.
It just seems that l3 is blowing up in each area. A little bit ago poor Sagonet was getting beaten up by them, then it was S4Y, and now you guys.
I hope you guys scare some sence into them, 'cuz really, for the cost that l3 must be, you should not be getting no where near as much as this
~Francisco
|
| Posted by HostTheNet, 12-04-2004, 03:49 AM | |
bummer, if the cogent is unnaffected, then why isnt the datacenter up on the cogent bandwith?
|
| Posted by AtomixNetwork, 12-04-2004, 03:52 AM | |
Ditch them and make us all happy
|
| Posted by HostTheNet, 12-04-2004, 03:54 AM | |
Ping statistics for 66.90.103.xxx:
Packets: Sent = 162, Received = 71, Lost = 91 (56% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 201ms, Average = 82ms
|
| Posted by johnnyo, 12-04-2004, 03:54 AM | |
level3 should be very nice, sure its no attack thing or something?
|
| Posted by superprogram, 12-04-2004, 03:57 AM | |
What is FDC?
|
| Posted by Punker1985, 12-04-2004, 03:58 AM | |
johnnyo it's an attack on the l3 router of 4.79.72.46 there is nothing FDC can do except for bitch @ l3
|
| Posted by RossH, 12-04-2004, 04:00 AM | |
L3 in chicago is having some major problems. For our Broadband customers we have a L3 pipe that comes outt chicago and everyone is having problems and we are logging calls like crazy.
|
| Posted by tek, 12-04-2004, 04:02 AM | |
Can't traffic be diverted to Cogent or some other provider that FDC is contracted with (BGP)?
Last edited by tek; 12-04-2004 at 04:15 AM.
|
| Posted by HostTheNet, 12-04-2004, 04:03 AM | |
Yes, it can.
I want to know why it hasnt yet.
|
| Posted by RossH, 12-04-2004, 04:03 AM | |
From St. Louis, MO
Target Name: www.fdcservers.net
IP: 66.90.66.135
Date/Time: 12/4/2004 2:01:41 AM
1 12 ms 222 ms 12 ms 314 ms 13 ms [10.18.160.1]
2 166 ms 281 ms 12 ms 287 ms 10 ms [24.217.2.157]
3 11 ms 256 ms 13 ms 286 ms 11 ms [24.217.63.193]
4 12 ms 275 ms 14 ms 261 ms 11 ms [24.217.63.194]
5 14 ms 294 ms 14 ms 236 ms 14 ms fl1-014.charter-stl.com [24.217.4.14]
6 35 ms 317 ms 22 ms 222 ms 26 ms so-1-2-0.gar2.chi1.bbnplanet.net [4.79.74.1]
7 N/A N/A 21 ms 197 ms 20 ms so-3-3-0.bbr1.Chicago1.Level3.net [4.68.96.41]
8 N/A N/A 22 ms 172 ms 22 ms so-7-0-0.gar1.Chicago1.Level3.net [4.68.96.50]
9 * 363 ms N/A N/A 149 ms [4.79.72.46]
10 * 389 ms * * 143 ms [209.120.176.2]
11 149 ms 364 ms * 289 ms 150 ms mail.web.fdcservers.net [66.90.66.135]
Ping statistics for www.fdcservers.net
Packets: Sent = 5, Received = 4, Lost = 1 (20.0%)
Round Trip Times: Minimum = 149ms, Maximum = 364ms, Average = 238ms
|
| Posted by DeltaAnime, 12-04-2004, 04:16 AM | |
Has there been any ground made petr, on either getting l3 happy, or getting cogent online?
~Francisco
|
| Posted by HostTheNet, 12-04-2004, 04:33 AM | |
Tracing route to fdcservers.net [66.90.66.135]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 102 ms 7 ms 7 ms adsl-68-75-85-254.dsl.milwwi.ameritech.net
[68.75.85.254]
3 8 ms 8 ms 8 ms dist2-vlan50.milwwi.ameritech.net
[65.43.19.227]
4 8 ms 8 ms 8 ms bb1-g1-0.milwwi.ameritech.net [65.43.19.99]
5 220 ms 50 ms 47 ms bb2-p11-3.milwwi.sbcglobal.net
[151.164.189.198]
6 10 ms 10 ms 11 ms bb1-p4-0.emhril.ameritech.net
[151.164.190.97]
7 222 ms 11 ms 10 ms bb2-p13-0.emhril.ameritech.net
[151.164.191.174]
8 11 ms 11 ms 11 ms ex2-p6-3.eqchil.sbcglobal.net
[151.164.40.86]
9 11 ms 11 ms 136 ms asn174-Cogent.eqchil.sbcglobal.net
[151.164.249.214]
10 176 ms 10 ms 11 ms p12-0.core02.ord01.atlas.cogentco.com
[154.54.2.241]
11 128 ms 411 ms 2133 ms FDC_Servers.demarc.cogentco.com
[38.112.0.234]
12 1704 ms 1668 ms 1466 ms mail.web.fdcservers.net [66.90.66.135]
Trace complete.
Got that from a freind.
|
| Posted by BSDAxis, 12-04-2004, 04:35 AM | |
What's the current status of everyone's dedicated servers? I am only having 25% packet loss when I ping my main IP address.
I did a traceroute on the IP, and it seems that LEVEL3 has gotten some of the issues fixed.
|
| Posted by johnnyo, 12-04-2004, 04:36 AM | |
just noticed another full dropout, even fdc homepage/board
and after this, incoming cogen/outgoing also, but still 45% loss to europe weird...
|
| Posted by HostTheNet, 12-04-2004, 04:36 AM | |
hmm... got this from myself
1 <10 ms <10 ms <10 ms 192.168.254.254
2 10 ms 10 ms 10 ms dsl-254.grp22.tnmmrl.infoave.net [204.116.106.25
4]
3 10 ms <10 ms <10 ms vlan2.gwy.tnmmrl.infoave.net [64.53.83.66]
4 10 ms 10 ms 20 ms 66.238.242.17.ptr.us.xo.net [66.238.242.17]
5 50 ms 50 ms 20 ms p4-3-0.MAR2.Nashville-TN.us.xo.net [207.88.85.10
9]
6 30 ms 20 ms 80 ms p5-1-0-3.RAR2.Atlanta-GA.us.xo.net [65.106.4.49]
7 40 ms 40 ms 40 ms p1-0-0.RAR2.Washington-DC.us.xo.net [65.106.0.5]
8 40 ms 40 ms 40 ms p1-0.IR1.Ashburn-VA.us.xo.net [65.106.3.138]
9 40 ms 40 ms 50 ms p12-5.core01.iad01.atlas.cogentco.com [154.54.10
.249]
10 40 ms 50 ms 40 ms p11-0.core02.dca01.atlas.cogentco.com [154.54.2.
197]
11 50 ms 40 ms 50 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82
]
12 40 ms 50 ms 51 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.1
4]
13 70 ms 80 ms 70 ms p14-0.core02.ord01.atlas.cogentco.com [66.28.4.8
6]
14 80 ms 70 ms 70 ms FDC_Servers.demarc.cogentco.com [38.112.0.234]
15 70 ms 70 ms 80 ms mail.web.fdcservers.net [66.90.66.135]
|
| Posted by BSDAxis, 12-04-2004, 04:41 AM | |
I notice that the IP 209.120.155.14 is getting request timed out on traceroute.
|
| Posted by HostTheNet, 12-04-2004, 04:41 AM | |
Ping statistics for 66.90.66.135:
Packets: Sent = 219, Received = 219, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 81ms, Average = 71ms
|
| Posted by johnnyo, 12-04-2004, 04:47 AM | |
hey.. just got an idea, why dont you switch level3 and cogent .. cogent
incoming and level3 out? would that change something?
huh.. seems to be fixed now..!!
|
| Posted by BSDAxis, 12-04-2004, 04:51 AM | |
no, its not fixed. When I ping my server, I get 50% loss =|.
I hope this gets fixed promtly. Customers are complaining ugh.
|
| Posted by johnnyo, 12-04-2004, 04:52 AM | |
weird.. i just tested both outgoing ping to europe from fdc, and back from europe to my server, 0% packet loss.
:
52 packets transmitted, 52 received, 0% packet loss, time 51058ms
|
| Posted by Trek, 12-04-2004, 04:56 AM | |
My server seems to be back up, no packet loss, decent ping times.
|
| Posted by BSDAxis, 12-04-2004, 05:10 AM | |
What network are you on with FDCServers? The Web hosting network, or the IRC Network? I am currently on the IRC Network, and I still have no luck.
Here is my ping results:
Pinging 208.53.145.130 with 32 bytes of data:
Reply 208.53.145.130: bytes=32 time=192ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 208.53.145.130:
Packets: sent = 4, Recieved = 1, Lost (75% loss)
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 192ms, Average = 192ms
|
| Posted by HostTheNet, 12-04-2004, 05:10 AM | |
seems like fdc is slowly making a come back, im routed thru cogent now.
|
| Posted by Homeslice, 12-04-2004, 03:54 PM | |
Hi,
Does anyone know anything about Yipes NET dedicated Intenet service ? I was wondering what it is costing people on the average for say a 1mbps-10mbps. And any feedback on experiences with their service will be much appreciated.
Thanks,
Homeslice
PM me if you'd like.
|
| Posted by IGobyTerry, 12-04-2004, 04:02 PM | |
Tracing route to fdcservers.net [66.90.66.135]
over a maximum of 30 hops:
1 37 ms 16 ms 15 ms h-66-167-210-1.sfldmidn.dynamic.covad.net [66.167.210.1]
2 17 ms 16 ms 15 ms 192.168.7.97
3 18 ms 18 ms 16 ms ge-5-1-133.hsa1.Detroit1.Level3.net [63.211.20.185]
4 17 ms 16 ms 16 ms ge-6-1-0.mp1.Detroit1.Level3.net [64.159.4.185]
5 22 ms 39 ms 22 ms so-0-1-0.bbr2.Chicago1.Level3.net [64.159.1.34]
6 24 ms 23 ms 35 ms so-7-0-0.gar1.Chicago1.Level3.net [4.68.96.50]
7 23 ms 22 ms 22 ms 4.79.72.42
8 25 ms 22 ms 23 ms 209.120.176.2
9 25 ms 24 ms 23 ms mail.web.fdcservers.net [66.90.66.135]
It's all perty for me now
|
| Posted by jsw6, 12-04-2004, 04:04 PM | |
Yipes, like any other carrier, isn't going to give you a bargain on a 10Mbps commit. I assume your desire to be with Yipes is driven by cost. You'd be better off with an economy hosting / co-location product than trying to deal with carriers directly at that small traffic level. You'll end up paying upwards of $50/Mbps, and probably close to $100/Mbps, for almost any carrier transit product at 10Mbps.
Beyond that, Yipes isn't a great choice of carrier from a technical perspective. They support virtually no BGP community features, and I doubt they'll ever invest man-hours in adding them. If you're going to buy from a carrier directly, choose one who can suit your needs. If you can't afford that, just find an economy hosting product that you're happy with until you grow into something bigger.
|
|
 Add to Favourites
 Print this Article
|
