asn.dev

Observed topology

AS399888 WIRECAT-LLC - WireCat LLC

Hosting APNIC Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS399888: 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
AS18779EGIHostingHostingIPv4 IPv6360
AS41378Kirino LLCUnclassifiedIPv4 IPv6103
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30307Kasumi Networks NA LLCUnclassifiedIPv4 IPv6227
AS30114Decima LLCUnclassifiedIPv637
AS55223BGP Networks LLCUnclassifiedIPv636

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS18779EGIHostingHostingIPv4 IPv6479
AS41378Kirino LLCUnclassifiedIPv4 IPv6284
AS30307Kasumi Networks NA LLCUnclassifiedIPv4 IPv6227
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS30114Decima LLCUnclassifiedIPv637
AS55223BGP Networks LLCUnclassifiedIPv636
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv41

Provenance

Where this comes from

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