asn.dev

Observed topology

AS15133

Not seen in any path

This AS number does not appear in any route we observed. That is normal for an AS that is allocated but not announcing, one used only privately, or one whose routes do not reach our collectors.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS15133, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 38 exchanges across 16 countries and 4 regions.

ExchangeLocationTheir addressMember ports
DE-CIX FrankfurtFrankfurt, Germany2001:7f8::3b1d:0:11,073
LINX LON1London, United Kingdom195.66.225.106925
AMS-IX AmsterdamAmsterdam, Netherlands80.249.209.162893
NAPAfrica IX JohannesburgJohannesburg, South Africa196.60.9.70603
Equinix Internet Exchange SingaporeSingapore, Singapore27.111.228.67490
Equinix Internet Exchange AshburnAshburn, United States206.126.236.112388
Seattle Internet ExchangeSeattle, United States206.81.80.152350
Any2 CaliforniaLos Angeles, United States206.72.210.232322
Equinix Internet Exchange WarsawWarsaw, Poland195.182.218.237298
Equinix Internet Exchange ChicagoChicago, United States208.115.136.144280
DE-CIX New YorkNew York, United States2001:504:36::3b1d:0:1279
Singapore Internet ExchangeSingapore, Singapore103.16.102.49273
Megaport IX SydneySydney, Australia103.26.69.90272
NetIXSofia, Bulgaria185.1.226.164264
JPIX TokyoTokyo, Japan210.171.224.234259
Equinix Internet Exchange SydneySydney, Australia45.127.173.33238
DE-CIX MadridMadrid, Spain2001:7f8:a0::3b1d:0:1229
DE-CIX DusseldorfDüsseldorf, Germany185.1.170.59225
Equinix Internet Exchange DallasDallas, United States206.223.118.44225
New York International Internet ExchangeNew York, United States198.32.160.14217
DE-CIX MunichMunich, Germany185.1.208.177207
IX Australia (Sydney NSW)Sydney, Australia218.100.53.39198
DE-CIX HamburgHamburg, Germany2001:7f8:3d::3b1d:0:1195
Digital Realty Atlanta Internet ExchangeAtlanta, United States206.126.110.199175
Equinix Internet Exchange MiamiMiami, United States198.32.242.236175
InterLAN-IXBucharest, Romania86.104.125.174151
Berlin Commercial Internet ExchangeBerlin, Germany193.178.185.12150
Kenya Internet Exchange Point - NairobiNairobi, Kenya196.223.21.104150
LINX ManchesterManchester, United Kingdom195.66.244.123145
DE-CIX MarseilleMarseille, France2001:7f8:36::3b1d:0:2113
Detroit Internet ExchangeDetroit, United States209.124.52.39102
Equinix Internet Exchange New YorkNew York, United States198.32.118.8598
AMS-IX MumbaiMumbai, India223.31.200.4285
Digital Realty New York Internet ExchangeNew York, United States206.126.115.23675
Equinix Los Angeles IBXLos Angeles, United States206.223.123.1472
DE-CIX LisbonLisbon, Portugal2001:7f8:d5::3b1d:0:163
Gigabit Portuguese Internet Exchange PointLisbon, Portugal193.136.250.17561
Equinix Internet Exchange SeattleSeattle, United States198.32.134.2743

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.