Observed topology

AS20253 QWILTED-PROD-01 - Qwilt Inc.

Unclassified ARIN

Upstreams 11 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 11

Adjacent (IPv6) 2

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS20253: 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
AS999	CORIX NETWORKS	Unclassified	IPv4	456
AS174	Cogent Communications, LLC	Transit	IPv4	59
AS701	Verizon Business	Residential	IPv4 IPv6	9
AS6939	Hurricane Electric LLC	Transit	IPv4	7
AS852	TELUS Communications Inc.	Residential	IPv4 IPv6	2
AS9002	RETN Limited	Unclassified	IPv4	2
AS3130	RGnet OU	Unclassified	IPv4	1
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	1
AS24482	SG.GS	Hosting	IPv4	1
AS52025	ParadoxNetworks Limited	Unclassified	IPv4	1

All 11 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

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

AS	Network	Type	Families	Paths seen
AS999	CORIX NETWORKS	Unclassified	IPv4	456
AS174	Cogent Communications, LLC	Transit	IPv4	59
AS701	Verizon Business	Residential	IPv4 IPv6	9
AS6939	Hurricane Electric LLC	Transit	IPv4	7
AS852	TELUS Communications Inc.	Residential	IPv4 IPv6	2
AS9002	RETN Limited	Unclassified	IPv4	2
AS3130	RGnet OU	Unclassified	IPv4	1
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	1
AS24482	SG.GS	Hosting	IPv4	1
AS52025	ParadoxNetworks Limited	Unclassified	IPv4	1

All 11 adjacent →

Provenance

Where this comes from

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