asn.dev

Observed topology

AS12678 BADOO-U

Hosting RIPE Content

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

Transit

Upstream networks

All 25

Networks observed carrying traffic for AS12678: 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
AS19551Incapsula IncHostingIPv4472
AS6939Hurricane Electric LLCTransitIPv4 IPv6274
AS1299Arelion Sweden ABTransitIPv4 IPv6141
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv682
AS174Cogent Communications, LLCTransitIPv443
AS8220COLT Technology Services Group LimitedHostingIPv434
AS3257GTT Communications Inc.TransitIPv4 IPv630
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS1836green.ch AGResidentialIPv4 IPv65
AS12859BIT BVHostingIPv4 IPv65

All 25 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS19551Incapsula IncHostingIPv4472
AS6939Hurricane Electric LLCTransitIPv4 IPv6274
AS1299Arelion Sweden ABTransitIPv4 IPv6141
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv682
AS174Cogent Communications, LLCTransitIPv443
AS8220COLT Technology Services Group LimitedHostingIPv434
AS3257GTT Communications Inc.TransitIPv4 IPv630
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS1836green.ch AGResidentialIPv4 IPv65
AS12859BIT BVHostingIPv4 IPv65

All 25 adjacent →

Provenance

Where this comes from

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