Observed topology

AS268248 AS268248 - UPNETIX TELECOM

Unclassified APNIC NSP

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268248: 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
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4	188
AS7738	V tal	Unclassified	IPv4 IPv6	116
AS4230	CLARO S.A.	Residential	IPv6	27

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS271657	Iran Telecom	Unclassified	IPv4 IPv6	117
AS274791	FIBER POINT SERVICOS DE COMUNICACOES MULTIMIDIA LT	Unclassified	IPv6	33
AS273708	LSMR PROVEDOR DE INTERNET LTDA	Unclassified	IPv4 IPv6	29

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS7738	V tal	Unclassified	IPv4 IPv6	273
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4	240
AS271657	Iran Telecom	Unclassified	IPv4 IPv6	117
AS271493	SPEED NET PEDRA	Unclassified	IPv4	61
AS4230	CLARO S.A.	Residential	IPv6	58
AS274791	FIBER POINT SERVICOS DE COMUNICACOES MULTIMIDIA LT	Unclassified	IPv6	33
AS273708	LSMR PROVEDOR DE INTERNET LTDA	Unclassified	IPv4 IPv6	29

Provenance

Where this comes from

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