asn.dev

Observed topology

AS207778 Linservers Jacobus Huijbrechts

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS207778: 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 LLCTransitIPv681
AS39521TNGNET B.V.UnclassifiedIPv4 IPv662
AS29632Netassist International EOODUnclassifiedIPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv64
AS25091IP-Max SAUnclassifiedIPv63
AS213241TECHIT.BE SRLResidentialIPv63

All 14 upstreams →

Transit

Downstream networks

inferred

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

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv681
AS39521TNGNET B.V.UnclassifiedIPv4 IPv662
AS29632Netassist International EOODUnclassifiedIPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv64
AS25091IP-Max SAUnclassifiedIPv63
AS213241TECHIT.BE SRLResidentialIPv63

All 14 adjacent →

Provenance

Where this comes from

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