asn.dev

Observed topology

AS274607 AS274607 - GHT Telecom

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS274607: 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
AS263966WORLD WIFI TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv6301
AS6939Hurricane Electric LLCTransitIPv4 IPv6268
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv695
AS24482SG.GSHostingIPv617
AS37721Virtual Technologies & SolutionsResidentialIPv617

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269270ANDRE FERREIRA LIMA SERVICOS DE COMUNICACAOUnclassifiedIPv433

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263966WORLD WIFI TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv6301
AS6939Hurricane Electric LLCTransitIPv4 IPv6268
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6127
AS269270ANDRE FERREIRA LIMA SERVICOS DE COMUNICACAOUnclassifiedIPv433
AS24482SG.GSHostingIPv4 IPv618
AS37721Virtual Technologies & SolutionsResidentialIPv617

Provenance

Where this comes from

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