Observed topology

AS2874 ORANGE BUSINESS SERVICES U.S. Inc.

Unclassified RIPE

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 11

Adjacent (IPv6) 8

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2874: 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 AS2874 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,102

Adjacency

Adjacent networks

All 12

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

AS	Network	Type	Families	Paths seen
AS51964	ORANGE BUSINESS SERVICES U.S. Inc.	Unclassified	IPv4 IPv6	1,236
AS5511	Orange S.A.	Transit	IPv4 IPv6	774
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	254
AS50304	Blix Solutions AS	Unclassified	IPv4 IPv6	57
AS33891	Core-Backbone GmbH	Hosting	IPv4	38
AS24482	SG.GS	Hosting	IPv4 IPv6	25
AS5405	Inter.link GmbH	Unclassified	IPv4 IPv6	22
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	20
AS20764	CJSC RASCOM	Unclassified	IPv4	19
AS12552	GlobalConnect AB	Unclassified	IPv4	18

All 12 adjacent →

Provenance

Where this comes from

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