asn.dev

Observed topology

AS49769 TERACOM-AB www.teracom.se

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49769: 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
AS1299Arelion Sweden ABTransitIPv4162
AS6939Hurricane Electric LLCTransitIPv430
AS8434Telenor Sverige ABResidentialIPv430
AS50304Blix Solutions ASUnclassifiedIPv46
AS12552GlobalConnect ABUnclassifiedIPv43
AS20764CJSC RASCOMUnclassifiedIPv43
AS24482SG.GSHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213195Teracom ABUnclassifiedIPv442

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4162
AS6939Hurricane Electric LLCTransitIPv454
AS213195Teracom ABUnclassifiedIPv442
AS8434Telenor Sverige ABResidentialIPv430
AS12552GlobalConnect ABUnclassifiedIPv49
AS24482SG.GSHostingIPv49
AS33891Core-Backbone GmbHHostingIPv46
AS50304Blix Solutions ASUnclassifiedIPv46
AS20764CJSC RASCOMUnclassifiedIPv43

Provenance

Where this comes from

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