Observed topology

AS267357 AS267357 - Livenet telecom

Unclassified APNIC

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 6

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267357: 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
AS270735	COMPUTIZE NETWORK TELECOMUNICACOES LTDA	Hosting	IPv4	632
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	442
AS21574	Century Telecom Ltda	Unclassified	IPv4 IPv6	76
AS52468	UFINET PANAMA S.A.	Unclassified	IPv6	9

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268725	Planex Telecom	Unclassified	IPv4 IPv6	164
AS273350	Gns Telecom	Unclassified	IPv4 IPv6	142

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS270735	COMPUTIZE NETWORK TELECOMUNICACOES LTDA	Hosting	IPv4 IPv6	770
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	526
AS268725	Planex Telecom	Unclassified	IPv4 IPv6	164
AS273350	Gns Telecom	Unclassified	IPv4 IPv6	142
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4 IPv6	93
AS21574	Century Telecom Ltda	Unclassified	IPv4 IPv6	76

Provenance

Where this comes from

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