asn.dev

Observed topology

AS208226 OUIHEBERG Ouiheberg SARL

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208226: 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
AS62000SERVERD SASHostingIPv4 IPv6666
AS203446SMARTNET Germany GmbHUnclassifiedIPv4 IPv6215
AS212477RoyaleHosting BVHostingIPv4 IPv6183
AS60068Datacamp LimitedHostingIPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205563Marc GomezUnclassifiedIPv668
AS210535Association LordhostingUnclassifiedIPv461
AS219084Belce TaylanUnclassifiedIPv461
AS205778WeDoHosting SASUnclassifiedIPv634
AS219179Kalonys SARLUnclassifiedIPv634
AS62098Espix Network SPRLUnclassifiedIPv4 IPv626
AS216438Raphael LAURENSUnclassifiedIPv4 IPv622
AS218373Sandro PischingerUnclassifiedIPv64
AS210250K Media Tech Ltd.UnclassifiedIPv41

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS62000SERVERD SASHostingIPv4 IPv6896
AS212477RoyaleHosting BVHostingIPv4 IPv6244
AS203446SMARTNET Germany GmbHUnclassifiedIPv4 IPv6220
AS205563Marc GomezUnclassifiedIPv668
AS210535Association LordhostingUnclassifiedIPv461
AS219084Belce TaylanUnclassifiedIPv461
AS205778WeDoHosting SASUnclassifiedIPv634
AS219179Kalonys SARLUnclassifiedIPv634
AS60068Datacamp LimitedHostingIPv627
AS62098Espix Network SPRLUnclassifiedIPv4 IPv626

All 13 adjacent →

Provenance

Where this comes from

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