ixreport

SAS Global Communications

AS205917 · SAS Telecoms

SAS Global Communications Ltd.

2Exchanges
0On an exchange's list, not in PeeringDB
2In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
2Using the route servers
2To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with SAS Global Communications? · Where should SAS Global Communications peer next? · Compare SAS Global Communications with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in SAS Global Communications's PeeringDB record, from what its exchanges publish: 2 to check. As of 2026-11-19 18:41 UTC.

Make the changes on SAS Global Communications's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If SAS Global Communications has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18Not on its IX-F export or website members list
    IPv4195.66.227.134
    IPv62001:7f8:4::3:245d:1
    Speed1000 Mbps (1G)
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.239.134
    IPv6–
    Speed1000 Mbps (1G)

Exchanges over time

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
Nov 8, 20262
Nov 7, 20262
Nov 6, 20262
Nov 5, 20262
Nov 4, 20262
Nov 3, 20262
Nov 2, 20262
Nov 1, 20262
Oct 31, 20262
Oct 30, 20262
Oct 29, 20262
Oct 28, 20262
Oct 27, 20262
Oct 26, 20262
Oct 25, 20262
Oct 24, 20262
Oct 23, 20262
Oct 22, 20262
Oct 21, 20262
Oct 20, 20262
Oct 19, 20262
Oct 18, 20262
Oct 17, 20262
Oct 16, 20262
Oct 15, 20262
Oct 14, 20262
Oct 13, 20262
Oct 12, 20262
Oct 11, 20262
Oct 10, 20262
Oct 9, 20262
Oct 8, 20262
Oct 7, 20262
Oct 6, 20262
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where SAS Global Communications's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 2G across 2 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.227.134 2001:7f8:4::3:245d:1 1G Yes PeeringDB only
United Kingdom LINX LON2 London, United Kingdom 195.66.239.134 1G Yes PeeringDB only

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where SAS Global Communications lists itself in PeeringDB, but don't have SAS Global Communications as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands North Two)
United Kingdom LONAPLondon, United Kingdom 311 Telehouse - London (Docklands North Two)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North Two)
Facilities (2)

The buildings SAS Global Communications lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Telehouse - London (Docklands North Two)London 2 of 5
United Kingdom Redhill DatacenterRedhill No exchange