asn.dev

Observed topology

AS214508 MANUBRAIBANT

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS214508: 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
AS212895Johannes ErnstUnclassifiedIPv665
AS214757Jakub KrsaUnclassifiedIPv620
AS34927iFog GmbHHostingIPv66
AS11967Hop179 OUUnclassifiedIPv65
AS24482SG.GSHostingIPv63
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv63
AS37989DCS1 Pte. Ltd.HostingIPv63
AS58057Securebit AGUnclassifiedIPv63
AS401753BIXCE IncUnclassifiedIPv63
AS199854Jens ThiesUnclassifiedIPv61

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS214508 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 11

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

ASNetworkTypeFamiliesPaths seen
AS212895Johannes ErnstUnclassifiedIPv665
AS214757Jakub KrsaUnclassifiedIPv620
AS34927iFog GmbHHostingIPv66
AS11967Hop179 OUUnclassifiedIPv65
AS24482SG.GSHostingIPv63
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv63
AS37989DCS1 Pte. Ltd.HostingIPv63
AS58057Securebit AGUnclassifiedIPv63
AS401753BIXCE IncUnclassifiedIPv63
AS199854Jens ThiesUnclassifiedIPv61

All 11 adjacent →

Provenance

Where this comes from

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