asn.dev

Observed topology

AS141193 EDGOO NETWORKS, UNIPESSOAL LDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141193: 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 AS141193 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS203020HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv67,890
AS134450HostRoyale Technologies Pvt LtdUnclassifiedIPv41,806
AS133499HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv61,261
AS207990HostRoyale Technologies Pvt LtdHostingIPv443
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv611,033
AS203020HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv67,890
AS134450HostRoyale Technologies Pvt LtdUnclassifiedIPv41,806
AS133499HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv61,261
AS207990HostRoyale Technologies Pvt LtdHostingIPv443
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv633

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 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.