Observed topology

AS267344 PLANOWEB NETWORKS

Unclassified ARIN Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

Upstream graph Who carries AS267344, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS267344 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267344: 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.

AS	Network	Type	Families	Paths seen
AS52873	Softdados Telecomunicacoes	Unclassified	IPv4 IPv6	58
AS1031	PEER 1031 LLC	Unclassified	IPv4 IPv6	47
AS999	CORIX NETWORKS	Unclassified	IPv4	26
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	12
AS33891	Core-Backbone GmbH	Hosting	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS270715	TELECOM SERVICOS DE INTERNET LTDA	Unclassified	IPv4 IPv6	103

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS52873	Softdados Telecomunicacoes	Unclassified	IPv4 IPv6	118
AS270715	TELECOM SERVICOS DE INTERNET LTDA	Unclassified	IPv4 IPv6	103
AS999	CORIX NETWORKS	Unclassified	IPv4	52
AS1031	PEER 1031 LLC	Unclassified	IPv4 IPv6	52
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	22
AS33891	Core-Backbone GmbH	Hosting	IPv4	4

Provenance

Where this comes from

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