asn.dev

Observed topology

AS35548 SMARTTERRA-AS

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35548: 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
AS8365Man-da.de GmbHEducationIPv4 IPv6231
AS1299Arelion Sweden ABTransitIPv4 IPv6157
AS3320Deutsche Telekom AGMobileIPv4 IPv6154
AS6939Hurricane Electric LLCTransitIPv612
AS24482SG.GSHostingIPv4 IPv610

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58211Marco ZebutUnclassifiedIPv4118
AS209915trivago N.V.UnclassifiedIPv4 IPv643
AS33933M2Soft GmbHUnclassifiedIPv421
AS198018trivago N.V.UnclassifiedIPv418
AS29018trivago N.V.UnclassifiedIPv48

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS8365Man-da.de GmbHEducationIPv4 IPv6368
AS1299Arelion Sweden ABTransitIPv4 IPv6195
AS3320Deutsche Telekom AGMobileIPv4 IPv6190
AS58211Marco ZebutUnclassifiedIPv4118
AS209915trivago N.V.UnclassifiedIPv4 IPv643
AS33933M2Soft GmbHUnclassifiedIPv421
AS198018trivago N.V.UnclassifiedIPv418
AS6939Hurricane Electric LLCTransitIPv612
AS24482SG.GSHostingIPv4 IPv612
AS29018trivago N.V.UnclassifiedIPv48

Provenance

Where this comes from

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