asn.dev

Observed topology

AS47787 EDGOO EDGOO NETWORKS UNIPESSOAL LDA

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47787: 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
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv671
AS174Cogent Communications, LLCTransitIPv655

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203020HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv614,470
AS207990HostRoyale Technologies Pvt LtdHostingIPv48,060
AS209043IPRoyal Services FZE LLCUnclassifiedIPv41,856
AS44144HostRoyale Technologies Pvt LtdHostingIPv4232
AS39486HostRoyale Technologies Pvt LtdHostingIPv4118
AS40138Mach Dilemma, LLCHostingIPv4 IPv619
AS208188Puget Sound Networks, LLCUnclassifiedIPv412

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4 IPv621,773
AS203020HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv614,502
AS207990HostRoyale Technologies Pvt LtdHostingIPv48,060
AS174Cogent Communications, LLCTransitIPv4 IPv62,804
AS209043IPRoyal Services FZE LLCUnclassifiedIPv41,856
AS44144HostRoyale Technologies Pvt LtdHostingIPv4232
AS6939Hurricane Electric LLCTransitIPv4 IPv6168
AS20205Amplex Electric, Inc.ResidentialIPv4166
AS39486HostRoyale Technologies Pvt LtdHostingIPv4118
AS40138Mach Dilemma, LLCHostingIPv4 IPv619

All 12 adjacent →

Provenance

Where this comes from

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