asn.dev

Observed topology

AS15672 TZTELECOM advertise with no-export community not available in all areas x7

Upstreams 12 carry this network
Downstreams 6 this network carries
Adjacent (IPv4) 17
Adjacent (IPv6) 6

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15672: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv62,755
AS9002RETN LimitedUnclassifiedIPv4 IPv61,115
AS8732JSC ComcorUnclassifiedIPv4822
AS62255BiMajLink d.o.o.UnclassifiedIPv4394
AS24482SG.GSHostingIPv4 IPv683
AS37721Virtual Technologies & SolutionsResidentialIPv482
AS49673Truenetwork LLCUnclassifiedIPv482
AS6939Hurricane Electric LLCTransitIPv464
AS50673Serverius Holding B.V.UnclassifiedIPv448
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv618
AS34927iFog GmbHHostingIPv48
AS57463NetIX Communications JSCUnclassifiedIPv48

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you.

Transit

Downstream networks

inferred

Networks for which AS15672 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS57796Freight Link OJSCUnclassifiedIPv467
AS33888Federal State Unitary Enterprise "State Scientific-research Institute of the Civil Aviation"UnclassifiedIPv467
AS203542IT-PROF LLCUnclassifiedIPv445
AS56975Metrex Engineering LTDUnclassifiedIPv639
AS35455RALF RINGER MANAGEMENT LLCUnclassifiedIPv427
AS57512OOO "Sportmaster"UnclassifiedIPv410

Adjacency

Adjacent networks

23 shown

Every AS seen directly next to AS15672 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv62,887
AS9002RETN LimitedUnclassifiedIPv4 IPv61,184
AS8732JSC ComcorUnclassifiedIPv4831
AS62255BiMajLink d.o.o.UnclassifiedIPv4405
AS24482SG.GSHostingIPv4 IPv687
AS37721Virtual Technologies & SolutionsResidentialIPv486
AS49673Truenetwork LLCUnclassifiedIPv485
AS33888Federal State Unitary Enterprise "State Scientific-research Institute of the Civil Aviation"UnclassifiedIPv467
AS57796Freight Link OJSCUnclassifiedIPv467
AS6939Hurricane Electric LLCTransitIPv464
AS50673Serverius Holding B.V.UnclassifiedIPv463
AS203542IT-PROF LLCUnclassifiedIPv445
AS56975Metrex Engineering LTDUnclassifiedIPv639
AS35455RALF RINGER MANAGEMENT LLCUnclassifiedIPv427
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv625
AS57512OOO "Sportmaster"UnclassifiedIPv410
AS57463NetIX Communications JSCUnclassifiedIPv48
AS34927iFog GmbHHostingIPv48
AS56655Gigahost ASUnclassifiedIPv61

Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS15672, 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 1 exchange across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
MSK-IX MoscowMoscow, Russia195.208.209.111498

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.

Provenance

Where this comes from

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.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 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.