Observed topology

AS32869 SILVERSTAR-NET - Silver Star Telecom, LLC

Hosting ARIN NSP

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32869: 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
AS6939	Hurricane Electric LLC	Transit	IPv4	650
AS3356	Level 3 Parent, LLC	Transit	IPv4	91
AS7018	AT&T Enterprises, LLC	Residential	IPv4	52
AS3130	RGnet OU	Unclassified	IPv4	13
AS24482	SG.GS	Hosting	IPv4	13
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	13

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS32915	Kattare Internet Services	Hosting	IPv4	147

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	782
AS32915	Kattare Internet Services	Hosting	IPv4	147
AS3356	Level 3 Parent, LLC	Transit	IPv4	91
AS7018	AT&T Enterprises, LLC	Residential	IPv4	58
AS3130	RGnet OU	Unclassified	IPv4	16
AS24482	SG.GS	Hosting	IPv4	16
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	16

Provenance

Where this comes from

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