Observed topology

AS48957 NETWORK-LVIV-AS

Unclassified RIPE

Upstreams 4 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48957: 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
AS3255	LLC EKSINTECH	Unclassified	IPv4 IPv6	565
AS1820	WNET TELECOM USA Corp.	Residential	IPv4	290
AS15895	"Kyivstar" PJSC	Mobile	IPv4	19
AS24482	SG.GS	Hosting	IPv4 IPv6	13

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS35166	PE Shtanhret Taras Orestovych	Unclassified	IPv4	132
AS43880	Laboratory of Information Technologies LLC	Unclassified	IPv4	132
AS43864	Integra-Media Ltd	Unclassified	IPv4	66
AS59468	TzOV "CENTR SAPR"	Unclassified	IPv4	66
AS29375	Technics for Business Ltd	Unclassified	IPv4	1
AS58021	Suprovich Natalya Petrivna PE	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3255	LLC EKSINTECH	Unclassified	IPv4 IPv6	813
AS1820	WNET TELECOM USA Corp.	Residential	IPv4	416
AS35166	PE Shtanhret Taras Orestovych	Unclassified	IPv4	132
AS43880	Laboratory of Information Technologies LLC	Unclassified	IPv4	132
AS43864	Integra-Media Ltd	Unclassified	IPv4	66
AS59468	TzOV "CENTR SAPR"	Unclassified	IPv4	66
AS15895	"Kyivstar" PJSC	Mobile	IPv4	41
AS24482	SG.GS	Hosting	IPv4 IPv6	19
AS29375	Technics for Business Ltd	Unclassified	IPv4	1
AS58021	Suprovich Natalya Petrivna PE	Unclassified	IPv4	1

Provenance

Where this comes from

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