asn.dev

Observed topology

AS41745 FORTIS-AS Hosting services

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS41745: 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
AS48729ServerKing B.V.UnclassifiedIPv4 IPv63,649
AS51765Oy Crea Nova Hosting Solution LtdHostingIPv42,940
AS42708Glesys ABUnclassifiedIPv41,710
AS49434FBW NETWORKS SASUnclassifiedIPv41,464
AS8285SIAHostingIPv4814
AS34702Aktsiaselts WaveComHostingIPv4767
AS19318Interserver, IncHostingIPv4698
AS213220Delta LtdUnclassifiedIPv4680
AS15694Atman Sp. z o.o.ResidentialIPv4540
AS35200TransitX LtdUnclassifiedIPv4295

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS41745 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 11

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

ASNetworkTypeFamiliesPaths seen
AS48729ServerKing B.V.UnclassifiedIPv4 IPv63,649
AS51765Oy Crea Nova Hosting Solution LtdHostingIPv42,940
AS42708Glesys ABUnclassifiedIPv41,710
AS49434FBW NETWORKS SASUnclassifiedIPv41,464
AS8285SIAHostingIPv4814
AS34702Aktsiaselts WaveComHostingIPv4767
AS19318Interserver, IncHostingIPv4698
AS213220Delta LtdUnclassifiedIPv4680
AS15694Atman Sp. z o.o.ResidentialIPv4540
AS35200TransitX LtdUnclassifiedIPv4295

All 11 adjacent →

Provenance

Where this comes from

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