asn.dev

Observed topology

AS197667 FEROMEDIA-AS

Residential RIPE

Upstreams 11 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 5
Upstream graph Who carries AS197667, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS197667 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS197667: 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
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4129
AS6939Hurricane Electric LLCTransitIPv4 IPv688
AS5617Orange Polska Spolka AkcyjnaMobileIPv4 IPv651
AS3257GTT Communications Inc.TransitIPv418
AS24482SG.GSHostingIPv4 IPv69
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv68
AS33891Core-Backbone GmbHHostingIPv46
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv46
AS20485Joint Stock Company TransTeleComUnclassifiedIPv44
AS24115EquinixHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197701NET-KOMP Krystian KaniaUnclassifiedIPv4102

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4225
AS197701NET-KOMP Krystian KaniaUnclassifiedIPv4102
AS6939Hurricane Electric LLCTransitIPv4 IPv688
AS5617Orange Polska Spolka AkcyjnaMobileIPv4 IPv654
AS3257GTT Communications Inc.TransitIPv421
AS24482SG.GSHostingIPv4 IPv69
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv68
AS33891Core-Backbone GmbHHostingIPv46
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv46
AS20485Joint Stock Company TransTeleComUnclassifiedIPv44

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.