asn.dev

Observed topology

AS203861 SERVEREXPRESS-AS Miteflux Technologies Ltd

Unclassified Spamhaus ASN-DROP RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203861: 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
AS3399Obenet ABUnclassifiedIPv4 IPv693
AS214409Zektra Networks LtdHostingIPv464
AS49592Pipe Networks GmbHUnclassifiedIPv462
AS203446SMARTNET Germany GmbHUnclassifiedIPv461
AS200636Paravirt LTDUnclassifiedIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198189Throttle LimitedUnclassifiedIPv4 IPv6157

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS198189Throttle LimitedUnclassifiedIPv4 IPv6157
AS214409Zektra Networks LtdHostingIPv4129
AS3399Obenet ABUnclassifiedIPv4 IPv6125
AS203446SMARTNET Germany GmbHUnclassifiedIPv4121
AS49592Pipe Networks GmbHUnclassifiedIPv462
AS200636Paravirt LTDUnclassifiedIPv460

Provenance

Where this comes from

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