asn.dev

Observed topology

AS14619 AS-THERA-

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14619: 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
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv659
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv631
AS265137CONECTIVA TELECOM TECNOLOGIA LTDA - MEUnclassifiedIPv4 IPv63
AS33891Core-Backbone GmbHHostingIPv4 IPv62
AS3303Swisscom (Schweiz) AGResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266407ASSEMBLEIA LEGISLATIVA DO ESTADO DE GOIASUnclassifiedIPv4 IPv696
AS18782Thera TelecomUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6184
AS266407ASSEMBLEIA LEGISLATIVA DO ESTADO DE GOIASUnclassifiedIPv4 IPv696
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv681
AS18782Thera TelecomUnclassifiedIPv666
AS273502LIVRE FIBRA INTERNET LTDA.UnclassifiedIPv426
AS265137CONECTIVA TELECOM TECNOLOGIA LTDA - MEUnclassifiedIPv4 IPv614
AS33891Core-Backbone GmbHHostingIPv4 IPv64
AS3303Swisscom (Schweiz) AGResidentialIPv41

Provenance

Where this comes from

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