Or Speed style. "If your peering drops below 50% your network will explode"..<br><br><div class="gmail_quote">On Fri, Nov 9, 2012 at 8:53 PM, Mark Smith <span dir="ltr"><<a href="mailto:markzzzsmith@yahoo.com.au" target="_blank">markzzzsmith@yahoo.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There seems to be a bit of a trend these days for police shows to take their stories from real life events. Perhaps this Vocus/Pipe drama might end up on<br>
<br>
Law & Order : MTU<br>
<div class="im HOEnZb"><br>
<br>
<br>
<br>
----- Original Message -----<br>
> From: James Spenceley <<a href="mailto:james@vocus.com.au">james@vocus.com.au</a>><br>
> To: Noel Butler <<a href="mailto:noel.butler@ausics.net">noel.butler@ausics.net</a>><br>
> Cc: <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br>
> Sent: Thursday, 8 November 2012 4:53 PM<br>
> Subject: Re: [AusNOG] Vocus vs. Pipe - Was: Vocus peering traffic missing from PIPE-IX?<br>
><br>
</div><div class="HOEnZb"><div class="h5">> Hi All,<br>
><br>
> We are probably at the point that some level of clarification would help.<br>
><br>
> Due to contractual reasons we were required to vacate all of our racks in the<br>
> PIPE facilities and also turn off a number of misc services (such as some<br>
> remaining fibre tails and peering). For clarity TPG/PIPE was entirely entitled<br>
> to take the course of action they did.<br>
><br>
> This involved Vocus moving a not-so-insignificant number of customers'<br>
> services and kit in a very short window of time. That move was completed<br>
> successfully yesterday and the last live pieces of equipment in PIPE DCs were<br>
> turned down last night (including all peering). Not all of our peering services<br>
> were terminated, but given that we expected they would be, we have planned for<br>
> it and shut them down ahead of time.<br>
><br>
> Vocus is still openly peering at the WAIA exchange points (WAIX, VIC-IX, QLD-IX)<br>
> and also at Equinix in Sydney (where we have upgraded our port to handle the<br>
> increased bandwidth). Our full routes are still available at those points and a<br>
> huge number of locations privately, if the volume justifies the port/cross<br>
> connect/admin costs.<br>
><br>
> I'd like to thank all of our affected customers (a lot whom are on this<br>
> list) for their patience and assistance. I know this has caused you additional<br>
> cost and distraction, so the positive attitude and support you've<br>
> (literally) all shown is greatly appreciated. Also I'd like to thank our IP<br>
> and Fibre teams who managed the migrations - they are simply the best and most<br>
> dedicated guys I know and worked incredibly hard to minimise any customer<br>
> inconvenience.<br>
><br>
> A number of people have suggested that this might escalate. It won't. There<br>
> is no "war". TPG/PIPE still have racks in Vocus data centres and we<br>
> won't be changing that. I've expressed this to PIPE and those who have<br>
> voiced concerns and now it is on public record.<br>
><br>
> Both PIPE and Vocus will continue working in a professional manor for the<br>
> delivery of Fibre/Telco services to each other's facilities. Pipe exercised<br>
> their contractual rights, it caused us a lot of difficultly but that's life<br>
> its now in the past. Since then there have been no instances of anything<br>
> deliberately negative.<br>
><br>
> Cheers,<br>
><br>
> --<br>
> James<br>
><br>
> (speaking privately to ausnog, not to any wider audience)<br>
><br>
> @Nathan Brookfield, on your delay getting cross connects, I don't believe<br>
> that is down to a conspiracy or any issues between PIPE and Vocus. Please talk<br>
> to your co-lo provider about getting the cross connect escalated (I'm sure<br>
> after your post it now has some attention). If there is anything we can do to<br>
> help, drop me a line.<br>
><br>
><br>
> On 08/11/2012, at 12:55 PM, Noel Butler wrote:<br>
><br>
>> On Thu, 2012-11-08 at 12:32 +1100, Skeeve Stevens wrote:<br>
>>><br>
>>> It is like the days when AAPT through Pipe out of their DC's....<br>
> now Pipe, under the new ownership seems to be doing the same thing. The company<br>
> that rose to success largely because of who ran it and how they operated, no<br>
> longer seems to consider what people think of them, which is sad, because it is<br>
> (or was) a good network asset.<br>
>>><br>
>><br>
>> So you are claiming now something the rest of us don't know, that is<br>
> that PIPE instigated this, or are you (as I suspect) just wildly waving your<br>
> arms pointing in a direction of your least liked characters?<br>
>> You're an intelligent man Skeeve, If you did know the truth, I doubt<br>
> you would be foolish enough to even imply it in public, so lets stop with the<br>
> blame game because unless one of the entities directly involved press release<br>
> it, no-one will really know, and as it's nobody else's business I<br>
> wouldn't hold your breath waiting for one <face-wink.png> and since<br>
> I'm only a bush lawyer (like almost everyone else around here), I'd say<br>
> one party wont without the agreement of the other fearing legal ramifications.<br>
>><br>
>> _______________________________________________<br>
>> AusNOG mailing list<br>
>> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
>> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
><br>
> _______________________________________________<br>
> AusNOG mailing list<br>
> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
><br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br>