asn.dev

Observed topology

AS49088 TELMEKOM-AS

Residential RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS49088: 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 IPv6529
AS3257GTT Communications Inc.TransitIPv4 IPv6134
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv646
AS24482SG.GSHostingIPv4 IPv613
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv613
AS212024Marc SchmittUnclassifiedIPv4 IPv613
AS20485Joint Stock Company TransTeleComUnclassifiedIPv411
AS33891Core-Backbone GmbHHostingIPv411
AS37100SEACOM LimitedUnclassifiedIPv411
AS59919Brainbox S.r.l.ResidentialIPv411

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50507Accademia Europea di BolzanoUnclassifiedIPv4165
AS51708Libera Universita di BolzanoUnclassifiedIPv4131

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6763
AS50507Accademia Europea di BolzanoUnclassifiedIPv4165
AS3257GTT Communications Inc.TransitIPv4 IPv6149
AS51708Libera Universita di BolzanoUnclassifiedIPv4131
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv664
AS212024Marc SchmittUnclassifiedIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv616
AS37100SEACOM LimitedUnclassifiedIPv416
AS20485Joint Stock Company TransTeleComUnclassifiedIPv414
AS33891Core-Backbone GmbHHostingIPv414

All 16 adjacent →

Provenance

Where this comes from

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