asn.dev

Observed topology

AS61828 NETWISE INFORMATICA LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61828: 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
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6779
AS6939Hurricane Electric LLCTransitIPv4 IPv675
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv650
AS24482SG.GSHostingIPv4 IPv614
AS33891Core-Backbone GmbHHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61717NetTri TelecomUnclassifiedIPv4120
AS273617Kingsnet Telecom LtdaUnclassifiedIPv668
AS264562PBR SERVICOS DE TELECOMUNICACOES LTDAResidentialIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6985
AS61717NetTri TelecomUnclassifiedIPv4120
AS6939Hurricane Electric LLCTransitIPv4 IPv6106
AS273617Kingsnet Telecom LtdaUnclassifiedIPv668
AS264562PBR SERVICOS DE TELECOMUNICACOES LTDAResidentialIPv459
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv655
AS24482SG.GSHostingIPv4 IPv619
AS33891Core-Backbone GmbHHostingIPv62

Provenance

Where this comes from

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