kentha
04-11-2003, 03:41 AM
Can you guy tell if Yipes network is realiable? Are they as good as NAC or Verio or Interlap?
Please give your comments
Please give your comments
![]() | View Full Version : Yipes network kentha 04-11-2003, 03:41 AM Can you guy tell if Yipes network is realiable? Are they as good as NAC or Verio or Interlap? Please give your comments mahinder 04-11-2003, 05:40 AM NAC is the data center. http://www.nac.net/ kentha 04-11-2003, 05:43 AM You mean Yipes are from NAC Datacenter? Where can I find this information from NAC website? Razer 04-11-2003, 06:19 AM If u want cheap yipes go to fdcservers.net As far as my knowledge serves me, i dont recall nac DC having yipes although they do have dcjn and premium nac b/w. Internap, Verio and premium nac b/w is way better than yipes. tazzy 04-11-2003, 06:35 AM Hello, It depends if you have Yipes --> Williams or Yipes --> Level3. Yipes does have peering aswell. :) alapo 04-11-2003, 08:51 AM Originally posted by kentha Can you guy tell if Yipes network is realiable? Are they as good as NAC or Verio or Interlap? Please give your comments Internap. Internap is cream of the crop (and quite expensive too). It has a blend of Verio, and other providers. Everyday 04-11-2003, 10:35 AM Yipes has been extremely reliable for us. One thing they have that most don't is 100% fiber. So its actually a fiber connection right to the data centers router. The connection is very fast from almost every spot in the country and very decent from overseas. illogix 04-11-2003, 10:39 AM I wouldn't go with Yipes as they might switch you to 100% Williams bandwidth anytime. And Level3 to Williams is big drop in quality. That's what happened to the company we have our dedicated servers from. kentha 04-11-2003, 10:55 AM How can they do that? How can they swift to William like that? mgriffin 04-11-2003, 01:25 PM Originally posted by illogix I wouldn't go with Yipes as they might switch you to 100% Williams bandwidth anytime. And Level3 to Williams is big drop in quality. That's what happened to the company we have our dedicated servers from. My guess (and is my guess only - I haven't talked to Yipes in some time) is that Yipes is offering Williams only bandwidth as a low cost option in addition to their standard offerings. I have seen Yipes peering w/ Level(3)/Genuity, Level(3)/Williams, and Williams-only in different markets / to different customers. Internap actually has a similar offering, where they'll put customers on 4-5 lower cost networks at a lower price in select markets in addition to their standard offering on 8-10 providers in most markets. From my observation, in markets served by Williams, they're dropping Genuity and moving to Williams along with Level(3). We're fed by Yipes in Denver which is still on Level(3)/Genuity (however Williams doesn't currently serve Denver, so I'm not sure if this will change once Williams turns up Denver) My guess is Williams-only through Yipes is by special arragement in order to save costs (again, I have no hard proof of this) - Mike kerplunk 04-11-2003, 08:27 PM I have never had any real problems with level3/genuity/yipes. I'd never leave BTN, though. :) XanTium 04-11-2003, 11:06 PM Yipes! ... that's slow Pinging yipes.com [209.213.209.72] with 32 bytes of data: Reply from 209.213.209.72: bytes=32 time=163ms TTL=240 Reply from 209.213.209.72: bytes=32 time=163ms TTL=240 Reply from 209.213.209.72: bytes=32 time=163ms TTL=240 Reply from 209.213.209.72: bytes=32 time=164ms TTL=240 Ping statistics for 209.213.209.72: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 163ms, Maximum = 164ms, Average = 163ms A good connected to USA is 90-100ms Everyday 04-11-2003, 11:36 PM Where is that ping from and what data center is it going to? mgriffin 04-11-2003, 11:37 PM That IP appears to be yipes.com, which is hosted in San Francisco. Knogle 04-12-2003, 01:43 AM C:\WINDOWS>ping yipes.com Pinging yipes.com [209.213.209.72] with 32 bytes of data: Reply from 209.213.209.72: bytes=32 time=219ms TTL=241 Reply from 209.213.209.72: bytes=32 time=263ms TTL=241 Reply from 209.213.209.72: bytes=32 time=252ms TTL=241 Reply from 209.213.209.72: bytes=32 time=226ms TTL=241 Ping statistics for 209.213.209.72: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 219ms, Maximum = 263ms, Average = 240ms That's one of the best ping times to the US i've seen. Erich 04-12-2003, 05:35 AM Originally posted by XanTium Yipes! ... that's slow A good connected to USA is 90-100ms to the east coast yes, to san francisco: not possible DarktidesNET 04-12-2003, 05:49 AM I get pretty good speeds to Yipes. Everyday 04-12-2003, 10:45 AM Depending on where you are coming from give this IP a try 66.227.114.219 its on the east coast. Dmax 04-12-2003, 01:14 PM When I ping yipes.com from Seattle WA I get as good or better ping than I do when pinging other SanFran IP from companies like Level3 and Verio ping yipes.com Pinging yipes.com [209.213.209.72] with 32 bytes of data: Reply from 209.213.209.72: bytes=32 time=61ms TTL=236 Reply from 209.213.209.72: bytes=32 time=29ms TTL=236 Reply from 209.213.209.72: bytes=32 time=34ms TTL=236 Reply from 209.213.209.72: bytes=32 time=29ms TTL=236 Ping statistics for 209.213.209.72: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 61ms, Average = 38ms -Denis kerplunk 04-12-2003, 03:02 PM Minnesota here. (central) I get a little bit above 100ms. Yipes! XanTium 04-12-2003, 08:36 PM Originally posted by XanTium Yipes! ... that's slow A good connected to USA is 90-100ms From Belgium 3mbit ADSL. It's going through Level3 first then on yipes. XanTium 04-12-2003, 08:38 PM Originally posted by Everyday Depending on where you are coming from give this IP a try 66.227.114.219 its on the east coast. yep ... you are right , yipes isn't bad at all after all. Reply from 66.227.114.219: bytes=32 time=91ms TTL=240 Reply from 66.227.114.219: bytes=32 time=90ms TTL=240 Reply from 66.227.114.219: bytes=32 time=92ms TTL=240 Reply from 66.227.114.219: bytes=32 time=89ms TTL=240 serverguy 04-13-2003, 05:53 PM Originally posted by mgriffin My guess (and is my guess only - I haven't talked to Yipes in some time) is that Yipes is offering Williams only bandwidth as a low cost option in addition to their standard offerings. I have seen Yipes peering w/ Level(3)/Genuity, Level(3)/Williams, and Williams-only in different markets / to different customers. Internap actually has a similar offering, where they'll put customers on 4-5 lower cost networks at a lower price in select markets in addition to their standard offering on 8-10 providers in most markets. From my observation, in markets served by Williams, they're dropping Genuity and moving to Williams along with Level(3). We're fed by Yipes in Denver which is still on Level(3)/Genuity (however Williams doesn't currently serve Denver, so I'm not sure if this will change once Williams turns up Denver) My guess is Williams-only through Yipes is by special arragement in order to save costs (again, I have no hard proof of this) - Mike Williams is in Denver at the main telco hotel, 910 15th st. They also offer DS3-OC12 to metro Denver via Qwest, ICG and others. mgriffin 04-13-2003, 06:00 PM Originally posted by serverguy Williams is in Denver at the main telco hotel, 910 15th st. They also offer DS3-OC12 to metro Denver via Qwest, ICG and others. Interesting. Last time I'd looked at the WCG backbone maps, Denver was listed as planned deployment city. Checking the map today, it does show Denver lit, so I guess time will tell with regards to Yipes peering here in Denver. eprodigy 04-13-2003, 06:35 PM Pinging yipes.com [209.213.209.72] with 32 bytes of data: Reply from 209.213.209.72: bytes=32 time=26ms TTL=244 Reply from 209.213.209.72: bytes=32 time=26ms TTL=244 Reply from 209.213.209.72: bytes=32 time=30ms TTL=244 Reply from 209.213.209.72: bytes=32 time=27ms TTL=244 Ping statistics for 209.213.209.72: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 26ms, Maximum = 30ms, Average = 27ms Great ping for me (Northern California)... webreseller 04-13-2003, 11:40 PM 209.213.209.72 is the yipes site which I know for a fact they have pings at the lowest priority level. We have used Yipes for close to 3 years and they are excellent. We have had nothing short of amazing service from them with attention to details. They have moved some centers to williams, however, only some. The use Level 3 (first and foremost), then as backups Genuity and Williams. With Level 3 purchasing Genuity there may have been some changes, however, they will be adding. We can not say anything negative about Yipes, they have been great. To test an IP on yipes you can use 66.54.216.242 Good luck... tweak` 04-17-2003, 10:07 PM i did tracerout from me in connecticut to the san fran site host. Tracing route to pecos.yipes.com [209.213.209.72] over a maximum of 30 hops: 1 31 ms 12 ms 15 ms 10.175.0.1 2 45 ms 16 ms 37 ms 12.244.126.225 3 50 ms 14 ms 50 ms 12.244.70.170 4 27 ms 18 ms 90 ms 12.244.73.102 5 35 ms 68 ms 17 ms gbr6-p80.n54ny.ip.att.net [12.123.1.206] 6 30 ms 17 ms 25 ms tbr2-p012401.n54ny.ip.att.net [12.122.11.29] 7 36 ms 33 ms 16 ms ggr1-p320.n54ny.ip.att.net [12.122.12.54] 8 30 ms 93 ms 16 ms interconnect-eng.NewYork1.Level3.net [63.211.54. 73] 9 18 ms 45 ms 27 ms unknown.Level3.net [64.159.17.98] 10 110 ms 97 ms 92 ms so-3-0-0.mp2.SanFrancisco1.Level3.net [209.247.8 .90] 11 115 ms 98 ms 99 ms pos9-0.core2.SanFrancisco1.Level3.net [209.247.1 0.238] 12 86 ms 88 ms 123 ms gige7-2.ipcolo1.SanFrancisco1.Level3.net [209.24 4.14.226] 13 88 ms 85 ms 111 ms unknown.Level3.net [63.211.150.226] 14 97 ms 86 ms 87 ms o0-1jp1.sfo001bd01.yipes.com [66.7.154.129] 15 150 ms 99 ms 94 ms o10-1bd1.sfo003ap01.yipes.com [209.213.196.205] 16 96 ms 107 ms 94 ms 209.213.209.38 17 140 ms 125 ms 117 ms pecos.yipes.com [209.213.209.72] not too bad, averages to around 95 , so it is possible to get 90-100 coast to coast |