asn.dev

Observed topology

AS212123 REDPANDA-AS Red Panda Network

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS212123: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6137
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv681
AS200462Lennart Seitz trading as "ETH-Services"HostingIPv4 IPv649
AS34854Maria Merkel trading as Blahaj StudioHostingIPv4 IPv642
AS21700Neptune Networks, LLCUnclassifiedIPv637
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv68
AS401753BIXCE IncUnclassifiedIPv4 IPv68
AS31500Global Network Management IncUnclassifiedIPv44
AS4913410VPN Research Network LTDUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207424Max OuwensUnclassifiedIPv64

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6137
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv682
AS200462Lennart Seitz trading as "ETH-Services"HostingIPv4 IPv650
AS34854Maria Merkel trading as Blahaj StudioHostingIPv4 IPv642
AS21700Neptune Networks, LLCUnclassifiedIPv637
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv68
AS401753BIXCE IncUnclassifiedIPv4 IPv68
AS58057Securebit AGUnclassifiedIPv65
AS31500Global Network Management IncUnclassifiedIPv44

Provenance

Where this comes from

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