I had a very clueless ATT salesperson tell me yesterday that “Our company 
policy is we don’t do BGP sessions.”  I have a client wanting to use ATT as an 
upstream and they won’t do BGP (mainly due to clueless sales). If this is the 
level of comp tenancy then good luck.  :-)


Justin Wilson
j...@mtin.net

---
http://www.mtin.net Owner/CEO
xISP Solutions- Consulting – Data Centers - Bandwidth

http://www.midwest-ix.com  COO/Chairman
Internet Exchange - Peering - Distributed Fabric

> On Feb 8, 2017, at 9:05 AM, Van Dyk, Donovan via NANOG <nanog@nanog.org> 
> wrote:
> 
> We’ve been running into a lot of problems lately with ATT peering lately. 
> Level3 included.
> 
> We have multiple carriers and most of them have run into this issue over the 
> past couple months where there is congestion between ATT and our carriers, it 
> appears there is a political issue on who should pay for the peering and 
> bandwidth. 
> My colleague says he heard on the grapevine (Horrible source I know) that ATT 
> is playing super hardball and requesting big cash for peering with them. 
> 
> Anyways, that’s all I got. 
> 
> Cheers
> 
> --
> Donovan Van Dyk
> 
> 
> 
> 
> The information contained in this electronic mail transmission and its 
> attachments may be privileged and confidential and protected from disclosure. 
> If the reader of this message is not the intended recipient (or an individual 
> responsible for delivery of the message to such person), you are strictly 
> prohibited from copying, disseminating or distributing this communication. If 
> you have received this communication in error, please notify the sender 
> immediately and destroy all electronic, paper or other versions.
> 
> 
> On 2/5/17, 8:21 PM, "david peahi" <davidpe...@gmail.com> wrote:
> 
>    We're seeing frequent dropped packets between ATT and Level 3 in Atlanta
>    with traffic sourced from an ATT user destined for Microsoft Office 365,
>    making Office 365 apps unusable during critical business hours. Anyone else
>    have this problem with ATT?
> 
> 

Reply via email to