Observed topology
AS13307 SKIF-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS13307: 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 |
|---|---|---|---|---|
| AS6723 | "AS6723" LIMITED LIABILITY COMPANY | Unclassified | IPv4 IPv6 | 632 |
Transit
Downstream networks
Networks for which AS13307 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43967 | TEREMKY LAN ISP LLC | Unclassified | IPv4 | 136 |
| AS39528 | Video Internet Technologies LTD. | Unclassified | IPv4 | 66 |
| AS207896 | Tourist Club Ltd. | Unclassified | IPv4 | 66 |
| AS43580 | TOV 'Nocservice' | Unclassified | IPv4 | 62 |
| AS212375 | PJSC Kyiv Vitamin Plant | Unclassified | IPv4 | 10 |
| AS15683 | "AS6723" LIMITED LIABILITY COMPANY | Unclassified | IPv4 | 7 |
| AS31009 | Levi9 Ukraine Ltd | Unclassified | IPv4 | 5 |
Adjacency
Adjacent networks
Every AS seen directly next to AS13307 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6723 | "AS6723" LIMITED LIABILITY COMPANY | Unclassified | IPv4 IPv6 | 904 |
| AS43967 | TEREMKY LAN ISP LLC | Unclassified | IPv4 | 136 |
| AS39528 | Video Internet Technologies LTD. | Unclassified | IPv4 | 66 |
| AS207896 | Tourist Club Ltd. | Unclassified | IPv4 | 66 |
| AS43580 | TOV 'Nocservice' | Unclassified | IPv4 | 62 |
| AS24812 | RPC HomeNet Ltd. | Residential | IPv4 | 49 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 31 |
| AS212375 | PJSC Kyiv Vitamin Plant | Unclassified | IPv4 | 10 |
| AS15683 | "AS6723" LIMITED LIABILITY COMPANY | Unclassified | IPv4 | 7 |
| AS31009 | Levi9 Ukraine Ltd | Unclassified | IPv4 | 5 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-18 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.