asn.dev

Observed topology

AS47379 SITS-AS SITS Ltd

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47379: 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
AS3216PJSC "Vimpelcom"MobileIPv4102
AS29076Citytelecom LLCHostingIPv466
AS20764CJSC RASCOMUnclassifiedIPv415
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34739Electronic Shield Ltd.UnclassifiedIPv4118
AS49371Shark Telecom LLCUnclassifiedIPv4117
AS204908Shark Telecom LLCUnclassifiedIPv434
AS48371Westlan LTDResidentialIPv418
AS35129"LLC Tetra-Telematik"UnclassifiedIPv47

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4221
AS20764CJSC RASCOMUnclassifiedIPv4143
AS34739Electronic Shield Ltd.UnclassifiedIPv4118
AS49371Shark Telecom LLCUnclassifiedIPv4117
AS1299Arelion Sweden ABTransitIPv4103
AS204908Shark Telecom LLCUnclassifiedIPv469
AS29076Citytelecom LLCHostingIPv466
AS48371Westlan LTDResidentialIPv453
AS24482SG.GSHostingIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410

All 11 adjacent →

Provenance

Where this comes from

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