asn.dev

Observed topology

AS34854 BLAHAJ-CLOUD Maria Merkel trading as Blahaj Studio

Hosting RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34854: 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 IPv6101
AS3214xTom GmbHHostingIPv4 IPv680
AS1299Arelion Sweden ABTransitIPv4 IPv638
AS24482SG.GSHostingIPv4 IPv65
AS401753BIXCE IncUnclassifiedIPv4 IPv63
AS206499LOCIX LIMITEDUnclassifiedIPv42
AS56662Marcin GondekUnclassifiedIPv61
AS205794JINZE YANGUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203105Blahaj Internet LtdUnclassifiedIPv4 IPv696
AS212123Jori VannesteUnclassifiedIPv4 IPv652
AS214757Jakub KrsaUnclassifiedIPv637
AS64473Maria Merkel trading as Blahaj StudioHostingIPv4 IPv630
AS215777Jiri CincuraUnclassifiedIPv619
AS207424Max OuwensUnclassifiedIPv61

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6199
AS3214xTom GmbHHostingIPv4 IPv6147
AS203105Blahaj Internet LtdUnclassifiedIPv4 IPv696
AS1299Arelion Sweden ABTransitIPv4 IPv692
AS212123Jori VannesteUnclassifiedIPv4 IPv652
AS214757Jakub KrsaUnclassifiedIPv637
AS64473Maria Merkel trading as Blahaj StudioHostingIPv4 IPv630
AS215777Jiri CincuraUnclassifiedIPv619
AS24482SG.GSHostingIPv4 IPv610
AS401753BIXCE IncUnclassifiedIPv4 IPv68

All 15 adjacent →

Provenance

Where this comes from

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