Observed topology

AS42512 X-COM-AS

Unclassified RIPE Cable/DSL/ISP

Upstreams 6 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42512: 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
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	723
AS1820	WNET TELECOM USA Corp.	Residential	IPv4	533
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	207
AS24482	SG.GS	Hosting	IPv4 IPv6	26
AS31148	PRIVATE JOINT-STOCK COMPANY "FARLEP-INVEST"	Residential	IPv4	18
AS29632	Netassist International EOOD	Unclassified	IPv6	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS51742	FOP Molochko Nina Vasilievna,	Residential	IPv4	41
AS212438	FOP Polischuk Svitlana Illivna	Unclassified	IPv4	34
AS57985	Corporation 'Niko Management'	Unclassified	IPv4	7

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	795
AS1820	WNET TELECOM USA Corp.	Residential	IPv4	533
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	216
AS51742	FOP Molochko Nina Vasilievna,	Residential	IPv4	41
AS212438	FOP Polischuk Svitlana Illivna	Unclassified	IPv4	34
AS24482	SG.GS	Hosting	IPv4 IPv6	27
AS31148	PRIVATE JOINT-STOCK COMPANY "FARLEP-INVEST"	Residential	IPv4	18
AS57985	Corporation 'Niko Management'	Unclassified	IPv4	7
AS29632	Netassist International EOOD	Unclassified	IPv6	2

Provenance

Where this comes from

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