asn.dev

Observed topology

AS47498 iFog GmbH

Unclassified RIPE Route Server

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47498: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS400688Daniel Marks, Sole ProprietorshipUnclassifiedIPv4 IPv66
AS56762Olympic Input/Output, LLCUnclassifiedIPv64
AS197371Andreas Meyer, trading as Swiss VoIP Carrier Solutions MeyerUnclassifiedIPv44
AS203405Lin Kai-LunUnclassifiedIPv64
AS215743Gerben Roelof FokkemaUnclassifiedIPv64
AS58299Openfactory GmbHResidentialIPv42
AS206193Jacob LeonardUnclassifiedIPv62
AS208755Thomas FergusonUnclassifiedIPv42
AS213880Jorge Janaite NetoUnclassifiedIPv62
AS42WoodyNet, Inc.UnclassifiedIPv41

All 13 downstreams →

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS62000SERVERD SASHostingIPv4 IPv612
AS34927iFog GmbHHostingIPv411
AS50629LWLcom GmbHUnclassifiedIPv4 IPv610
AS400688Daniel Marks, Sole ProprietorshipUnclassifiedIPv4 IPv66
AS56762Olympic Input/Output, LLCUnclassifiedIPv64
AS197371Andreas Meyer, trading as Swiss VoIP Carrier Solutions MeyerUnclassifiedIPv44
AS203405Lin Kai-LunUnclassifiedIPv64
AS215743Gerben Roelof FokkemaUnclassifiedIPv64
AS6206Netrouting B.V.HostingIPv42
AS58299Openfactory GmbHResidentialIPv42

All 18 adjacent →

Provenance

Where this comes from

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