asn.dev

Observed topology

AS48303 ovisit OVIS IT Consulting GmbH

Residential RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS48303: 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
AS13237euNetworks GmbHUnclassifiedIPv4 IPv681
AS1299Arelion Sweden ABTransitIPv4 IPv649
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS34549meerfarbig GmbH & Co. KGHostingIPv49
AS24482SG.GSHostingIPv4 IPv64
AS6797GlobalConnect ABUnclassifiedIPv43
AS8551Bezeq International Ltd.UnclassifiedIPv43
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43
AS34019Hivane AssociationUnclassifiedIPv43
AS37100SEACOM LimitedUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15038The Cambridge Incubator, LLCUnclassifiedIPv459

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6105
AS1299Arelion Sweden ABTransitIPv4 IPv662
AS15038The Cambridge Incubator, LLCUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv4 IPv648
AS34549meerfarbig GmbH & Co. KGHostingIPv412
AS24482SG.GSHostingIPv4 IPv65
AS6797GlobalConnect ABUnclassifiedIPv44
AS8551Bezeq International Ltd.UnclassifiedIPv44
AS20485Joint Stock Company TransTeleComUnclassifiedIPv44
AS34019Hivane AssociationUnclassifiedIPv44

Provenance

Where this comes from

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