Observed topology
AS13094 SFO-IX-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS13094: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 11 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 1 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 | 1 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 1 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 1 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS13094 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56451 | Telekey-S Ltd | Unclassified | IPv4 | 54 |
| AS31695 | Limited Company "Intermedia" | Unclassified | IPv4 | 50 |
| AS58067 | JOINT-STOCK COMPANY "MOSCOW ENERGY COMMUNICATION NODE" | Unclassified | IPv4 | 36 |
| AS50427 | Orion Telecom LLC | Residential | IPv4 | 26 |
| AS15880 | Private entrepreneur Chikalin Anatoly Nikolaevich | Unclassified | IPv4 | 24 |
| AS48327 | Ray-Svyaz Ltd. | Unclassified | IPv6 | 23 |
| AS203493 | Egor Timoshenko | Hosting | IPv4 IPv6 | 20 |
| AS52175 | Magellan Telecom Kuzbass Ltd. | Unclassified | IPv4 | 19 |
| AS51086 | Scientific and production association "SCAT" Ltd. | Unclassified | IPv4 | 15 |
| AS56707 | OOO NETCOM | Unclassified | IPv4 | 13 |
Adjacency
Adjacent networks
Every AS seen directly next to AS13094 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 229 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 109 |
| AS203493 | Egor Timoshenko | Hosting | IPv4 IPv6 | 97 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 86 |
| AS58067 | JOINT-STOCK COMPANY "MOSCOW ENERGY COMMUNICATION NODE" | Unclassified | IPv4 | 70 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 68 |
| AS56451 | Telekey-S Ltd | Unclassified | IPv4 | 54 |
| AS31695 | Limited Company "Intermedia" | Unclassified | IPv4 | 50 |
| AS50427 | Orion Telecom LLC | Residential | IPv4 | 26 |
| AS15880 | Private entrepreneur Chikalin Anatoly Nikolaevich | Unclassified | IPv4 | 24 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.