Observed topology
AS199070 TBD-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS199070: 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.
Transit
Downstream networks
Networks for which AS199070 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS199070 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8985 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 | 234 |
| AS201835 | "State Institution of the Yamal-Nenets autonomous district Multifunctional Centre of state and municipal services" | Unclassified | IPv4 | 133 |
| AS43849 | Sever-Svyaz LLC | Unclassified | IPv4 IPv6 | 104 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 74 |
| AS39580 | GAUZ MIAC YaNAO | Unclassified | IPv4 | 12 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.