Observed topology

AS267857 INTEGRA MULTISOLUTIONS S.A.S.

Unclassified ARIN

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267857: 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
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4 IPv6	289
AS18678	INTERNEXA S.A. E.S.P	Unclassified	IPv4	77
AS3816	COLOMBIA TELECOMUNICACIONES S.A. ESP BIC	Residential	IPv4	60
AS262589	SAMM TECNOLOGIA E TELECOMUNICACOES S.A	Unclassified	IPv4	42

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS273168	INFRAESTRUCTURA Y REDES SAS	Unclassified	IPv6	33

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4 IPv6	322
AS18678	INTERNEXA S.A. E.S.P	Unclassified	IPv4	77
AS3816	COLOMBIA TELECOMUNICACIONES S.A. ESP BIC	Residential	IPv4	60
AS262589	SAMM TECNOLOGIA E TELECOMUNICACOES S.A	Unclassified	IPv4	42
AS273168	INFRAESTRUCTURA Y REDES SAS	Unclassified	IPv6	33

Provenance

Where this comes from

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