asn.dev

Observed topology

AS49551 TELESETI-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49551: 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
AS61031ESCOMTEL BACKGROUND COMMUNICATION NETWORKS Ltd.ResidentialIPv4357
AS3216PJSC "Vimpelcom"MobileIPv4276
AS20485Joint Stock Company TransTeleComUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv448
AS24482SG.GSHostingIPv46
AS34927iFog GmbHHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46
AS50673Serverius Holding B.V.UnclassifiedIPv46
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv46

Transit

Downstream networks

inferred

Networks for which AS49551 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS61031ESCOMTEL BACKGROUND COMMUNICATION NETWORKS Ltd.ResidentialIPv4357
AS3216PJSC "Vimpelcom"MobileIPv4276
AS20485Joint Stock Company TransTeleComUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv448
AS24482SG.GSHostingIPv46
AS34927iFog GmbHHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46
AS50673Serverius Holding B.V.UnclassifiedIPv46
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv46

Provenance

Where this comes from

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