asn.dev

Observed topology

AS50073 Webcraft Found LLC

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50073: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212651D-CONECT LLCUnclassifiedIPv4240
AS201626Podillia-hotel PJSCUnclassifiedIPv4 IPv694
AS202318ECO-INITIATIVE LLCUnclassifiedIPv634
AS202383EL.K.STIL LLCUnclassifiedIPv634
AS202481LTD "Reapolis"UnclassifiedIPv634
AS213897BUBBLES ALTER LIMITEDUnclassifiedIPv634
AS214018INTERNET INTELLIGENCE COMPANY LTDUnclassifiedIPv634

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6316
AS212651D-CONECT LLCUnclassifiedIPv4240
AS3257GTT Communications Inc.TransitIPv4 IPv6188
AS201626Podillia-hotel PJSCUnclassifiedIPv4 IPv694
AS202318ECO-INITIATIVE LLCUnclassifiedIPv634
AS202383EL.K.STIL LLCUnclassifiedIPv634
AS202481LTD "Reapolis"UnclassifiedIPv634
AS213897BUBBLES ALTER LIMITEDUnclassifiedIPv634
AS214018INTERNET INTELLIGENCE COMPANY LTDUnclassifiedIPv634

Provenance

Where this comes from

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