asn.dev

Observed topology

AS196945 MICROBASE-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS196945: 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
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4 IPv6203
AS39505VESTITEL BGUnclassifiedIPv4173
AS6939Hurricane Electric LLCTransitIPv4 IPv673

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207767FERMORITE Systems, Applications and Services on IT and Technology IKEUnclassifiedIPv488
AS214948CH.STAMOULIS-TH.CHRISTODOULOPOULOS TECHNOLOGICAL LLCUnclassifiedIPv4 IPv682
AS40990First Telecom Ltd.UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4 IPv6318
AS39505VESTITEL BGUnclassifiedIPv4173
AS6939Hurricane Electric LLCTransitIPv4 IPv6101
AS207767FERMORITE Systems, Applications and Services on IT and Technology IKEUnclassifiedIPv488
AS198477TI SPARKLE GREECE SAUnclassifiedIPv486
AS214948CH.STAMOULIS-TH.CHRISTODOULOPOULOS TECHNOLOGICAL LLCUnclassifiedIPv4 IPv682
AS40990First Telecom Ltd.UnclassifiedIPv459

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.