asn.dev

Observed topology

AS33891 Core-Backbone GmbH

Hosting RIPE

Upstreams 1 carry this network
Downstreams 1,854 this network carries
Adjacent (IPv4) 2,094
Adjacent (IPv6) 326
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,854

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

ASNetworkTypeFamiliesPaths seen
AS18403FPT Telecom CompanyResidentialIPv4 IPv65,556
AS7552Viettel GroupMobileIPv45,292
AS20546SOPRADO GmbHHostingIPv4 IPv65,128
AS12389PJSC RostelecomResidentialIPv43,233
AS15598NorthC Deutschland GmbHHostingIPv4 IPv63,113
AS20940Akamai International B.V.HostingIPv4 IPv63,013
AS7029Windstream Communications LLCResidentialIPv42,974
AS396356Latitude.shHostingIPv4 IPv62,913
AS6079RCNResidentialIPv42,890
AS7713PT Telekomunikasi IndonesiaResidentialIPv42,889

All 1,854 downstreams →

Adjacency

Adjacent networks

All 2,094

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

ASNetworkTypeFamiliesPaths seen
AS39392SH.cz s.r.o.HostingIPv4 IPv6283,046
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv686,048
AS6461Zayo BandwidthTransitIPv449,141
AS49666Telecommunication Infrastructure CompanyUnclassifiedIPv446,255
AS60068Datacamp LimitedHostingIPv4 IPv634,926
AS1299Arelion Sweden ABTransitIPv4 IPv620,475
AS3356Level 3 Parent, LLCTransitIPv4 IPv620,017
AS22652Videotron LteeResidentialIPv4 IPv618,706
AS577Bell CanadaMobileIPv4 IPv616,996
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv613,541

All 2,094 adjacent →

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.