Observed topology

AS199250 CKPARTNET

Residential APNIC

Upstreams 3 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS199250: 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
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	426
AS3356	Level 3 Parent, LLC	Transit	IPv4	19
AS24482	SG.GS	Hosting	IPv4	7

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS204864	CENTRUM KOMPUTEROWE "PARTNET" MIROSLAW WOLSZLEGIER	Unclassified	IPv4	130

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	522
AS204864	CENTRUM KOMPUTEROWE "PARTNET" MIROSLAW WOLSZLEGIER	Unclassified	IPv4	130
AS3356	Level 3 Parent, LLC	Transit	IPv4	45
AS24482	SG.GS	Hosting	IPv4	9
AS33891	Core-Backbone GmbH	Hosting	IPv4	4
AS5617	Orange Polska Spolka Akcyjna	Mobile	IPv4	1
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv4	1

Provenance

Where this comes from

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