Observed topology
AS15672 TZTELECOM advertise with no-export community not available in all areas x7
Unclassified RIPE
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 2,962 |
| AS8732 | JSC Comcor | Unclassified | IPv4 | 1,531 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 579 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 85 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 84 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 84 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 56 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 32 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 17 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS15672 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33888 | Federal State Unitary Enterprise "State Scientific-research Institute of the Civil Aviation" | Unclassified | IPv4 | 65 |
| AS57796 | Freight Link OJSC | Unclassified | IPv4 | 65 |
| AS219081 | Klinika Bud Zdorov LLC | Unclassified | IPv4 | 64 |
| AS56975 | Metrex Engineering LTD | Unclassified | IPv4 IPv6 | 42 |
| AS203542 | IT-PROF LLC | Unclassified | IPv4 | 41 |
| AS35455 | RALF RINGER MANAGEMENT LLC | Unclassified | IPv4 | 16 |
| AS57512 | OOO "Sportmaster" | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS15672 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 3,151 |
| AS8732 | JSC Comcor | Unclassified | IPv4 | 1,562 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 617 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 90 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 88 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 88 |
| AS33888 | Federal State Unitary Enterprise "State Scientific-research Institute of the Civil Aviation" | Unclassified | IPv4 | 65 |
| AS57796 | Freight Link OJSC | Unclassified | IPv4 | 65 |
| AS219081 | Klinika Bud Zdorov LLC | Unclassified | IPv4 | 64 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 62 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
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. 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.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.