asn.dev

Observed topology

AS210879 SPARTEO Sparteo SAS

Hosting APNIC

Upstreams 4 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 7
Upstream graph Who carries AS210879, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS210879 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS8309SIPARTECH SASUnclassifiedIPv4 IPv697
AS35625Eurofiber France SASHostingIPv4 IPv652
AS204092Association GRIFONUnclassifiedIPv4 IPv63
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210855Meetscale SASUnclassifiedIPv4 IPv6211
AS210858Sparteo SASUnclassifiedIPv4 IPv6153
AS48402Sparteo SASUnclassifiedIPv4 IPv694

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8309SIPARTECH SASUnclassifiedIPv4 IPv6343
AS35625Eurofiber France SASHostingIPv4 IPv6252
AS210855Meetscale SASUnclassifiedIPv4 IPv6211
AS210858Sparteo SASUnclassifiedIPv4 IPv6153
AS48402Sparteo SASUnclassifiedIPv4 IPv694
AS204092Association GRIFONUnclassifiedIPv4 IPv612
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv64

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.