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.
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]
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.
Google AS15169 is on SLIX with 2x100Gb ports.
AS: 15169
PeeringDB: https://peeringdb.com/net/433
Policy: "Generally Open"
IPv4: 149.112.13.41
IPv4: 149.112.13.42
IPv6: 2001:504:105::41
IPv6: 2001:504:105::42
Google AS15169 is currently peering with both route-servers. If you are
already peering with the route-servers, you will see their advertised
routes immediately. If you would like to peer with the route-servers and
currently are not, please contact info(a)slix.net, as access is not open
by default.
Dates: 2021/06/06 & 2021/06/07
Maintenance Window: 05:25 MDT - 05:35 MDT
Where: SLIX Route Servers & AS112 peer
The AS112 peer server will be rebooted at on 2021/06/06 @ 05:25 MDT and
route-server-1 will reboot at 05:30 MDT for kernel and OS updates.
Route-server-2 will be rebooted the following morning at 2021/06/07 @
05:30 MDT for kernel and OS updates.
Please peer with both route-server-1 and route-server-2 if you wish to
have uninterrupted service to other SLIX route-server participants. If
you aren't peering with the route-servers yet, and wish to, please email
me so I can set you up.
When: May 29, 2021
Maintenance Window: 00:00 MDT - 01:00 MDT
Where: SLIX EdgeConnex
The SLIX 100Gb switch at EdgeConnex will be swapped out tonight with a higher-power model more suited for the required 40KM optic backhaul.
Peers affected:
Amazon
Cloudflare
Twitch
Hey all, the number of participants peering with the route-servers is
growing, but I'm noticing that many do not have some or all of their
routes registered in an IRRDB like RADB or ARIN. If they are not
registered, the route-server will not pass them on to other peers. If
someone else has RPKI registered a network you are announcing
unauthorized, it will also drop these routes.
If you go to the looking glass page at:
https://ixp.slix.net/lg
You can select between IPv4 and IPv6 routers and then look at the view
the routers have of your peer. The route-collectors simply takes routes
in and doesn't export anything, so you can feel free to experiment with it.
The routes with a black triangle with an exclamation point are being
filtered. If you click on the DETAILS button to the right, you can see
why.
In addition to IRRDB, RPKI is checked, which I also recommend that
everyone look into, as more and more networks are RPKI filtering. If
you're paying ARIN for services right now, you can most likely use their
IRRDB and RPKI registries for no additional charge. Otherwise, radb.net
is good for IRRDB entries as well.
