Observed topology

AS10282 GLOBAL ONE

Unclassified APNIC NSP

Upstreams 0 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 22

Adjacent (IPv6) 7

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10282: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS51964	ORANGE BUSINESS SERVICES U.S. Inc.	Unclassified	IPv4 IPv6	2,581
AS15495	BASF Digital Solutions GmbH	Unclassified	IPv4 IPv6	30

Adjacency

Adjacent networks

All 25

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

AS	Network	Type	Families	Paths seen
AS51964	ORANGE BUSINESS SERVICES U.S. Inc.	Unclassified	IPv4 IPv6	3,169
AS5511	Orange S.A.	Transit	IPv4 IPv6	1,924
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	526
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	117
AS33891	Core-Backbone GmbH	Hosting	IPv4	92
AS12779	IT.Gate S.p.A.	Unclassified	IPv4	48
AS6797	GlobalConnect AB	Unclassified	IPv4	44
AS1836	green.ch AG	Residential	IPv4	39
AS8551	Bezeq International Ltd.	Unclassified	IPv4	39
AS12859	BIT BV	Hosting	IPv4	39

All 25 adjacent →

Provenance

Where this comes from

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