asn.dev

Observed topology

AS208621 logicforge LogicForge Limited

Hosting RIPE

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

Transit

Upstream networks

All 26

Networks observed carrying traffic for AS208621: 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
AS63018Dedicated.comHostingIPv4 IPv6327
AS20860IOMART CLOUD SERVICES LIMITEDHostingIPv4 IPv6219
AS6939Hurricane Electric LLCTransitIPv4 IPv695
AS44066firstcolo GmbHUnclassifiedIPv4 IPv692
AS42708Glesys ABUnclassifiedIPv4 IPv658
AS174Cogent Communications, LLCTransitIPv4 IPv628
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv611
AS9002RETN LimitedUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv68
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv66

All 26 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209243QuickHostUK LimitedUnclassifiedIPv4 IPv6333
AS59566LogicForge LimitedHostingIPv633

Adjacency

Adjacent networks

All 32

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

ASNetworkTypeFamiliesPaths seen
AS209243QuickHostUK LimitedUnclassifiedIPv4 IPv6355
AS63018Dedicated.comHostingIPv4 IPv6327
AS20860IOMART CLOUD SERVICES LIMITEDHostingIPv4 IPv6313
AS6939Hurricane Electric LLCTransitIPv4 IPv6184
AS44066firstcolo GmbHUnclassifiedIPv4 IPv692
AS42708Glesys ABUnclassifiedIPv4 IPv658
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv651
AS59566LogicForge LimitedHostingIPv633
AS50304Blix Solutions ASUnclassifiedIPv429
AS174Cogent Communications, LLCTransitIPv4 IPv628

All 32 adjacent →

Provenance

Where this comes from

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