asn.dev

Observed topology

AS33891 Core-Backbone GmbH

Hosting RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33891: 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
AS56655Gigahost ASUnclassifiedIPv41

Transit

Downstream networks

All 1,852

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

ASNetworkTypeFamiliesPaths seen
AS20546SOPRADO GmbHHostingIPv4 IPv64,967
AS12389PJSC RostelecomResidentialIPv43,470
AS15598NorthC Deutschland GmbHHostingIPv4 IPv63,114
AS20940Akamai International B.V.HostingIPv4 IPv62,978
AS7029Windstream Communications LLCResidentialIPv42,953
AS396356Latitude.shHostingIPv4 IPv62,917
AS6079RCNResidentialIPv42,838
AS201011Core-Backbone GmbHUnclassifiedIPv4 IPv62,577
AS9009M247 Europe SRLHostingIPv42,555
AS47692Nessus GmbHHostingIPv41,993

All 1,852 downstreams →

Adjacency

Adjacent networks

All 2,082

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

ASNetworkTypeFamiliesPaths seen
AS39392SH.cz s.r.o.HostingIPv4 IPv6267,207
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv685,565
AS6461Zayo BandwidthTransitIPv450,918
AS49666Telecommunication Infrastructure CompanyUnclassifiedIPv444,616
AS60068Datacamp LimitedHostingIPv4 IPv635,514
AS1299Arelion Sweden ABTransitIPv4 IPv622,146
AS3356Level 3 Parent, LLCTransitIPv4 IPv619,962
AS22652Videotron LteeResidentialIPv4 IPv618,790
AS577Bell CanadaMobileIPv4 IPv617,059
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv613,410

All 2,082 adjacent →

Provenance

Where this comes from

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