asn.dev

Observed topology

AS49770 INTERNETPORT-AS

Upstreams 17 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 16
Adjacent (IPv6) 5

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49770: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv62,369
AS1299Arelion Sweden ABTransitIPv4603
AS1257Tele2 Sverige ABMobileIPv4 IPv694
AS24482SG.GSHostingIPv4 IPv648
AS50673Serverius Holding B.V.UnclassifiedIPv416
AS50304Blix Solutions ASUnclassifiedIPv4 IPv616
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv415
AS3303Swisscom (Schweiz) AGResidentialIPv415
AS37721Virtual Technologies & SolutionsResidentialIPv415
AS49673Truenetwork LLCUnclassifiedIPv415
AS12552GlobalConnect ABUnclassifiedIPv41
AS8434Telenor Sverige ABResidentialIPv41
AS57463NetIX Communications JSCUnclassifiedIPv41
AS20473The Constant Company, LLCHostingIPv61
AS35280F5 Networks SARLHostingIPv41
AS56655Gigahost ASUnclassifiedIPv41
AS5405Inter.link GmbHUnclassifiedIPv41

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.

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

22 shown

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,369
AS1299Arelion Sweden ABTransitIPv4608
AS1257Tele2 Sverige ABMobileIPv4 IPv694
AS24482SG.GSHostingIPv4 IPv649
AS50673Serverius Holding B.V.UnclassifiedIPv418
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv416
AS50304Blix Solutions ASUnclassifiedIPv4 IPv616
AS3303Swisscom (Schweiz) AGResidentialIPv415
AS49673Truenetwork LLCUnclassifiedIPv415
AS37721Virtual Technologies & SolutionsResidentialIPv415
AS56655Gigahost ASUnclassifiedIPv42
AS35280F5 Networks SARLHostingIPv41
AS5405Inter.link GmbHUnclassifiedIPv41
AS12552GlobalConnect ABUnclassifiedIPv41
AS57463NetIX Communications JSCUnclassifiedIPv41
AS20473The Constant Company, LLCHostingIPv61
AS8434Telenor Sverige ABResidentialIPv41

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS49770, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 4 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
STHIX - StockholmStockholm, Sweden192.121.80.24191
Stockholm Internet ExchangeStockholm, Sweden192.121.80.24191
Netnod StockholmStockholm, Sweden195.69.119.6077
Netnod Sundsvall- GävleSundsvall, Sweden194.68.128.6018

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.