asn.dev

Observed topology

AS23428 SERVERFORGE

Unclassified ARIN

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS23428: 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 LLCTransitIPv4 IPv6235
AS54641InMotion Hosting, Inc.HostingIPv4 IPv690
AS22611InMotion Hosting, Inc.HostingIPv4 IPv689
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv684
AS61138Zappie Host LLCUnclassifiedIPv448
AS1299Arelion Sweden ABTransitIPv4 IPv624
AS64289Macarne.comUnclassifiedIPv4 IPv623
AS9002RETN LimitedUnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv64
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50842ServerForge LLCUnclassifiedIPv636
AS207556ServerForge LLCUnclassifiedIPv636

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6235
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv6156
AS54641InMotion Hosting, Inc.HostingIPv4 IPv690
AS22611InMotion Hosting, Inc.HostingIPv4 IPv689
AS61138Zappie Host LLCUnclassifiedIPv448
AS50842ServerForge LLCUnclassifiedIPv636
AS207556ServerForge LLCUnclassifiedIPv636
AS1299Arelion Sweden ABTransitIPv4 IPv624
AS64289Macarne.comUnclassifiedIPv4 IPv623
AS9002RETN LimitedUnclassifiedIPv4 IPv65

Provenance

Where this comes from

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