Observed topology

AS6853 ORANGE BUSINESS SERVICES U.S. Inc.

Unclassified RIPE

Upstreams 0 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 12

Adjacent (IPv6) 13

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6853: 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 AS6853 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	1,127
AS49865	JT International SA	Unclassified	IPv4 IPv6	177

Adjacency

Adjacent networks

All 15

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

AS	Network	Type	Families	Paths seen
AS5511	Orange S.A.	Transit	IPv4 IPv6	1,144
AS51964	ORANGE BUSINESS SERVICES U.S. Inc.	Unclassified	IPv4 IPv6	1,127
AS49865	JT International SA	Unclassified	IPv4 IPv6	177
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	103
AS24482	SG.GS	Hosting	IPv4 IPv6	11
AS33891	Core-Backbone GmbH	Hosting	IPv4	10
AS1836	green.ch AG	Residential	IPv4 IPv6	8
AS34019	Hivane Association	Unclassified	IPv4 IPv6	8
AS48362	Stadtwerke Feldkirch	Residential	IPv4 IPv6	5
AS9002	RETN Limited	Unclassified	IPv6	4

All 15 adjacent →

Provenance

Where this comes from

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