August 2021 - Discuss

XMission Router Maintenance
by Lindsay Parsons 24 Aug '21

24 Aug '21

Hello, XMission (AS6135) will be upgrading the router we use to peer with SLIX tonight. You can expect our peer to be down tonight between 12:01 AM - 6:00 AM MDT. For reference: XMission AS6315 IPv4: 149.112.13.11 IPv6: 2001:504:105::11 Thank you, [ https://xmission.com/ ] Lindsay Parsons XMission Jr. Network Administrator 801.303.0821 [ mailto:lindsay@xmission.com | lindsay(a)xmission.com ] [ https://www.facebook.com/XMissionInternet ] [ https://twitter.com/#!/xmission ] [ https://www.linkedin.com/ ] Utah's premier Internet provider since 1993.

1 0

Microsoft has joined SLIX
by Microsoft Internet Peering Team 12 Aug '21

12 Aug '21

Hello SLIX Peers, Microsoft has joined SLIX ! Please review our peering policy at https://www.microsoft.com/peering<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeering.a…> and follow the process to request peering. Microsoft peering requests are processed via Azure portal which provides automatable steps to set up and easy way to manage all your peerings in one place. Peering with Microsoft will directly connect you to services including O365, Azure, Xbox, MSN, Bing and more! Thank you for peering with Microsoft! Microsoft Interconnection Team - AS8075 [cid:image001.jpg@01D78F65.ACC92050]

1 0

Welcome Packet Clearing House AS42/AS3856
by Pete Ashdown 09 Aug '21

09 Aug '21

Packet Clearing House AS42/AS3856 is on SLIX with 2x10Gb ports. AS: 42/3856 PeeringDB: https://www.peeringdb.com/net/3924 <https://www.peeringdb.com/net/3924> https://www.peeringdb.com/net/286 <https://www.peeringdb.com/net/286> Policy: Open IPv4: 149.112.13.30 IPv4: 149.112.13.37 IPv6: 2001:504:105::30 IPv6: 2001:504:105::37

1 0

Fwd: Automatic reply: [EXTERNAL] [Salt Lake Internet eXchange] Peering Request
by Pete Ashdown 03 Aug '21

03 Aug '21

If you use the IXP Manager “Peering Manager” to request peering from Microsoft, this email will be sent back to info(a)slix.net <mailto:info@slix.net>. I’m forwarding it here so everyone can see their procedure. > Begin forwarded message: > > From: Peering-Interconnection <inter-x(a)microsoft.com> > Subject: Automatic reply: [EXTERNAL] [Salt Lake Internet eXchange] Peering Request from Veracity Networks (ASN29933) > Date: August 2, 2021 at 11:21:56 PM GMT+2 > To: Salt Lake Internet eXchange <info(a)slix.net> > > Hello, > To report a live site issue or network outage, please email ioc(a)microsoft.com <mailto:ioc@microsoft.com> or call +1(425) 705-2686 for immediate assistance. > For Exchange Peering requests: > Please review our peering policy at https://www.microsoft.com/peering <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.micro…> and follow the process to request Exchange peering. An Azure account is required with credit card validation. The credit card validation is only used for our fraud management system and will not be charged. The Azure resource types used to set up peering are always-free Azure products, i.e., you are not charged for creating an Azure account or creating a subscription or accessing the Azure resources PeerAsn and Peering to set up peering. > If this is regarding private peering or any other peering related questions, this email is monitored during normal business hours and most emails are replied to within 24 hours. > Microsoft encourages companies to build a profile in peeringdb because several of our internal tools utilize the database for contact and location information. Please keep in mind that it can take our tool up to 24 hours to see new information in Peeringdb. > Our complete peering details can be viewed at http://as8075.peeringdb.com <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fas8075.pee…> > Thank you, > Microsoft Interconnection Team.

1 0